I did this workaround: * edit build/boost/src/Boost/project-config.jam * change --with-python310 to --with-python in 'libraries' * rebuild On 17/11/21 05:42, Pete Zaitcev wrote:
Hello: I am following directions in README.md and hit the following. $ cd build $ ninja [128/2107] Performing build step for 'Boost' FAILED: boost/src/Boost-stamp/Boost-build boost/lib/libboost_atomic.a boost/lib/libboost_chrono.a boost/lib/libboost_thread.a boost/lib/libboost_system.a boost/lib/libboost_date_time.a boost/lib/libboost_regex.a boost/lib/libboost_random.a boost/lib/libboost_program_options.a boost/lib/libboost_iostreams.a boost/lib/libboost_context.a boost/lib/libboost_coroutine.a boost/lib/libboost_python310.a boost/lib/libboost_filesystem.a boost/lib/libboost_container.a /home/zaitcev/ceph/ceph-srbac/build/boost/src/Boost-stamp/Boost-build /home/zaitcev/ceph/ceph-srbac/build/boost/lib/libboost_atomic.a [....... gazillion of libraries .......] /home/zaitcev/ceph/ceph-srbac/build/boost/lib/libboost_coroutine.a /home/zaitcev/ceph/ceph-srbac/build/boost/lib/libboost_python310.a /home/zaitcev/ceph/ceph-srbac/build/boost/lib/libboost_filesystem.a /home/zaitcev/ceph/ceph-srbac/build/boost/lib/libboost_container.a cd /home/zaitcev/ceph/ceph-srbac/build/boost/src/Boost && CC=/usr/bin/cc CXX=/usr/bin/c++ ./b2 -j1 -d0 --user-config=/home/zaitcev/ceph/ceph-srbac/build/user-config.jam toolset=gcc headers stage variant=release threading=multi link=static address-model=64 "cxxflags=-fPIC -w" && /usr/bin/cmake -E touch /home/zaitcev/ceph/ceph-srbac/build/boost/src/Boost-stamp/Boost-build error: wrong library name 'python310' in the --with-<library> option. [... ninja continues parallel builds ...] added 2835 packages in 541.617s ninja: build stopped: subcommand failed. [zaitcev@lembas build]$ echo $? 1 [zaitcev@lembas build]$ Not sure what to do about this. Can we build using system Boost? It is a well-known library. It should not be necessary to build a fork for ourselves. I started with ./install-deps.sh, which did not install boost-devel. Should I just install it myself? And then how do I tell cmake that I have it? -- Pete _______________________________________________ Dev mailing list -- dev@xxxxxxx To unsubscribe send an email to dev-leave@xxxxxxx
_______________________________________________ Dev mailing list -- dev@xxxxxxx To unsubscribe send an email to dev-leave@xxxxxxx