i get an error saying x86_64-pc-linux-gnu-gcc: : No such file or directory when trying to build boost-build-1.42 Reproducible: Always Steps to Reproduce: 1. emerge boost-build 2. 3. Actual Results: >>> Compiling source in /var/tmp/portage/dev-util/boost-build-1.42.0/work/boost_1_42_0/tools (for ABI=amd64) ... ### ### Using 'cc' toolset. ### rm -rf bootstrap mkdir bootstrap x86_64-pc-linux-gnu-gcc -o bootstrap/mkjambase0 -march=native -O2 -fno-strict-aliasing -Wl,-O1 mkjambase.c ./bootstrap/mkjambase0 jambase.c Jambase x86_64-pc-linux-gnu-gcc -o bootstrap/jam0 -march=native -O2 -fno-strict-aliasing -Wl,-O1 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 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 expand.c: In function ‘var_expand’: expand.c:85: warning: field precision should have type ‘int’, but argument 2 has type ‘long int’ variable.c: In function ‘var_string_to_file’: variable.c:408: warning: ignoring return value of ‘fwrite’, declared with attribute warn_unused_result variable.c:409: warning: ignoring return value of ‘fwrite’, declared with attribute warn_unused_result ./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 47 targets... ...updating 2 targets... [MKDIR] bin.linuxx86_64 [COMPILE] bin.linuxx86_64/bjam x86_64-pc-linux-gnu-gcc: : No such file or directory expand.c: In function ‘var_expand’: expand.c:85: warning: field precision should have type ‘int’, but argument 2 has type ‘long int’ variable.c: In function ‘var_string_to_file’: variable.c:408: warning: ignoring return value of ‘fwrite’, declared with attribute warn_unused_result variable.c:409: warning: ignoring return value of ‘fwrite’, declared with attribute warn_unused_result "x86_64-pc-linux-gnu-gcc" -o bin.linuxx86_64/bjam "-DNDEBUG" "-DOPT_HEADER_CACHE_EXT" "-DOPT_GRAPH_DEBUG_EXT" "-DOPT_SEMAPHORE" "-DOPT_AT_FILES" "-DOPT_DEBUG_PROFILE" "-DOPT_FIX_TARGET_VARIABLES_EXT" "-DOPT_IMPROVED_PATIENCE_EXT" "-DYYSTACKSIZE=5000" "-march=native" "-O2" "" "-fno-strict-aliasing" "-O" "-Wl,-O1" "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" "mem.c" "newstr.c" "option.c" "output.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_64/bjam... ...failed updating 1 target... ...updated 1 target... * ERROR: dev-util/boost-build-1.42.0 failed: * building bjam failed * * Call stack: * ebuild.sh, line 48: Called src_compile * environment, line 3413: Called die * The specific snippet of code: * LIBS=${LDFLAGS} CC=$(tc-getCC) ./build.sh ${toolset} $(use_with python) || die "building bjam failed"; * * If you need support, post the output of 'emerge --info =dev-util/boost-build-1.42.0', * the complete build log and the output of 'emerge -pqv =dev-util/boost-build-1.42.0'. * The complete build log is located at '/var/tmp/portage/dev-util/boost-build-1.42.0/temp/build.log'. * The ebuild environment file is located at '/var/tmp/portage/dev-util/boost-build-1.42.0/temp/environment'. * S: '/var/tmp/portage/dev-util/boost-build-1.42.0/work/boost_1_42_0/tools' >>> Failed to emerge dev-util/boost-build-1.42.0, Log file: >>> '/var/tmp/portage/dev-util/boost-build-1.42.0/temp/build.log' Expected Results: compile normally
You conveniently omitted * Compilation of boost-build is known to break if {C,LD}FLAGS contain * extra white space (bug 293652) *** This bug has been marked as a duplicate of bug 293652 ***
