-
-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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
glibc: guard more function declarations #22771
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.
I checked the version guards with the release notes, and they all look good. Your commit summary mentions close_range
is in v2.36, but the diff and the truth are v2.34.
While reading the v2.39 release notes, I noticed pidfd_spawn
and pidfd_spawnp
were also added (in lib/libc/include/generic-glibc/bits/spawn_ext.h
), if you want to cover a couple more while you're here ... But feel free to leave these for later/never.
I'm not a deputized reviewer, so feel free to ignore me.
13fc810
to
04bd6ed
Compare
It is only available starting from glibc 2.34
It was added in glibc 2.28
04bd6ed
to
2c59b3b
Compare
Thank you both for your reviews! All comments should be addressed now |
2c59b3b
to
edee702
Compare
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.
LGTM, but I'm just a drive-by reviewer.
Guard the declaration of:
close_range
(introduced in 2.34)statx
(introduced in 2.28)fsopen
,fsmount
,move_mount
,fsconfig
,fspick
,open_tree
,mount_setattr
(introduced in 2.36)pidfd_open
,pidfd_getfd
,pidfd_send_signal
(introduced in `2.36)pidfd_getpid
(introduced in 2.39)This fixes building util-linux
while targeting glibc
2.17` (or any version prior to 2.39)