id,summary,reporter,owner,description,type,status,milestone,component,version,severity,resolution,keywords,cc 3630,building bjam with custom CFLAGS fails if $CFLAGS contains extra white space,Sebastian Mingramm ,René Rivera,"Steps to reproduce: cd boost_1_41_1_beta1/tools/jam/src/[[BR]] export CFLAGS=""-O2 -pipe""[[BR]] export CC=""x86_64-pc-linux-gnu-gcc""[[BR]] ./build.sh cc[[BR]] Output:[[BR]] [...][[BR]] [COMPILE] bin.linuxx86_64/bjam[[BR]] x86_64-pc-linux-gnu-gcc: : No such file or directory[[BR]] expand.c: In function 'var_expand':[[BR]] expand.c:85: warning: field precision should have type 'int', but argument 2 has type 'long int'[[BR]] variable.c: In function 'var_string_to_file':[[BR]] variable.c:408: warning: ignoring return value of 'fwrite', declared with attribute warn_unused_result[[BR]] variable.c:409: warning: ignoring return value of 'fwrite', declared with attribute warn_unused_result[[BR]] ""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"" ""-O2"" """" ""-pipe"" ""-s"" ""-O"" ""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""[[BR]] ...failed [COMPILE] bin.linuxx86_64/bjam...[[BR]] ...failed updating 1 target...[[BR]] What happens is that the extra white space gets converted into a """", which gcc doesn't like. There are bug reports on the gentoo bugzilla for boost 1.35 [1], 1.39, 1.40 and it's present in 1.41.0_beta1. It was also reported that the problem occurs with LDFLAGS [1, comment 27].[[BR]] [1] https://bugs.gentoo.org/show_bug.cgi?id=265402",Bugs,closed,Boost.Jam 3.1.18,build,Boost.Jam 3.1.16,Problem,fixed,,ohnobinki@…