From: "John W. Linville" <linville@tuxdriver.com>
To: MIPS Linux List <linux-mips@linux-mips.org>
Subject: glibc 2.3.3 patches for mips?
Date: Wed, 6 Oct 2004 19:38:43 -0400 [thread overview]
Message-ID: <20041006233841.GA13351@tuxdriver.com> (raw)
Anyone here using glibc 2.3.3 on mips? I had trouble using crosstool to
build a gcc_3.3.3-glibc_2.3.3 combination. gcc_3.3.3-glibc_2.3.3 seems
to have built fine, although I haven't done much testing of the
binaries...
If anyone is using glibc_2.3.3, what patches (if any) did you use to get
it going?
Thanks,
John
--
John W. Linville
linville@tuxdriver.com
next reply other threads:[~2004-10-06 23:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-06 23:38 John W. Linville [this message]
2004-10-06 23:53 ` glibc 2.3.3 patches for mips? David Daney
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=20041006233841.GA13351@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=linux-mips@linux-mips.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