-
Notifications
You must be signed in to change notification settings - Fork 219
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
feat: Add manylinux_2_34 image #1698
base: main
Are you sure you want to change the base?
Conversation
29bdc85
to
48669de
Compare
manylinux_2_34 (AlmaLinux 9 based) | ||
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ | ||
|
||
Toolchain: GCC 13 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Didn't you say in #1585 that you'd want to start off with GCC 14?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I said that "I'd like to wait" but if I don't get some sort of planning/roadmap for availability (it's been in stream 9 for a while now but the fact that it's nowhere else requires more investigation on why), we might want to start with 13 & update later on.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Digging a bit more into this I only could find that there's some on-going work in RHEL bug tracker. It seems they're already using it in a staging area but still finding bugs and reworking if I understand correctly. I have not found any kind of planning around this.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Makes sense. 👌
We're also using GCC 13 in conda-forge until GCC 15 is released, for pretty much those reasons (picking up all the bugfixes over the course of a year leading up to the next major version).
8bc6a94
to
d88418f
Compare
d88418f
to
2bdd641
Compare
2bdd641
to
caec6d5
Compare
based on #1672
close #1575