|
Boost-Build : |
From: Lian Cheng (rhythm.mail_at_[hidden])
Date: 2008-04-24 01:37:06
Thanks very much for the tip!
I've done exactly what you told me to do, and I attached the result.
These lines seem important:
###
### Using 'gcc' toolset.
###
rm -rf bootstrap
mkdir bootstrap
gcc -o bootstrap/jam0 command.c compile.c [...]
./bootstrap/jam0 -f build.jam --toolset=gcc --toolset-root= clean
XXX
XXX bin.linuxx86_64
XXX :bin.linuxx86_64
...found 1 target...
...updating 1 target...
...updated 1 target...
./bootstrap/jam0 -f build.jam --toolset=gcc --toolset-root=
XXX
XXX bin.linuxx86_64
XXX :bin.linuxx86_64
...found 47 targets...
...updating 2 targets...
[MKDIR] :bin.linuxx86_64
[COMPILE] :bin.linuxx86_64/bjam
[...]
But I still cannot figure out what's going on... This line seems to be
the trouble maker:
locate-target ?= bin$(.)$(OS:L)$(OSPLAT:L) ;
Vladimir Prus wrote:
>
> In jam's src directory there's build.jam, that includes the following code:
>
> # Put executables in platform-specific subdirectory.
> locate-target = $(LOCATE_TARGET) ;
> if $(VMS)
> {
> locate-target ?= bin$(.)vms ;
> }
> ...
> if $(debug)
> {
> locate-target = [ .path $(locate-target)$(.)debug ] ;
> }
> else
> {
> locate-target = [ .path $(locate-target) ] ;
> }
>
> Can you add:
>
> ECHO XXX $(locate-target) ;
>
> after each assignment and see where the wrong name first appears?
>
> - Volodya
>
Boost-Build list run by bdawes at acm.org, david.abrahams at rcn.com, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk