Re: [Boost-build] [Boost-cvs] CVS: boost/tools/build/v2/tools gcc.jam, 1.82, 1.83

From: Eric Niebler (eric_at_[hidden])
Date: 2006-10-25 16:29:06

Rene Rivera wrote:
> Eric Niebler wrote:
>> Jürgen Hunold wrote:
>>> Hi Rene !
>>>
>>> This commit just broke my builds :-))
>>>
>> Me too. I use gcc that I built myself under cygwin. user-config.jam has:
> 
> Ooh... any chance you could tell me what the "(..)" part says for the 
> regular cygwin?

Not sure what (..) part you're referring to, but if I execute "g++ -v" 
from cygwin, this is what I get:

$ g++ -v
Reading specs from /usr/lib/gcc/i686-pc-cygwin/3.4.4/specs
Configured with: /gcc/gcc-3.4.4/gcc-3.4.4-1/configure --verbose 
--prefix=/usr --exec-prefix=/usr --sysconfdir=/etc --libdir=/usr/lib 
--libexecdir=/usr/lib --mandir=/usr/share/man --infodir=/usr/share/info 
--enable-languages=c,ada,c++,d,f77,java,objc --enable-nls 
--without-included-gettext --enable-version-specific-runtime-libs 
--without-x --enable-libgcj --disable-java-awt --with-system-zlib 
--enable-interpreter --disable-libgcj-debug --enable-threads=posix 
--enable-java-gc=boehm --disable-win32
-registry --enable-sjlj-exceptions --enable-hash-synchronization 
--enable-libstdcxx-debug : (reconfigured)
Thread model: posix
gcc version 3.4.4 (cygming special) (gdc 0.12, using dmd 0.125)

That's for the default g++ that comes with cygwin.

>> If I try to run this test with "bjam --v2 toolset=gcc-4.1 proto_fusion", 
>> I get the cryptic:
>>
>> gcc.compile.c++ 
>> ../../../bin.v2/libs/xpressive/test/proto_fusion.test/gcc-cygming_special-4.1/debug/link-static/proto_fusion.o
>> /bin/sh: line 1: -ftemplate-depth-128: command not found
>>
>>        -ftemplate-depth-128 -O0 -fno-inline -Wall -g 
>> -ftemplate-depth-1024 -DBOOST_ALL_NO_LIB=1  -I"../../.." -c -o 
>> "C:\cygwin\home\catfood\boost\cvs\boost\bin.v2\libs\xpressive\test\proto_fusion.test\gcc-cygming_special-4.1\debug\link-static\proto_fusion.o" 
>> "proto_fusion.cpp"
> 
> Cryptic indeed. Not sure why it would not have the command to execute 
> since I didn't change that part of the toolset.
> 
> For now... I've changed it as Volodya suggested. For now the flavor only 
> gets added for MinGW. Could you check to see if this helps.

Thanks, that fixed it.

I don't suppose you and Volodya have a way of testing out the impact of 
these toolset changes before you commit them, do you? Broken toolsets 
are pretty disruptive. I guess it'd be hard to test, since everybody's 
machine is configured differently. Thoughts?

-- 
Eric Niebler
Boost Consulting
www.boost-consulting.com