Build log on x86 of boost-build v1.34

dev-util:boost-build-1.34.1:20080505-151240.log (text/plain), 3.23 KB, created by Jason McGuiness on 2008-05-05 15:16:51 UTC

>>> Unpacking source...
>>> Unpacking boost_1_34_1.tar.bz2 to /var/tmp/portage/dev-util/boost-build-1.34.1/work
>>> Source unpacked.
>>> Compiling source in /var/tmp/portage/dev-util/boost-build-1.34.1/work/boost_1_34_1/tools ...
###
### Using 'cc' toolset.
###
rm -rf bootstrap
mkdir bootstrap
i686-pc-linux-gnu-gcc -o bootstrap/jam0 -march=athlon-xp -O3 -pipe -momit-leaf-frame-pointer -fomit-frame-pointer -fprefetch-loop-arrays -ffast-math -funroll-all-loops -funit-at-a-time -fpeel-loops -ftracer -funswitch-loops -fno-strict-aliasing -Wl,-O3 -Wl,--enable-new-dtags -Wl,--sort-common -Wl,--strip-all command.c compile.c debug.c execunix.c expand.c fileunix.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 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 w32_getreg.c modules/set.c modules/path.c modules/regex.c modules/property-set.c modules/sequence.c modules/order.c execnt.c filent.c
./bootstrap/jam0 -f build.jam --toolset=cc --toolset-root= clean
...found 1 target...
...updating 1 target...
...updated 1 target...
./bootstrap/jam0 -f build.jam --toolset=cc --toolset-root= --with-python
...found 45 targets...
...updating 2 targets...
[MKDIR] bin.linuxx86
[COMPILE] bin.linuxx86/bjam
i686-pc-linux-gnu-gcc: 	-Wl,--strip-all: No such file or directory

    "i686-pc-linux-gnu-gcc"   -o bin.linuxx86/bjam -DNDEBUG -DOPT_HEADER_CACHE_EXT -DOPT_GRAPH_DEBUG_EXT -DOPT_SEMAPHORE -DOPT_AT_FILES -DOPT_FIX_TARGET_VARIABLES_EXT -DOPT_IMPROVED_PATIENCE_EXT -DYYSTACKSIZE=5000 -march=athlon-xp -O3 -pipe -momit-leaf-frame-pointer 	-fomit-frame-pointer -fprefetch-loop-arrays -ffast-math 	-funroll-all-loops -funit-at-a-time -fpeel-loops -ftracer 	-funswitch-loops -fno-strict-aliasing -O "-Wl,-O3" "-Wl,--enable-new-dtags" "-Wl,--sort-common" "	-Wl,--strip-all" command.c compile.c debug.c expand.c glob.c hash.c hcache.c headers.c hdrmacro.c jam.c jambase.c jamgram.c lists.c make.c make1.c newstr.c option.c parse.c regexp.c rules.c scan.c search.c subst.c w32_getreg.c timestamp.c variable.c modules.c strings.c filesys.c builtins.c pwd.c class.c native.c modules/set.c modules/path.c modules/regex.c modules/property-set.c modules/sequence.c modules/order.c execunix.c fileunix.c pathunix.c

...failed [COMPILE] bin.linuxx86/bjam...
...failed updating 1 target...
...updated 1 target...
 [31;01m*[0m 
 [31;01m*[0m ERROR: dev-util/boost-build-1.34.1 failed.
 [31;01m*[0m Call stack:
 [31;01m*[0m               ebuild.sh, line   49:  Called src_compile
 [31;01m*[0m             environment, line 2600:  Called die
 [31;01m*[0m The specific snippet of code:
 [31;01m*[0m           LIBS="${LDFLAGS}" CC=$(tc-getCC) ./build.sh ${toolset} $(use_with python) || die "building bjam failed";
 [31;01m*[0m  The die message:
 [31;01m*[0m   building bjam failed
 [31;01m*[0m 
 [31;01m*[0m If you need support, post the topmost build error, and the call stack if relevant.
 [31;01m*[0m A complete build log is located at '/dev/shm/portage/log/dev-util:boost-build-1.34.1:20080505-151240.log'.
 [31;01m*[0m The ebuild environment file is located at '/var/tmp/portage/dev-util/boost-build-1.34.1/temp/environment'.
 [31;01m*[0m