From: Carlos O'Donell <carlos@baldric.uwo.ca>
To: parisc-linux@lists.parisc-linux.org
Subject: [parisc-linux] glibc + SuSE (When email becomes to much)
Date: Wed, 20 Nov 2002 14:49:24 -0500 [thread overview]
Message-ID: <20021120194924.GA26804@systemhalted> (raw)
pa,
I remember someone posting an email about trying
to build an unpatched version of glibc 2.3.1 :)
I have the patches required to build glibc 2.3.1,
if this person is still interested, please email
me or the list.
Actually, 5 of the 8 patches I have are now in upstream
glibc... so you need very little to get upstream
building (gcc-3.2 and new binutils).
My incoming email gets very filtered these days,
and if you're in the queue for more than 30 days
it's likely that I'll forget... unless you have
physical presence in my life or frequent IRC
(e.g. Red haired vixens (real life), or Tausq (IRC) :)
c.
next reply other threads:[~2002-11-20 19:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-20 19:49 Carlos O'Donell [this message]
2002-11-21 6:53 ` [parisc-linux] glibc + SuSE (When email becomes to much) jsoe0708
2002-11-21 7:39 ` jsoe0708
2002-11-21 16:05 ` John David Anglin
2002-11-22 17:00 ` jsoe0708
2002-11-22 17:30 ` John David Anglin
2002-11-25 2:55 ` Carlos O'Donell
2002-11-25 7:45 ` jsoe0708
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=20021120194924.GA26804@systemhalted \
--to=carlos@baldric.uwo.ca \
--cc=parisc-linux@lists.parisc-linux.org \
/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