Issues
- The port was slighly outdated, there was 1.37 in ports and upstream version was 1.39
- It was not possible to control optional python support using OPTIONS framework
- It was not possible to add python support after devel/boost was installed without it (this requires deinstalling of devel/boost and installing devel/boost-python)
- It was possible for one application to depend of devel/boost and for another on devel/boost-python, making them formally incompatible, while they actually depended on the same product
- Boost shared libraries were installed with version 4. It was not clear how that corresponds to 1.37. This number was not modifed since version 1.34. This is incorrect, because boost.org does not provide any binary compatibility between older and newer releases.
Past Efforts
- A set of expirimental non-conflicting ports for boost-1.38 with versioned layout (installs headers into PREFIX/include/boost-1.38/boost and so on) was created. The tarball is at
http://alexanderchuranov.com/boost-port/boost-versioned-20080323.tar.bz2(This link is broken) - A set of non-conflicting ports with system layout (install files where devel/boost does) was created, boost port was split into several complementary ports: boost-jam, boost-libs, boost-python-libs and boost-docs, with boost-all meta-port.
- Boost was updated to 1.39. Tarball with portset may be downloaded from
http://alexanderchuranov.com/boost-port/boost-1.39-split-2009-05-08.tar.bz2(This link is broken) - All ports that depend on devel/boost were modified to depend on one of new ports (boost-libs or boost-python)
- A decision on shared libraries version was made: do not change version at every update. This does not agree with boost.org, because boost.org does not provide binary compatibility between releases. However, rebuilding all ports that depend on boost at each update was condidered non-productive. For details see http://www.mail-archive.com/freebsd-ports@freebsd.org/msg20753.html
- Build process was modified: lbraries do not contain a SONAME with hardcoded release version
- Build process was modified: libraries do contain a SONAME, but without a hardcoded release version
- Many small fixes for issues reported as the result of an exp-run. Updated diff and tarball are at
http://alexanderchuranov.com/boost-port/(This link is broken) - Modified set of ports is checked in!
Fixed Ports
| origin | version | issue | state |
| audio/gx2osd | gx2osd-0.2_2 | Can't find “filesystem” library. | not reproduced with recent version of ports |
| editors/abiword-plugins | abiword-plugins-2.6.8 | pkg_delete can not find 'boost/interprocess/containers/detail' for removal | fixed, tested |
| games/flyhard | flyhard-0.42 | boost/shared_ptr.hpp not found | fixed, tested |
| games/galaxyhack | galaxyhack-1.74_3 | Installed library libboost_filesystem.so requires “system” library with a specified path: bin.v2/libs/system/build/gcc-4.2.1/release/threading-multi/libboost_system.so.1.39.0 | fixed |
| games/lordsawar | lordsawar-0.1.5 | Ports do not see the file “boost/shared_ptr.hpp” and start installing boost-libs, while actually boost-libs package is installed on the system. | fixed |
| games/plee-the-bear | plee-the-bear-0.3.1_1 | Installed library libboost_filesystem.so requires “system” library with a specified path: bin.v2/libs/system/build/gcc-4.2.1/release/threading-multi/libboost_system.so.1.39.0 | fixed |
| games/pokerth | pokerth-0.7 | Installed library libboost_filesystem.so requires “system” library with a specified path: bin.v2/libs/system/build/gcc-4.2.1/release/threading-multi/libboost_system.so.1.39.0 | fixed |
| games/secretmaryochronicles | secretmaryochronicles-1.8 | Configure can not find Boost.Filesystem library. This is probably the same issue as of net-p2p/rblibtorrent | not reproduced when testing |
| graphics/aqsis | aqsis-1.4.2 | Ports do not see the boost_filesystem.4 library, which should be installed into the system by pkg_add. | not reproducible on recent version of ports, tested |
| misc/metalink-tools | metalink-tools-0.3.3_1 | Undefined references to the Boost.System library during build | fixed |
| multimedia/bmpx | bmpx-0.40.14_2 | Configure can not find Boost.Filesystem library. This is probably the same issue as of net-p2p/rblibtorrent | fixed, tested |
| net-p2p/rblibtorrent | rblibtorrent-0.13 | Configure can not find Boost.Filesystem library linking against 'libboost_filesystem-mt.so', which is installed as 'libboost_filesystem.so' | fixed, tested |
| net-p2p/rblibtorrent-devel | rblibtorrent-devel-0.14.3 | Configure can not find Boost.Filesystem library linking against 'libboost_filesystem-mt.so', which is installed as 'libboost_filesystem.so' | fixed |
| print/lyx | lyx-1.4.5.1_1 | Installed library libboost_filesystem.so requires “system” library with a specified path: bin.v2/libs/system/build/gcc-4.2.1/release/threading-multi/libboost_system.so.1.39.0 | fixed |
| print/lyx15 | lyx-1.5.7 | Installed library libboost_filesystem.so requires “system” library with a specified path: bin.v2/libs/system/build/gcc-4.2.1/release/threading-multi/libboost_system.so.1.39.0 | fixed |
| science/avogadro | avogadro-0.9.6 | Can not find Boost.Python library | not reproduced on recent version of ports, tested |
| science/peekabot | peekabot-0.6.0 | cannot find Boost headers version >= 103400 | not reproduced on recent version of ports, tested |
Failures Not Related To Boost
The following is a list of failures, reported during boost ports testing, which are not related to boost ports.
- emulators/open-vm-tools-nox11
- graphics/gdal
- security/openssl
- security/shibboleth2-sp
- x11-toolkits/gigi
- x11/gnome-applets