diff options
Diffstat (limited to 'dev-libs/boost/files/boost-1.48.0-python_linking.patch')
| -rw-r--r-- | dev-libs/boost/files/boost-1.48.0-python_linking.patch | 24 |
1 files changed, 0 insertions, 24 deletions
diff --git a/dev-libs/boost/files/boost-1.48.0-python_linking.patch b/dev-libs/boost/files/boost-1.48.0-python_linking.patch deleted file mode 100644 index e7f4e7c..0000000 --- a/dev-libs/boost/files/boost-1.48.0-python_linking.patch +++ /dev/null @@ -1,24 +0,0 @@ ---- libs/python/build/Jamfile.v2 -+++ libs/python/build/Jamfile.v2 -@@ -109,20 +109,7 @@ - <link>static:<define>BOOST_PYTHON_STATIC_LIB - <define>BOOST_PYTHON_SOURCE - [ cond $(python2) : <cxxflags>-fno-strict-aliasing ] -- -- # On Windows, all code using Python has to link to the Python -- # import library. -- # -- # On *nix we never link libboost_python to libpython. When -- # extending Python, all Python symbols are provided by the -- # Python interpreter executable. When embedding Python, the -- # client executable is expected to explicitly link to -- # /python//python (the target representing libpython) itself. -- # -- # python_for_extensions is a target defined by Boost.Build to -- # provide the Python include paths, and on Windows, the Python -- # import library, as usage requirements. -- [ cond [ python.configured ] : <library>/python//python_for_extensions ] -+ [ cond [ python.configured ] : <library>/python//python ] - - # we prevent building when there is no python available - # as it's not possible anyway, and to cause dependents to |