-
Notifications
You must be signed in to change notification settings - Fork 377
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
Add missing include for check_symbol_exists #2831
Conversation
The build fails because of a missing include in cmake: CMake Error at CMakeLists.txt:353 (check_symbol_exists): Unknown CMake command "check_symbol_exists". Include the needed file to fix the issue.
The patch is technically correct of course, but I'm curious: what cmake version is failing due to this? Because the project is certainly building fine on several platforms/distros as is. |
I'm using Fedora 39:
|
Huh. That's where our CI is building every PR on the project, and what I use locally. Without seeing any errors from this. Can you provide a full reproducer for getting to that failure, I'd like to try and understand what's going on here. |
Sure, this is what happens with a fresh clone:
|
This seems pretty bizarre, all I get is
And that's how it goes in all our CI builds, Fedora packages and so on. Do you have any cmake-related environment variables set, or something like that? Can you reproduce on another user account? Apologies for the "interrogation" on what's a correct patch, but if there's a setting somewhere that makes cmake more strict for mistakes like this one then we should have it enabled. And if it's something else, I sure would like to understand what. |
This is a fresh boot of the Fedora arm64 image available for download here: I'm using it only to build RPM in a VM (my host is an Apple ARM notebook) |
Oh okay, arm64, that's a difference. But then it doesn't happen on Fedora koji builds on that platform, eg here: https://kojipkgs.fedoraproject.org//packages/rpm/4.19.1/1.fc39/data/logs/aarch64/build.log Could be a difference in installed packages perhaps, maybe there's a cmake module that "leaks" its own include of that file or something like that. Oh well. Thanks for the patch! |
The build fails because of a missing include in cmake:
Include the needed file to fix the issue.