-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Build error on Arch Linux - 'Could not find a package configuration file provided by "boost_signals"' #1
Comments
Looks like you're trying to build the master branch - I don't recommend using it as there is a lot of development happening there at the moment, so it may be unstable. It's best to stick to releases, the most recent one (0.16.1) will not trigger this specific error you've encountered. But if you really want to compile master branch, then you'll need the |
Thanks for the feedback. I indeed have I just did a bit more googling and found a similar error on another Arch package, which has a reply comment noting it means it "Tries to use Boost.Signals, which was removed in Boost 1.69.0". (FWIW, if I do I use a lot of -git packages so I'm used to living on the bleeding edge. I'll be mindful that master head might not be in a buildable state at times. |
I use I generally keep Once I get to setting up a CI config, I think I should be able to ensure master can be built on Arch; though obviously my testing recipe will not account for whatever customizations a user might have in their system. |
https://www.boost.org/users/history confirms "Discontinued Libraries: Signals." in 1.69.0 in Dec '18. |
Correct, that's because I have prepared a temporary branch |
A-ha, thanks! Trying it but it errors out with;
I see now, ta, that signals2 is part of the
|
I was able to reproduce this issue in a docker container from Interestingly, some components (e.g. system, filesystem, fiber, log) get found correctly. Others (like signals2, hana, heap, uuid, algorithm) do not get detected. I'll try tracing the CMake module for Boost to see how exactly does it search for these components. |
Right, so CMake detects that boost on Arch was built with CMake config support, and therefore it does not search for these libraries directly, but looks for pre-build configurations in |
Alright - this is simply because signals2 is a header-only library (I was fooled by Debian's package, because it also contains an |
The text was updated successfully, but these errors were encountered: