public inbox for libc-hacker@sourceware.org
 help / color / mirror / Atom feed
From: Ulrich Drepper <drepper@redhat.com>
To: GNU libc hacker <libc-hacker@sources.redhat.com>
Subject: abilist problems
Date: Mon, 24 Mar 2003 19:40:00 -0000	[thread overview]
Message-ID: <3E7F58D5.4020602@redhat.com> (raw)

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

I have some big problems with the current abilist implementation.  glibc
always allowed to compile against different kernel headers and have the
resulting binary reflect the kernel the headers are taken from.  This
can cut down on runtime tests for functionality which is known to not be
available since an old kernel is used.

The abilist check causes all such builds to fail.  Syscalls which are
listed only in syscalls.list and are not available in the kernel headers
will have no code created for them.  This in turn obviously results in
differences to the interface.

I see two ways out:

- - make the abilist check optional and/or figure out how to determine
  when the tests can be made mandatory.  E.g., if the kernel header
  version is more recent than x.y.z, make the tests mandatory.

- - create stubs for the syscalls which are not announced in the kernel
  headers.


I probably have a preference for the second solution.  Any volunteer to
hack something?

- -- 
- --------------.                        ,-.            444 Castro Street
Ulrich Drepper \    ,-----------------'   \ Mountain View, CA 94041 USA
Red Hat         `--' drepper at redhat.com `---------------------------
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)

iD8DBQE+f1jV2ijCOnn/RHQRAq93AKCzVJcJDhg5CE/jy5UmvVZusBrD5QCgneZk
YdoDceoehTxT7UyPbfjaoKQ=
=2/qU
-----END PGP SIGNATURE-----

             reply	other threads:[~2003-03-24 19:13 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-24 19:40 Ulrich Drepper [this message]
2003-03-24 19:46 ` Andreas Jaeger
2003-03-24 19:48   ` Ulrich Drepper
2003-03-26  1:02 ` Roland McGrath
2003-03-27  0:20   ` Ulrich Drepper
2003-03-27 11:11     ` Roland McGrath
2003-03-26  3:22 Roland McGrath
2003-03-27  0:59 Steven Munroe
2003-03-27  2:46 ` Ulrich Drepper
2003-03-27 13:15 ` Andreas Schwab

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=3E7F58D5.4020602@redhat.com \
    --to=drepper@redhat.com \
    --cc=libc-hacker@sources.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).