Re: [boost] Experience with Boost.Build

From: Steve M. Robbins (steven.robbins_at_[hidden])
Date: 2002-02-21 22:54:21

On Thu, Feb 21, 2002 at 08:21:29PM -0700, Dan Nuffer wrote:

> - The Boost.Python build failed.  I don't know for sure since Jam 
> doesn't print the command it's running, but judging from the gcc error 
> messages, the Python headers were not found (they are in a standard 
> place - /usr/include/python1.5, so why weren't they found?) 

The build assumes /usr/local/include/python1.5 unless you tell it
otherwise.  I believe "jam -sPYTHON_ROOT=/usr" should work.

> It would be 
> nice if Jam would print out the command it invoked so I could tell what 
> was happening.

You can get a list of the commands jam will run using "jam -o/tmp/trace".

 
> - The only library that appears to have sucessfully built was regex. 
>  It's the only .so file.  There are some .o files for the thread 
> library, but no .so or .a.  Searching back through the ton of error 
> messages I found this:
> libs/thread/build/../src/once.cpp:138: parse error at end of input
> Is there a way to get Jam to stop once an error happens?  It would make 
> it a lot easier to find any errors!
> Boost.Python failed because the build didn't look in the right place for 
> the headers.
> How do I fix either of these problems?

The file once.cpp has a stray "extern "C" {" that you can just remove.

-Steve 

-- 
by Rocket to the Moon,
by Airplane to the Rocket,
by Taxi to the Airport,
by Frontdoor to the Taxi,
by throwing back the blanket and laying down the legs ...
- They Might Be Giants