From: Dan Kegel <dank@kegel.com>
To: linuxppc-embedded@lists.linuxppc.org
Subject: crosstool-0.16: ppc405 working in glibc-2.3.2 now
Date: Thu, 31 Jul 2003 21:31:48 -0700 [thread overview]
Message-ID: <3F29ED34.5080304@kegel.com> (raw)
crosstool is a set of scripts for building and testing cross-compilers
based on gcc/glibc/linux.
A new release is ready, and can be downloaded from
http://kegel.com/crosstool
The big change with this release is that it builds glibc-2.3.2
properly on ppc405, thanks to a patch from Daniel Jacobowitz.
You can see the regression test summaries at
http://www.kegel.com/crosstool/current/summaries/
Changelog:
0.16 21 July 2003 "Shaking out glibc-2.3.2 a bit"
glibc-2.3.2-patches/glibc-2.3.2-without-fp.patch, straight from Daniel
Jacobowitz, fixes the --without-fp option of glibc-2.3.2, needed for ppc405.
glibc-2.3.2-patches/glibc-2.3.2-cross.patch, from cvs, avoids a glaring build failure.
gcc-3.3-patches/sh-pic-set_fpscr.patch is a partial fix for problems
building gcc-3.3/glibc-2.3.2 for sh4. Work in progress.
gcc3.3-glibc2.3.2.dat now refers to binutils-2.14.90.0.5 in hopes
that fixes problems on sh4 (or at least makes it easier for Kaz to
play with)
My gcc-*-patches directories are a bit out of sync; if you run
into a problem, it could be the patch you need hasn't been copied
or symlinked into your version of gcc's patches directory yet.
Note that wget on Red Hat 9 is rumored to not be able to fetch from
gnu.org. Workaround - use vanilla wget, or perhaps add the flag to use
passive mode.
--
Dan Kegel
http://www.kegel.com
http://counter.li.org/cgi-bin/runscript/display-person.cgi?user=78045
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
reply other threads:[~2003-08-01 4:31 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=3F29ED34.5080304@kegel.com \
--to=dank@kegel.com \
--cc=linuxppc-embedded@lists.linuxppc.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;
as well as URLs for NNTP newsgroup(s).