Johan Nilsson
> Hate to ask this, but are you really, really sure?
The file does exist:
bjam
error: Unable to find file or target named
error: '/var/tmp/ma0/boost/boost_1_42_0/stage/lib/libboost_system.a'
error: referred from project at
error: ''
Both 'ls' and 'file' show that file exists. As this was the first
thing I checked.
ls -l /var/tmp/ma0/boost/boost_1_42_0/stage/lib/libboost_system.a
-rw-r----- 1 ma0 ma 72008 2010-02-16 13:01 /var/tmp/ma0/boost/boost_1_42_0/stage/lib/libboost_system.a
file /var/tmp/ma0/boost/boost_1_42_0/stage/lib/libboost_system.a
/var/tmp/ma0/boost/boost_1_42_0/stage/lib/libboost_system.a: current ar archive
>>This is what my boost-build.jam look like:
>> BOOST_BUILD = [ MATCH --boost-build=(.*) : $(ARGV) ] ;
>> BOOST_BUILD ?= $(BOOST_ROOT)/tools/build/v2 ;
>> boost-build $(BOOST_BUILD) ;
>> Does the above actually work, or are you leaving something out? I don't know
>> if boost-build.jam is subject to some special treatment but you'd normally
>> need to e.g.:
>> local ARGV = [ modules.peek : ARGV ] ;
>> local BOOST_ROOT = [ modules.peek : BOOST_ROOT ] ; # or use "os.environ"
Yes this works in 1.39 and 1.40 so I have assumed it must work in 1.42
There appears to be some kind of regression in 1.42 but I cant pin it down.
Best regards,
Ta,
Avi