On Thursday 10 January 2008 13:52:15 Deanna Phillips wrote: > Neat. Could you please explain the reason for and origin of the > patches to boost code?
BJAM_CONFIG environment variable can be used in CONFIGURE_ENV, as i added SO_VERSION variable to the boost jamfile that defines the version number which is appended to generated shared libraries. it's not perfect but better than none at all. configure and tools/build/v2/tools/gcc.jam we don't have statvfs: libs/filesystem/src/operations.cpp three files needed to be touched to make sure boost_wserialization doesn't get build in any cases: Jamfile.v2, libs/serialization/test/Jamfile.v2 and libs/serialization/build/Jamfile.v2 was passing unnecessary and unfriendly flags for the python module: tools/build/v2/tools/python.jam those two patches are official bug fixes from boost web site: boost/function/function_template.hpp boost/function/function_base.hpp Boost.Function in Boost 1.34.x has a bug that affects the construction of Boost.Function objects in a multi-threaded context. To patch your Boost 1.34.x, copy the files function_base.hpp and function_template.hpp into the Boost directory boost/function. hopefully i got them all covered.
