From: Daniel Jacobowitz <dan@debian.org>
To: Disconnect <lkml@sigkill.net>
Cc: lkml <linux-kernel@vger.kernel.org>
Subject: Re: glibc+sysenter sources..?
Date: Wed, 9 Apr 2003 17:10:43 -0400 [thread overview]
Message-ID: <20030409211042.GA29819@nevyn.them.org> (raw)
In-Reply-To: <1049913600.18782.24.camel@sparky>
On Wed, Apr 09, 2003 at 02:40:00PM -0400, Disconnect wrote:
> I found the binaries (ftp://people.redhat.com/drepper/glibc/2.3.1-25/)
> but the sources don't seem to be available. (That makes it hard to
> test, since my 2.5 system is running debian..)
>
> Preferable would be a patch against the standard 2.3.1 (rather than one
> against the redhat sources) but I can probably detangle it if needed.
>
> Also, has this been tested under SMP or am I forging new ground? (dual
> ppro 200 system under 2.5.66-bk10.)
Just get a recent version of glibc. 2.3.2 includes the patches, I
think. That'll be in Debian/unstable in another week or so I bet.
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2003-04-09 20:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-09 18:40 glibc+sysenter sources..? Disconnect
2003-04-09 21:10 ` Daniel Jacobowitz [this message]
2003-04-10 18:08 ` Disconnect
2003-04-10 21:00 ` Steven Cole
2003-04-10 21:06 ` Disconnect
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=20030409211042.GA29819@nevyn.them.org \
--to=dan@debian.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkml@sigkill.net \
/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 NNTP newsgroup(s).