Martin Costabel wrote:
The boost1.32-pyXX-1.32.0-2 package is built --without-python and does
not build libboost_python-*.dylib. As a reason, the package description
says
NB - Boost.Python isn't built because a bug in Apple's version of gcc
causes a deadlock when Boost.Python extensions are imported into Python
This statement dates from before the arrival of gcc-4.0, but it is still
present in the 10.4-transitional package. Does anyone remember what the
symptoms of this problem were? Is the problem solved now?
I am asking because I would like to update the visual-py23 package, and
the new version (which has been out for many months BTW) uses
libbost_python.dylib. Its build instructions propose to build first a
special version of gcc-3.4.3 and then use this to build libboost_python.
I would like to avoid this and use gcc-4.0 instead, or rather Fink's
boost if possible.
Having received no response, I have now moved on and done the following:
- I upgraded visual-py23 to the new version 3.2.1 that uses boost (and
versionalized it, so there is now also a visual-py24, and both can be
installed at the same time).
- I made a new package boost1.32.python with a -shlibs splitoff. This
supplies the libboost.python library that is missing from the
boost1.32-pyXY package. It coexists with the latter, and actually
visual-pyXY builddepends on both, because of header files.
I preferred to make a new add-on package (using the same sources and
almost the same patch file) instead of fixing the old boost1.32-pyXY
one, because fixing it would take more than just enabling the building
of the python libraries. Maybe when a new boost1.33 package will be
made, we can simplify this and reintegrate everything.
Right now, I don't want to touch the architecture of the boost1.32-pyXY
packages, although I think it is wrong: The -py23 and -py24 variants
build exactly the same files (identical binaries), so they conflict, but
the -shlibs splitoffs don't and cannot Conflicts and Replaces each
other. I understand why there are 2 variants (because we have 2 pythonXY
executables in Fink and no one wants to settle on only one), but I think
there should be no variant. The package can actually be built using
Apple's python, and the result is exactly identical AFAICT to what one
gets with python23 or with python24. There are no version-specific
python directories involved here. I am saying this, however, only for
the record and for future considerations. For the moment:
Please do *not* improve or fix or otherwise change the boost1.32-py
package now. If anyone wants to use the boost.python libraries, then
they should install one of the two boost1.32-py2[3|4]-1.32.0-2 packages
plus the new boost1.32.python-1.32.0-11 package. For an upcoming
boost1.33 package, I suggest to put all this together in one package
(plus -shlibs splitoff) and drop any variants.
--
Martin
-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
_______________________________________________
Fink-devel mailing list
Fink-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/fink-devel
