From: "Steven J. Hill" <sjhill@cotw.com>
To: libc-alpha@sources.redhat.com, linux-mips@oss.sgi.com
Subject: New MIPS cross toolchain using glibc-2.2.5pre1....
Date: Fri, 25 Jan 2002 14:46:31 -0600 [thread overview]
Message-ID: <3C51C427.392B40E4@cotw.com> (raw)
Greetings.
First I want to thank HJ Lu for his patience as I traded quite
a few emails with him trying to get this up and working. I was
successful with building a new MIPS toolchain using the following:
binutils-cvs-LATEST
gcc-cvs-LATEST (gcc-3.1)
glibc-2.2.5pre1
It compiles kernels and user apps with no problems. I have made
everything available here:
ftp://ftp.cotw.com/Linux/MIPS/toolchain/experimental
Most important is the patch required to glibc-2.2.5pre1 in order
for a MIPS toolchain to even build. The other important item is
that it is absolutely necessary to specify the '--enable-kernel=2.4.X'
option when configuring glibc, or you will have problems with
undefined versioned symbols related to GLIBC_2.1. There is also
a shell script in the 'sources' directory that shows the exact steps
that I used. Hopefully this will be of some use to someone. Cheers.
-Steve
--
Steven J. Hill - Embedded SW Engineer
reply other threads:[~2002-01-25 21:46 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=3C51C427.392B40E4@cotw.com \
--to=sjhill@cotw.com \
--cc=libc-alpha@sources.redhat.com \
--cc=linux-mips@oss.sgi.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.