Issue 98685 - build don't create subdirectories unxlngi6.pro, unxlngi6.pro/misc + class in wizards
Summary: build don't create subdirectories unxlngi6.pro, unxlngi6.pro/misc + class in ...
Status: CLOSED NOT_AN_OOO_ISSUE
Alias: None
Product: Build Tools
Classification: Code
Component: dmake (show other issues)
Version: current
Hardware: PC Linux, all
: P3 Trivial (vote)
Target Milestone: ---
Assignee: hjs
QA Contact: issues@tools
URL:
Keywords:
: 98684 (view as issue list)
Depends on:
Blocks:
 
Reported: 2009-01-31 17:51 UTC by maand
Modified: 2009-11-05 17:05 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this issue.
Description maand 2009-01-31 17:51:42 UTC 
I tried to compile DEVOOom41 on my Linux box (openSuSE 10.3-i586), but I run
into trubble, when make works in wizards. The build script wasn't able to create
the subdirectories unxlngi6.pro and misc and class inside wizards/unxlngi6.pro.
If I create the subdirectories manually the build process works. This should be
done by the build script.
Comment 1 hjs 2009-02-02 16:03:55 UTC 
*** Issue 98684 has been marked as a duplicate of this issue. ***
Comment 2 hjs 2009-02-02 16:06:27 UTC 
works fine here.
what was the command line you started the build with and was the tree clean or
used for builds before?
Comment 3 maand 2009-02-02 18:41:07 UTC 
@jhs: The tree was clean. I checked m41 out in a clean directory. I started with
./configure --disable-mozilla  --disable-binfilter. Then I run ./bootstrap and
source LinuxX86Env.Set.sh. The next step was dmake and later make (instead of
dmake, because I heard from Rene, that this works.).
When the build broks in the directories (named in my description), I started the
build process first in the folder again with build and then deliver (I had to
create the missing directories first.).
Comment 4 Stephan Bergmann 2009-02-03 08:33:24 UTC 
I wonder whether the combination of using tcsh during build (i.e., no
./configure --with-use-shell=bash) and sourcing the bash-specific
LinuxX86EnvSet.sh (instead of the tcsh-specific LinuxX86EnvSet) causes trouble.
Comment 5 hjs 2009-11-05 17:04:53 UTC 
seems to be no more problem...
Comment 6 hjs 2009-11-05 17:05:16 UTC 
.