From: Kumar Gala <kumar.gala@freescale.com>
To: Aubrey Lee <aubrey1127@gmail.com>,
"<tglx@linutronix.de> <tglx@linutronix.de>" <tglx@linutronix.de>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: Build cross tools for PowerQUICCIII
Date: Mon, 10 Jan 2005 09:52:48 -0600 [thread overview]
Message-ID: <AD51476A-631F-11D9-807E-000393DBC2E8@freescale.com> (raw)
In-Reply-To: <7f834d4e050109212155be7b19@mail.gmail.com>
I've attached some patches Freescale has developed and sent Dan K. to
include into crosstool. Feel free to use these until Dan K.
incorporates them into crosstool:
http://gate.crashing.org/~galak/crosstool-0.28-rc37-e500.patch.bz2
http://gate.crashing.org/~galak/crosstool-0.28-extra-patches.patch.bz2
Two patches are needed for crosstool-0.28-rc37, and are attached:
1/ e500 toolchain patch.
This patch contains the following:
- spe patches for glibc-2.3.2 and glibc-2.3.2,
- gcc-3.4.3-e500-glibc-2.3.3-spe.dat
- powerpc-e500.dat
- powerpc-e500.config (e500 kernel config for 2.6.9)
- demo-e500.sh
demo-e500.sh will build an e500 toolchain comprising gcc-3.4.3
glibc-2.3.3, and binutils-2.15
2/ getandpatch EXTRA_PATCHES patch.
This is a patch for getandpatch to permit additional patches (in
addition to the standard crosstool patches) that are needed to be
applied for a toolchain build. To do this the environment variable
EXTRA_PATCHES is set to the name of the patches needed. For example
when building the e500 toolchain EXTRA_PATCHES needs to be set to "spe"
to apply the spe patches to glibc. The glibc spe patches are located
in: crosstool-0.28-rc37/patches/glibc-2.3.2-spe
The advantage that this gives is that all the standard crosstool
patches
for glibc-2.3.2 can remain in their original directory, and the spe
patches are applied in addition to the normal glibc patches.
- kumar
On Jan 9, 2005, at 11:21 PM, Aubrey Lee wrote:
> Hi, I want to build cross tools for PowerQUICCIII(mpc8540, e500
> core),
> Had anyone built cross tools successfully by cross-tools-0.28?
> What type of target should I set? Could you tell me the versions
> you have used?
> Thank you!
> Best regards
>
> Aubrey
> _______________________________________________
> Linuxppc-embedded mailing list
> Linuxppc-embedded@ozlabs.org
> https://ozlabs.org/mailman/listinfo/linuxppc-embedded
prev parent reply other threads:[~2005-01-10 15:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-10 5:21 Build cross tools for PowerQUICCIII Aubrey Lee
2005-01-10 15:52 ` Kumar Gala [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=AD51476A-631F-11D9-807E-000393DBC2E8@freescale.com \
--to=kumar.gala@freescale.com \
--cc=aubrey1127@gmail.com \
--cc=linuxppc-embedded@ozlabs.org \
--cc=tglx@linutronix.de \
/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.