From: Ulrich Drepper <drepper@redhat.com>
To: GNU libc hackers <libc-hacker@sources.redhat.com>
Subject: Re: vm86 system call update
Date: Wed, 03 Dec 2003 00:27:00 -0000 [thread overview]
Message-ID: <3FCD2DB3.6020901@redhat.com> (raw)
In-Reply-To: <20031202220436.GQ12344@sunsite.ms.mff.cuni.cz>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Jakub Jelinek wrote:
> That is only about the kernel headers you compile glibc against.
Of course. But nominally we still support 2.0.x kernels, even for
compiling. Nobody tried it, of course. Bumping the compile-time
requirement to 2.2.SOMETHING should be OK.
- --
➧ Ulrich Drepper ➧ Red Hat, Inc. ➧ 444 Castro St ➧ Mountain View, CA â–
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (GNU/Linux)
iD8DBQE/zS2z2ijCOnn/RHQRApktAKCXO5pni/hhv6iqvxeDIUwb+UobKwCcDzqD
svNEaE9RO7IQDDslxalJzg4=
=9HNh
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2003-12-03 0:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-02 23:49 Roland McGrath
2003-12-03 0:05 ` Ulrich Drepper
2003-12-03 0:09 ` Jakub Jelinek
2003-12-03 0:27 ` Ulrich Drepper [this message]
2003-12-03 0:12 ` Roland McGrath
2003-12-03 0:24 ` Ulrich Drepper
2003-12-03 0:13 ` Roland McGrath
2003-12-03 15:49 Steven Munroe
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=3FCD2DB3.6020901@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).