From: Jakub Jelinek <jakub@redhat.com>
To: Ulrich Drepper <drepper@redhat.com>, Roland McGrath <roland@redhat.com>
Cc: Glibc hackers <libc-hacker@sources.redhat.com>
Subject: [PATCH] Move sched_[sg]etaffinity to GLIBC_2.3.3
Date: Tue, 16 Sep 2003 20:20:00 -0000 [thread overview]
Message-ID: <20030916181834.GP12344@sunsite.ms.mff.cuni.cz> (raw)
Hi!
sched_[gs]etaffinity API was changed after 2.3.2 incompatibly, but
nothing used the old symbols from glibc (AFAIK schedutils use
kernel syscalls directly, so did versions of "run" up to these days).
Better change the symbol version, so that it is clear these symbols
have nothing to do with the old sched_[sg]etaffinity.
2003-09-16 Jakub Jelinek <jakub@redhat.com>
* posix/Versions (sched_getaffinity, sched_setaffinity): Change
from GLIBC_2.3.2 to GLIBC_2.3.3 symbol version.
--- libc/posix/Versions.jj 2002-11-19 20:05:30.000000000 -0500
+++ libc/posix/Versions 2003-09-16 16:05:33.000000000 -0400
@@ -110,14 +110,15 @@ libc {
__nanosleep;
}
GLIBC_2.3.2 {
- sched_getaffinity; sched_setaffinity;
-
# Note that these symbols appear in sysdeps/unix/sysv/linux/Versions
# under GLIBC_2.0; the first instance in the script is taken as the
# default, so linux configurations put them in GLIBC_2.0 while other
# configuration put them in GLIBC_2.3.2.
getresuid; getresgid; setresuid; setresgid;
}
+ GLIBC_2.3.3 {
+ sched_getaffinity; sched_setaffinity;
+ }
GLIBC_PRIVATE {
# functions which have an additional interface since they are
# are cancelable.
Jakub
next reply other threads:[~2003-09-16 20:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-16 20:20 Jakub Jelinek [this message]
2003-09-16 21:00 ` Ulrich Drepper
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20030916181834.GP12344@sunsite.ms.mff.cuni.cz \
--to=jakub@redhat.com \
--cc=drepper@redhat.com \
--cc=libc-hacker@sources.redhat.com \
--cc=roland@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).