Trying to build Boost.Python examples from the boost-examples package results in errors. The apparent reason is a wrong path in /usr/share/doc/boost-examples/libs/python/example/boost-build.jam. I'm trying to understand what the proper correction is by discussing with the Boost.Build maintainers, so I haven't anything specific to suggest. (The nature of the issue suggests that this applies to all platforms / versions.) I merely wanted to raise the issue here. (I'm myself maintaining Boost.Python, and I'm trying to figure out what the best way forward is. Ideally I would like to separate Boost.Python out into a stand-alone project (using the rest of Boost as a prerequisite, but otherwise independent), which would also mean that the Boost.Python examples shouldn't be packaged with boost-examples any longer. FWIW.
This message is a reminder that Fedora 23 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 23. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '23'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 23 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
This bug appears to have been reported against 'rawhide' during the Fedora 26 development cycle. Changing version to '26'.
This message is a reminder that Fedora 26 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 26. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '26'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 26 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Shut up, bot.
This bug appears to have been reported against 'rawhide' during the Fedora 29 development cycle. Changing version to '29'.
This message is a reminder that Fedora 29 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 29 on 2019-11-26. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '29'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 29 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
This message is a reminder that Fedora 31 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 31 on 2020-11-24. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '31'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 31 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
/usr/share/doc/boost-examples/libs/python/example/boost-build.jam is no longer packaged. We package README.md and Jamroot from https://github.com/boostorg/python/tree/develop/example and as the README says: This directory contains various examples using Boost.Python. You may compile these using the bjam command either in this directory or in any of the subdirectories. You may need to adjust the paths in the Jamroot file if Boost.Python is not installed in a default location. See http://boostorg.github.io/python/doc/html/building/no_install_quickstart.html for details. If I run b2 in the examples dir I get an error because non-root users can't create files in there: example$ b2 warning: no Python configured in user-config.jam warning: will use default configuration warning: No toolsets are configured. warning: Configuring default toolset "gcc". warning: If the default is wrong, your build may not work correctly. warning: Use the "toolset=xxxxx" option to override our guess. warning: For more configuration options, please consult warning: https://www.bfgroup.xyz/b2/manual/release/index.html#bbv2.overview.configuration /usr/share/boost-build/src/util/path.jam:500: in path.makedirs from module path error: Could not create directory 'bin' /usr/share/boost-build/src/build/configure.jam:479: in configure.set-log-file from module configure /usr/share/boost-build/src/build-system.jam:762: in load from module build-system /usr/share/boost-build/src/kernel/modules.jam:294: in import from module modules /usr/share/boost-build/src/kernel/bootstrap.jam:139: in boost-build from module /usr/share/boost-build/src/kernel/boost-build.jam:5: in module scope from module So we might want to edit the README to suggest copying the files elsewhere. If I do that and run b2 (after installing python3-devel, boost-python3 and boost-numpy3) I get linker errors: /usr/bin/ld: cannot find -lboost_numpy: No such file or directory /usr/bin/ld: cannot find -lboost_python: No such file or directory That's because in Fedora we package them with version-specific names: /usr/lib64/libboost_python311.so /usr/lib64/libboost_numpy311.so I'm not sure if add the 311 suffix or upstream does. To fix this, I think we want the jamfiles to use the library names that match what is actually installed, and we want the README to suggest copying everything to a dir that the user can write to.
(In reply to Jonathan Wakely from comment #8) > I'm not sure if add the 311 suffix or upstream does. s/add/we add/