Re: [jamboost] tooset flags problem

From: David Abrahams (dave_at_[hidden])
Date: 2003-01-15 06:49:46

Vladimir Prus <ghost_at_[hidden]> writes:

> David Abrahams wrote:
>
>>>$bjam gcc-3.2
>>>...found 9 targets...
>>>...updating 5 targets...
>>>MkDir1 bin
>>>MkDir1 bin/gcc-3.2
>>>MkDir1 bin/gcc-3.2/debug
>>>gcc.compile bin/gcc-3.2/debug/hello.o
>>>hello.cpp:8:2: warning: no newline at end of file
>>>gcc.link bin/gcc-3.2/debug/hello
>>>
>>>Isn't it the coolness?
>> 
>> 
>> It *is* the coolness. However, I'm a bit surprised it worked, since
>> the whole reason I changed gcc.jam was that it was still reporting
>> <toolset-version> as invalid.
>
> I though that your intention was not to make <toolset-version>
> valid,

I didn't have that specific intention in mind. I do worry that if
<toolset-version> remains invalid, it's going to come back and bite us
eventually.

> but to make <toolset>gcc-3.2 valid. Now, toolset.flags accepts
> <toolset>gcc-3.2, verifies that it's valid, and converts it into
> normalized form, <toolset>gcc/<toolset-version>3.2
> Therefore, there's no need to make <toolset-version>3.2 to be valid.
>
>>>However, we've one problem still. Assume, that gcc-3.2 is never declared.
>>>If you run
>>>
>>> bjam gcc-3.2
>>>
>>>in examples-v2/hello, you won't be told that property is invalid, but that
>>>./hello cannot be build. Adding "--debug-generators" to the command line
>>>shows that <toolset>gcc-3.2 is in build request. I guess the error
>>>should be reported after calling build-request.expand, which call is on
>>>build-system.jam, line 63.
>>>
>>>Dave, what do you think?
>> 
>> 
>> I'm inclined to think that build-request.expand or one of the rules it
>> calls ought to be validating properties as it goes along.
>
> Oh, property.validate-property-set appears to be exactly what's needed.

Oh I think I just made changes to feature.jam which make that
unneccessary.

However, I'm getting this failure:

cd c:/boost/tools/build/test/
set PATH=c:/tools/mingw-2.0/bin;%PATH% && python stage.py
Traceback (most recent call last):
File "c:\boost\tools\build\test\stage.py", line 15, in ?
t.write("aux/1", "")
File "c:\boost\tools\build\test\BoostBuild.py", line 129, in write
open(nfile, "wb").write(content)
IOError: [Errno 2] No such file or directory: 'C:\\DOCUME~1\\DAVIDA~1\\LOCALS~1\\Temp\\testcmd.487\\aux\\1'

Compilation exited abnormally with code 1 at Wed Jan 15 06:48:00

-- 
David Abrahams
dave_at_[hidden] * http://www.boost-consulting.com
Boost support, enhancements, training, and commercial distribution