From: Kumar Gala <galak@kernel.crashing.org>
To: Clint Thomas <cthomas@Soneticom.com>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: GCC version to kernel version
Date: Fri, 13 Oct 2006 10:34:09 -0500 [thread overview]
Message-ID: <EE6BAB8C-DD74-412B-BDD1-1758426B62F7@kernel.crashing.org> (raw)
In-Reply-To: <3C02138692C13C4BB675FE7EA24095291F5A08@bluefin.Soneticom.local>
On Oct 13, 2006, at 9:55 AM, Clint Thomas wrote:
> Hey guys,
>
> Generic question here. To each linux kernel version, is there a
> specific version of GCC and GLIBC I should be using to build the
> kernel, RFS, etc? I cannot seem to find any concrete proof that
> this is the case, but I am having issues building a new RFS with my
> older GCC and GLIBC, so I'm looking at updating them. I'm currently
> using GCC 3.3.2 and GLIBC 2.3.2 to build for the Linux 2.4.27
> kernel on an e500 (MPC8541) core. Thanks!
>
It depends on what user space functionality you want/need form e500.
If you plan on using SPE or fp I'd say to make sure to get tools
chains that support e500. If you are just running normal integer
code than any toolchain should be fine.
- k
next prev parent reply other threads:[~2006-10-13 15:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-13 14:55 GCC version to kernel version Clint Thomas
2006-10-13 15:34 ` Kumar Gala [this message]
2006-10-13 15:39 ` Clint Thomas
2006-10-13 15:54 ` Kumar Gala
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=EE6BAB8C-DD74-412B-BDD1-1758426B62F7@kernel.crashing.org \
--to=galak@kernel.crashing.org \
--cc=cthomas@Soneticom.com \
--cc=linuxppc-embedded@ozlabs.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