Re: [Visualpython-users] Help with Boost on Mac OS

[Bruce S. <Bru...@nc...>]

Note in the CVS file MAC-OSX.txt (which is somewhat out of date) these 
comments, which may or may not be relevant to your problem:

Before making a change to src/Makefile.in, I got a message about 
possible mismatch of versions,
as though when I build against /sw/bin/python2.5 and then run 
/sw/bin/python2.5 the system thinks
these are different pythons. Martin Costabel commented:

"I am getting this, too, when using the dynamic boost-python library, 
but not with the static
libboost_python-mt.a. This is certainly a bug with the 
libboost_python-mt.dylib, but I haven't
yet found a combination of build flags to build it correctly, in 
particular in a way that would
also work on OSX 10.5."

Following his suggestion, I put Mac-specific code into src/Makefile.in 
to link to these other
libraries. But then I got this error message in the link phase of the make:

/usr/bin/ld: table of contents for archive: /sw/lib/libboost_python-mt.a 
is out of date; rerun ranlib(1) (can't load from it)

So I executed ranlib /sw/lib/libboost_python-mt.a, redid the make, 
executed make install, and it worked.

Bruce

Hugh Fisher wrote:
> I'm just starting to fill in the stubs for my native Mac
> OS Carbon version of VPython, which in turn seems to be
> triggering previously hidden Boost errors. Things like
> 	bool check() const;
> in boost/python/extract.hpp are being reported as errors
> by Xcode 'doesn't declare anything'
> 
> I downloaded the Boost 1_34_1 sources and bjam, did a
> bjam build and then bjam install. If that wasn't enough,
> I have absolutely no idea how to proceed.
> 
> Can anybody point me to either a nice prebuilt installer
> for Boost on MacOS, or at least some detailed instructions
> on pitfalls and how to avoid them?
>