-
Notifications
You must be signed in to change notification settings - Fork 519
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
update glibc to 2.38 #3355
update glibc to 2.38 #3355
Conversation
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.
Did a quick sanity check. Built an aws-k8s-1.27
variant and joined to an EKS cluster. Node joined and reported healthy. All kube-system
pods looked good and were in a Running
state. Ran sonobuoy quick test which passed.
Nothing stood out as odd or obviously wrong in the updated patches. Looks good to me.
Housekeeping changes: * Drop post-release patches for glibc 2.37, and add patches for 2.38. * Keep the `localedef` hack working with one more hack. * Remove unsupported configure options, and add new ones to disable building `nscd` rather than just excluding it from packaged files. * Include libmvec for all architectures, since it's now supported on aarch64. Functional changes: * `--enable-multi-arch` to include microarch-optimized functions in the same DSO. This trades off a small amount of disk space and RAM to provide optimized versions of some string and memory functions. (This feature was disabled by accident in the original packaging.) * `--enable-fortify-source` to build with the maximum supported level of `_FORTIFY_SOURCE` when possible. Currently, this is "2", but will be "3" when we update to GCC 12. Signed-off-by: Ben Cressey <[email protected]>
⬆️ force pushes add recent patches (and fix a blunder with the local 9001 patch) |
Issue number:
#3170
Description of changes:
Housekeeping changes:
localedef
hack working with one more hack.building
nscd
rather than just excluding it from packaged files.aarch64.
Functional changes:
--enable-multi-arch
to include microarch-optimized functions inthe same DSO. This trades off a small amount of disk space and RAM
to provide optimized versions of some string and memory functions.
(This feature was disabled by accident in the original packaging.)
--enable-fortify-source
to build with the maximum supported levelof
_FORTIFY_SOURCE
when possible. Currently, this is "2", butwill be "3" when we update to GCC 12.
Testing done:
Tested AWS and VMware variants, with this change alone and in combination with other recent commits. Nodes all came up healthy and ran containers.
Terms of contribution:
By submitting this pull request, I agree that this contribution is dual-licensed under the terms of both the Apache License, version 2.0, and the MIT license.