Re: [Boost-build] building boost.python

Subject: Re: [Boost-build] building boost.python
From: Stefan Seefeld (stefan_at_[hidden])
Date: 2015-05-08 13:45:11

On 08/05/15 01:28 PM, Steven Watanabe wrote:
> AMDG
>
> On 05/08/2015 10:35 AM, Stefan Seefeld wrote:
>> Having made the adjustment you
>> suggest, I get a new error:
>>
>> error: No best alternative for /python_for_extensions
>>     next alternative: required properties: <python>2.7 <target-os>linux
>>         matched
>>     next alternative: required properties: <python>2.7 <target-os>linux
>>         matched
> You're probably initializing python twice.
> check project-config.jam and user-config.jam.

Hmm, my user-config.jam file contained "using python ;". Removing it
made the error go away. (I used to use that to specify a non-default
python version.)

Is there a way for bjam (or boost.build) to detect the multiple
initialization, and simply skip all but the first ?

>
>> I don't quite understand that error, and I'm not sure whether this is
>> user error or a problem in boost.build.
>>
>>
>> As to the stand-alone build: should I just remove the boost-build.jam
>> file entirely?
> I think so.  If you're working inside
> the boost tree, then you'll pick up
> BOOST_ROOT/boost-build.jam.

Er, if I'm building stand-alone, I'm not inside the boost tree, and thus
there is no boost-build.jam.

>> That yields the error "error: Unable to load Jamfile."
>> (Do I really need both a Jamfile and a Jamroot ?)
>>
> No.  Is there any more to the error message?

The full error is:

/usr/share/boost-build/build/project.jam:262: in find-jamfile from
module project
error: Unable to load Jamfile.
error: Could not find a Jamfile in directory '../../..'.
error: Attempted to find it with pattern '[Bb]uild.jam [Jj]amfile.v2
[Jj]amfile [Jj]amfile.jam'.
error: Please consult the documentation at 'http://www.boost.org'.
/usr/share/boost-build/build/project.jam:280: in load-jamfile from
module project
/usr/share/boost-build/build/project.jam:64: in load from module project
/usr/share/boost-build/build/project.jam:89: in load-used-projects from
module project
/usr/share/boost-build/build/project.jam:75: in load from module project
/usr/share/boost-build/build/project.jam:145: in project.find from
module project
/usr/share/boost-build/build-system.jam:535: in load from module
build-system
/usr/share/boost-build/kernel/modules.jam:289: in import from module modules
/usr/share/boost-build/kernel/bootstrap.jam:139: in boost-build from module
/usr/share/boost-build/boost-build.jam:8: in module scope from module

(The explicit '../../..' path above looks quite suspicious, as if
boost.build made assumptions about the directory structure that aren't
met in my stand-alone case.

        Stefan

-- 
      ...ich hab' noch einen Koffer in Berlin...