From: Jakub Jelinek <jakub@redhat.com>
To: Ulrich Drepper <drepper@redhat.com>
Cc: Roland McGrath <roland@redhat.com>,
GNU libc hackers <libc-hacker@sources.redhat.com>
Subject: Re: vm86 system call update
Date: Wed, 03 Dec 2003 00:09:00 -0000 [thread overview]
Message-ID: <20031202220436.GQ12344@sunsite.ms.mff.cuni.cz> (raw)
In-Reply-To: <3FCD28A0.7090306@redhat.com>
On Tue, Dec 02, 2003 at 04:04:48PM -0800, Ulrich Drepper wrote:
> > -vm86 - vm86 i:p __vm86 vm86
> > +vm86old EXTRA vm86old i:p __vm86old vm86@GLIBC_2.0
> > +vm86 - vm86 i:ip __vm86 vm86@GLIBC_2.3.3
>
> This generates wrong code for very old kernels which name have no
> vm86old (and name the old version vm86). We can bump the minimum kernel
> requirement, I'd have no problem with that.
That is only about the kernel headers you compile glibc against.
I doubt glibc would build against say 2.2.x kernel headers but I see
no reason why it shouldn't work on 2.2.5 kernel.
Jakub
next prev parent reply other threads:[~2003-12-03 0:09 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 [this message]
2003-12-03 0:27 ` Ulrich Drepper
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=20031202220436.GQ12344@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).