From: Ralf Baechle <ralf@linux-mips.org>
To: Neo <cjia@cse.unl.edu>
Cc: linux-mips@linux-mips.org
Subject: Re: How to build the glibc for MIPS?
Date: Fri, 29 Sep 2006 01:02:33 +0100 [thread overview]
Message-ID: <20060929000233.GG3394@linux-mips.org> (raw)
In-Reply-To: <451C537B.7060507@cse.unl.edu>
On Thu, Sep 28, 2006 at 05:58:03PM -0500, Neo wrote:
> I have successfully built the cross toolchain excluding glibc following
> the steps of www.linux-mips.org. Now, I am wondering how to build the
> glibc for MIPS. The websites provided by linux-mips are not accessible
> any more or they cannot be built successfully.
Are you refering to the instructions in the old MIPS-HOWTO document?
I've asked LDP to remove it because it was so obsolete. Building glibc
has fortunately become much easier these days; it's mostly a question of
getting the build environment right.
Ralf
next prev parent reply other threads:[~2006-09-29 0:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-28 22:58 How to build the glibc for MIPS? Neo
2006-09-29 0:02 ` Ralf Baechle [this message]
2006-11-22 10:54 ` Mile Davidovic
2006-11-22 10:54 ` Mile Davidovic
2006-11-22 12:55 ` sjhill
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=20060929000233.GG3394@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=cjia@cse.unl.edu \
--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