Re: [Visualpython-users] Release: VPython 2.9.4

[Jonathan B. <jbr...@ea...>]

On Mon, 2004-06-14 at 04:14, Martin Costabel wrote:
> Jonathan Brandmeyer wrote:
> []
> > OSX.  3.3.x (x >= 1) should be fine.
> > 
> > I have attached mkdist_osx.sh, which has been slightly updated from what
> > is in the .tar.bz2 file on Sourceforge.  Hopefully, that will give you a
> > good starting point.  If you have any questions at all, feel free to
> > ask.
> 
> I am not yet quite there. I first tried a gcc-3.5.0 snapshot whose 
> sources I had lying around (it is used for the Fink gfortran package). 
> This didn't work. It produced internal compiler errors. 

Gaaa!  GCC from stage 1?  You are far braver than I.  Besides,
Boost.Python needed a few patches to work with the new (and more strict)
C++ front-end that was released with GCC 3.4, and those patches are not
available in the 1.31.0 release.  That's why I specifically recommended
3.3.  3.3.0 had other bugs in it that lead to ICE in the compiler on all
platforms.

> They are caused by the fact that these symbols are contained in 
> libboost_python.dylib, but as non-external. Did you build Boost.Python 
> only with static libraries, or do you have an idea how to upgrade these 
> symbols
> 
> 00091340 s typeinfo for boost::python::instance_holder
> 000913a8 s typeinfo for boost::python::objects::py_function_impl_base
> 
> from "non-external (was a private external)" to external?

Yes.  Add -DBOOST_PYTHON_DYNAMIC_LIB to BOOSTFLAGS when building
libboost_python.dylib.  My mistake.


> > If you manage to get a set of working .debs, and you don't want to force
> > folks to upgrade to the unstable 2.9 version yet, I would be happy to
> > put them up on Sourceforge alongside the other packages.
> 
> There is a version 2.1.9 .deb in the Fink binary distribution (no boost 
> needed for this, but had to be compiled with gcc-3.1, as you may 
> remember). http://fink.sourceforge.net/pdb/package.php/visual-py23

Yes, I remember.  I was merely offering to help with a setup that
wouldn't force someone who is already using your 2.1.9 visual-py23
package to upgrade to the not-quite-stable 2.9 version.