Subject: Re: [Boost-build] LOG FILE was Re: 2 Problems with bootstrap.bat
From: Steven Watanabe (watanabesj_at_[hidden])
Date: 2012-03-17 19:50:36
AMDG
On 03/17/2012 04:27 PM, Jim Sager wrote:
>
>
> Here is my log
>
> ###
> ### 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...
> ...updated 1 target...
> ./bootstrap/jam0 -f build.jam --toolset=gcc --toolset-root=
> ...found 49 targets...
> ...updating 3 targets...
> [MKDIR] bin.linuxx86
> [COMPILE] bin.linuxx86/b2
> [COPY] bin.linuxx86/bjam
> ...updated 3 targets...
>
This is the wrong file. There's a bug in bootstrap.bat
that causes it to write the log to the parent directory.
In Christ,
Steven Watanabe