From: Pete Popov <ppopov@pacbell.net>
To: Steven Liu <stevenliu@psdc.com>
Cc: linux-mips@oss.sgi.com
Subject: Re: glibc
Date: Wed, 15 Aug 2001 14:05:02 -0700 [thread overview]
Message-ID: <3B7AE3FE.1070103@pacbell.net> (raw)
In-Reply-To: 84CE342693F11946B9F54B18C1AB837B0A248C@ex2k.pcs.psdc.com
Steven Liu wrote:
> Hi, ALL:
>
> I am porting Linux version 2.2.12 to Mips R3000 and need to build glibc
> but I could not find the following files:
>
> glibc-2.0.6.tar.gz
> glibc-crypt-2.0.6.tar.gz
> glibc-localedata-2.0.6.tar.gz
> glibc-linuxthreads-2.0.6.tar.gz
> glibc-2.0.6-mips.patch
>
> If anyone know the place I caould get the files and let me know, I would
> be greatly appreciated.
Why are you porting 2.2.12? 2.4 is much more easy to port and there's already
pretty good support for a number of different boards. The tools and glibc
(2.2.3) are ready and available from a few places. And, you are much more likely
to get help from someone with the 2.4 kernel, since that's what everyone seems
to be using. As soon as your 2.2.12 port is done, it will be dead. Who are you
going to submit it to? Just my 2c anyway.
Pete
next prev parent reply other threads:[~2001-08-15 21:02 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-15 20:45 glibc Steven Liu
2001-08-15 20:45 ` glibc Steven Liu
2001-08-15 21:05 ` Pete Popov [this message]
[not found] <no.id>
2001-08-15 20:58 ` glibc Alan Cox
2001-08-15 20:58 ` glibc Alan Cox
2001-08-16 8:50 ` glibc Brian Murphy
2001-08-16 14:04 ` glibc Alan Cox
2001-08-16 14:04 ` glibc Alan Cox
2001-08-16 16:14 ` glibc Ralf Baechle
2001-08-16 19:09 ` glibc Martin Michlmayr
2001-08-16 20:05 ` glibc James Simmons
2001-08-16 20:10 ` glibc Soeren Laursen
2001-08-16 16:04 ` glibc H . J . Lu
2001-08-16 17:00 ` glibc Brian Murphy
2001-08-16 21:15 ` glibc H . J . Lu
-- strict thread matches above, loose matches on Subject: below --
2001-08-15 21:31 glibc Siders, Keith
2001-08-15 21:38 ` glibc Ilya Volynets
2001-08-15 21:37 glibc Siders, Keith
2001-08-15 22:03 glibc Siders, Keith
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=3B7AE3FE.1070103@pacbell.net \
--to=ppopov@pacbell.net \
--cc=linux-mips@oss.sgi.com \
--cc=stevenliu@psdc.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