-
Notifications
You must be signed in to change notification settings - Fork 420
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 master, on Ubuntu 24.04 vanilla #449
Comments
Addendum: Our compile script is as simple as it gets, on a vanilla EC2 Ubuntu 24.04 x64 instance:
|
I have created a Dockerfile to reproduce the issue with different Ubuntu versions and different commits. My findings:
The latter mentioned has changed a lot in CMakeLists.txt without updating BUILDING.md. |
I am able to compile the most recent commit 9b8d11f by adding
Older commits may still fail because of an unlinked math function. Without testing I guess this was fixed in b6e0d50. Disclaimer: I am not experienced enough in C to fully understand all implications introduced by adding |
@erictroebs Thanks for the extra info. Not an experienced C/C++ programmer either, but in a nutshell, the While I don't think this compiler flag should be necessary to build the code since it's not included in the build scripts, it might be a useful clue for the developers to pin-point the source of the problem. Thanks for all the details about how you were able to reproduce. |
We regularly build the
master
branch on vanilla Ubuntu 24.04 on EC2 x64 instances (tonight,ami-04b4f1a9cf54c11d0
/amazon/ubuntu/images/hvm-ssd-gp3/ubuntu-noble-24.04-amd64-server-20250115
inus-east-1
)The last time we successfully did (before it failed tonight) was on 2024-12-18 18:42:26 UTC-0500.
So our problem must be related to one or many of the 7 commits of 3 Jan 2025.
You'll find the last few lines of our compile log below. Please let me know if you need more info.
--
We version pinned on 4.1.1 to work around this, so it's not impairing us.
It's really just a heads up. You may close this issue anytime, we just wanted to make you aware of this issue.
--
The text was updated successfully, but these errors were encountered: