Boost failed updating 56 targetsdie "Building of Boost libraries failed"; * * If you need support, post the output of `emerge --info '=dev-libs/boost-1.56.0-r1::gentoo'`, * the complete build log and the output of `emerge -pqv '=dev-libs/boost-1.56.0-r1::gentoo'`.
Looking at the jamfile it seems like the previously used create-library rule had all the handling for that while the new ac.check-library probably isn't even aware of these parameters.
Reverting the changes to the Jam files allows using the custom zlib version again.
https://github.com/boostorg/iostreams/commit/dfb1f61c26b77556a1cca0654d08847cf87d26ae This commit broke the ability to build boost with without zlib. gcc.compile.c bin.v2/libs/iostreams/build/gcc-4.8/release/link-static/threading-multi/bzip2.o libs/iostreams/src/bzip2.cpp:: fatal error: bzlib.h: No such file or directory #include "bzlib.h" // Julian Seward's "bzip.h" header. "g " -ftemplate-depth-128 -O3 -finline-functions -Wno-inline -Wall -pthread -DBOOST_ALL_NO_LIB=1 -DBOOST_IOSTREAMS_USE_DEPRECATED -DNDEBUG -I"." -c -o "bin.v2/libs/iostreams/build/gcc-4.8/release/link-static/threading-multi/bzip2.o" "libs/iostreams/src/bzip2.cpp" ...failed gcc.compile.c bin.v2/libs/iostreams/build/gcc-4.8/release/link-static/threading-multi/bzip2.o...
...skipped # find /usr -name pyconfig.h /usr/include/python3.4m/pyconfig.h /usr/include/multiarch-i386-linux/python3.4m/pyconfig.h /usr/include/multiarch-i386-linux/python2.7/pyconfig.h /usr/include/python2.7/pyconfig.h # find /usr -name pyconfig.h /usr/include/python3.4m/pyconfig.h /usr/include/multiarch-i386-linux/python3.4m/pyconfig.h /usr/include/multiarch-i386-linux/python2.7/pyconfig.h /usr/include/python2.7/pyconfig.h ...updated 68 targets... The following directory should be added to compiler include paths: /home/gg/Downloads/DOWNLOAD/test/boost_1_57_0 The following directory should be added to linker library paths: /home/gg/Downloads/DOWNLOAD/test/boost_1_57_0/stage/lib I tried add before " $(prefix)/include : python$(version)* " but python libs missed ( libboost_python ) and I con not find error. I ask because I see ./can add only 1 python version to for local file_name in glob.glob("/include/python*/Python.h".format(version=$(version), prefix=$(prefix))) # file_name = /usr/include/python3.4m/Python.h includes ? = /usr/include/python3.4m ; This still appears to be an issue in Boost 1.59.0, I found this report when searching for my problem.
Or maybe I'm just completely misunderstanding it which is always possible.
./--with-python=/usr/bin/python3 --with-python-root=/usr ./b2 ... gcc.compile.c bin.v2/libs/python/build/gcc-4.9.2/release/threading-multi/object/function_doc_signature.o In file included from ./boost/python/detail/prefix.hpp:13:0, from ./boost/python/converter/registrations.hpp:8, from libs/python/src/object/function_doc_signature.cpp:9: ./boost/python/detail/wrap_python.hpp:: fatal error: pyconfig.h: No such file or directory # include ^ compilation terminated.
note: to enable them, add "using mpi ;" to your error: at /home/ubuntu/build/boost_1_54_0/tools/build/v2/kernel/modules.jam:107 error: Unable to find file or target named error: '/zlib//zlib' error: referred to from project at error: 'libs/iostreams/build' error: could not resolve project reference '/zlib' Performing configuration checks - zlib : no (cached) - zlib : no (cached) Component configuration: - atomic : not building - chrono : not building - container : not building - context : not building - coroutine : not building - date_time : not building - exception : not building - filesystem : not building - graph : not building - graph_parallel : not building - iostreams : building - locale : not building - log : not building - math : not building - mpi : not building - program_options : not building - python : not building - random : not building - regex : not building - serialization : not building - signals : not building - system : not building - test : not building - thread : not building - timer : not building - wave : not building ...patience... Setting ZLIB_BINARY, ZLIB_INCLUDE and ZLIB_LIBPATH previously allowed to specify an externally compiled version of zlib with custom binary name.
These options seem to no longer have any effect on the build configuration resulting in zlib not being found and disabled.