Re: [Boost-build] bjam bug invoking codeworker

Subject: Re: [Boost-build] bjam bug invoking codeworker
From: Fabien CHÊNE (fabien.chene_at_[hidden])
Date: 2009-10-22 08:31:05

2009/10/8 Fabien CHÊNE <fabien.chene_at_[hidden]>:
> Hello,
>
> I encounter a bug invoking codeworker in an 'action', bjam is
> mysteriously stucked.
> It used to work with an older version (M11, Boost.Jam 3.1.14), and
> does not work anymore at least on svn trunk.

I am trying to debug bjam, but i can't build a debug version of bjam,
build.sh --debug seems to be broken, a JamBase file is requested and
is no longer present in the build directory:

./build.sh --debug
###
### Using 'gcc' toolset.
###
rm -rf bootstrap
mkdir bootstrap
gcc -o bootstrap/jam0 command.c compile.c debug.c expand.c glob.c
hash.c hdrmacro.c headers.c jam.c jambase.c jamgram.c lists.c make.c
make1.c newstr.c option.c output.c parse.c pathunix.c pathvms.c
regexp.c rules.c scan.c search.c subst.c timestamp.c variable.c
modules.c strings.c filesys.c builtins.c pwd.c class.c native.c md5.c
w32_getreg.c modules/set.c modules/path.c modules/regex.c
modules/property-set.c modules/sequence.c modules/order.c execunix.c
fileunix.c
./bootstrap/jam0 -f build.jam --toolset=gcc --toolset-root= clean
...found 1 target...
...updating 1 target...
[DELETE] clean
...updated 1 target...
./bootstrap/jam0 -f build.jam --toolset=gcc --toolset-root= --debug
don't know how to make Jambase
...found 54 targets...
...updating 2 targets...
...can't find 1 target...
...skipped jambase.c for lack of Jambase...
...skipped bjam for lack of jambase.c...
...skipped jam for lack of bjam...
...skipped 3 targets...

Any help ?

-- 
Fab