From: "Shih-Ying Chou" <sschou@mtu.edu>
To: "André Lämmer" <alaemmer@fh-konstanz.de>
Cc: <linuxppc-embedded@lists.linuxppc.org>
Subject: Re: Compiling Kernel 2.6 for ppc32
Date: Wed, 10 Sep 2003 15:14:20 -0400 [thread overview]
Message-ID: <002401c377cf$bcff2800$6401a8c0@sazabimobile> (raw)
In-Reply-To: 000001c377b5$d341b2f0$0f21258d@fhkonstanz.de
> *** 2.6 kernels no longer buildcorrectly with old versions of binutils.
> *** Please upgrade your binutils to 2.12.1 or newer
>
> Will be there a new release in the next time?
>
You can go to http://kegel.com/crosstool/ to download the scripts that can
help you to get the newer version of gcc, glibc and binutils. I have used
it to create a cross-compile tool chain and the tool chain can compile the
2.6.0-test5 successfully. The scripts do support several processor
architecture including ppc and others.
Hope this can help you.
Shih-Ying Chou
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
prev parent reply other threads:[~2003-09-10 19:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-09 16:17 Compiling Kernel 2.6 for ppc32 André Lämmer
2003-09-09 16:49 ` Dan Kegel
2003-09-09 17:30 ` Wolfgang Denk
2003-09-10 16:08 ` André Lämmer
2003-09-10 16:54 ` Wolfgang Denk
2003-09-10 19:14 ` Shih-Ying Chou [this message]
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='002401c377cf$bcff2800$6401a8c0@sazabimobile' \
--to=sschou@mtu.edu \
--cc=alaemmer@fh-konstanz.de \
--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).