Re: [Boost-build] bjam - windows - drive letter - resolved

Subject: Re: [Boost-build] bjam - windows - drive letter - resolved
From: Anant Rao (arao_at_[hidden])
Date: 2010-02-26 13:54:34

Hi Volodya,

Thanks for your suggestion. I tried it, but to of no avail.
Here's what I did.

I copied the nighly build src and built bjam.exe.
'bjam.exe --version' shows 

Boost.Build V2 (Milestone 12)
Boost.Jam 03.1.17

I just copied this binary to my place. I didn't copy any of the *.jam files from the nightly build. Is it ok?

If this is correct, I'm afraid the fix didn't work. I am upper-casing the first letter of the path (excluding the drive letter) to get bjam to work.

Thanks,
Anant

-----Original Message-----
From: boost-build-bounces_at_[hidden] [mailto:boost-build-bounces_at_[hidden]] On Behalf Of Vladimir Prus
Sent: Thursday, February 25, 2010 11:58 PM
To: Boost.Build developer's and user's list
Subject: Re: [Boost-build] bjam - windows - drive letter - resolved

Anant Rao wrote:
> Hi,
> 
>  
> 
> I finally figured out the issue that I reported yesterday.
> 
>  
> 
> Say, I have something like this in my Jamroot:
> 
>  
> 
> constant DICTIONARY_SRC : $(SHARED)/dictionary/src ;
> 
>  
> 
>  
> 
> If $(SHARED)    is C:/hudson/<blah>,  bjam fails with the following errors:
> 
>  
> 
> c:\Hudson\jobs\test_anant\workspace\dev\ThirdParty\Boost\boost_1_40_0\boost-build.jam:16: 
> in module scope
> 
> c:/Hudson/jobs/test_anant/workspace/dev/ThirdParty/Boost/boost_1_40_0/tools/build/v2/build\targets.jam:406: 
> in find-really
> 
> *** argument error
> 
> * rule project.find ( name : current-location )
> 
> * called with: ( libmempools :  )
> 
> * missing argument current-location
> 
> c:/Hudson/jobs/test_anant/workspace/dev/ThirdParty/Boost/boost_1_40_0/tools/build/v2/build\project.jam:145:see 
> definition of rule 'find' being called
> 
>  
> 
>  
> 
>  
> 
> If $(SHARED)    is C:/Hudson/<blah>,  bjam works fine.
> 
>  
> 
> So, the diff is this:
> 
>  
> 
> C:/hudson     -> fails
> 
> C:/Hudson    -> works ok

> 
>  
> 
> Could somebody confirm this?

Could you try with nightly build as available at http://boost.org/boost-build2 ?
I think I've checked in a patch that should address a very similar failure mode.

- Volodya
_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost-build