Re: [Boost-build] Having problem with building with 1.42

Subject: Re: [Boost-build] Having problem with building with 1.42
From: Johan Nilsson (r.johan.nilsson_at_[hidden])
Date: 2010-02-17 02:43:19

Avi Bahra wrote:
> I am using bjam to build my application on suse linux. I have defined
> a
> environment variable BOOST_ROOT, which allows me to switch between
> boost builds.  I have used this approach for 1.38, 1.39,1.40.
> I always build the boost libraries I need myself using bjam.
>    bjam --build-dir=./tmpBuildDir toolset=gcc stage link=static
> --with-system
> i.e I don't bother with build scripts in $BOOST_ROOT
>
> With 1.42 when I build my application I get  an error of the form:
>
> 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:     ''
>
> The error is very misleading because the file exists?

Hate to ask this, but are you really, really sure?

> When I switch back, to 1.39/1.40 there are no problems.
>
> 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"

Sorry, that's all I can see. Haven't used bjam/boost.build more recent than 
1.40 a lot, so I haven't seen any similar problems.

/ Johan