From: Clemens Koller <clemens.koller@anagramm•de>
To: Sasvata Chatterjee <sasvata.chatterjee@gmail•com>
Cc: linuxppc-embedded@ozlabs•org
Subject: Re: Latest GCC/GLIBC working combo for a Linux 2.4.x kernel?
Date: Fri, 25 May 2007 14:54:20 +0200 [thread overview]
Message-ID: <4656DC7C.8020503@anagramm.de> (raw)
In-Reply-To: <a9fc2a630705241728q4d203569n6eb008cc65a7eba9@mail.gmail.com>
Hi, Sasvata!
> We are using a RHEL/386 machine to cross-compile for Debian/PowerPC
> (8260) target, a few year old embedded system that we inherited. The
> kernel is 2.4.9. Using crosstools, and following Dan Kegel's notes, the
> combo we have is gcc-2.95-3/glibc-2.2.5.
>
> Does anybody have any working version using newer versions of the 2.4
> kernel and newer GCC versions for a powerpc-603e target? One motivation
> is to use BusyBox-1.5.1, but I am told on that list that GCC 2/x is too
> old (I tried before I asked, it doesn't compile).
It's propably painful to work your way through crosstools with such an
old toolchain. I would have a look if one of the ELDK's from
http://www.denx.de can be used for your board - at least for a good start.
If you run into problems with older linux-2.4 kernel version with the newer ELDK's,
you can also go back to some older version?
> Any help, pointers, example config files for crosstools, etc. would be
> really appreciated!
You are always welcome at their mailing list. See:
http://kegel.com/crosstool
Best greets,
--
Clemens Koller
__________________________________
R&D Imaging Devices
Anagramm GmbH
Rupert-Mayer-Straße 45/1
Linhof Werksgelände
D-81379 München
Tel.089-741518-50
Fax 089-741518-19
http://www.anagramm-technology.com
next prev parent reply other threads:[~2007-05-25 12:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-25 0:28 Latest GCC/GLIBC working combo for a Linux 2.4.x kernel? Sasvata Chatterjee
2007-05-25 12:54 ` Clemens Koller [this message]
2007-05-25 21:39 ` Wolfgang Denk
2007-05-29 15:29 ` Sasvata Chatterjee
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=4656DC7C.8020503@anagramm.de \
--to=clemens.koller@anagramm$(echo .)de \
--cc=linuxppc-embedded@ozlabs$(echo .)org \
--cc=sasvata.chatterjee@gmail$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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