Crosstool for e500 core (target) on PowerMac G4(host)

[Kumar Gala]

On Aug 29, 2007, at 7:54 AM, Clemens Koller wrote:

> Hi, Mike!
>
> mike zheng schrieb:
>> I have a PowerMac G4 with Linux 2.6.15. I want a build a cross- 
>> compiler for MPC8548( E500 Core, SPE) target. I downloaded  
>> crosstool-0.28-rc37 plus Kumar Gala's patches. The Gcc I am using  
>> to compile the crosstool is 3.3.1 on PowerMac G4.
>
> Hmm... I didn't finish that hazzle to get this (old) e500 cross- 
> toolchain
> working. (Well, my knowledge wasn't very detailed at that time.)
>
> Instead I managed to get an up to date _native_ toolchain which is  
> IMHO
> quite simple to maintain.
> (gcc-4.2.1, binutils-2.17, latest (e)glibc, latest kernels)
> My mpc8540 development platform has a harddisk on pci and can be
> used like a normal workstation now...
>
>> The crosstool download following files under /root/downloads:
>> binutils-2.15.tar.bz2, glibc-2.3.4.tar.bz2, gcc-3.4.3.tar.bz2,  
>> glibc-linuxthreads-2.3.3.tar, linux-2.6.9.tar.bz2
>
> It should work... hence you will end up with a quite old toolchain.
>
>> After run demo-e500.sh, I get the toolchain under /opt/crosstool/ 
>> powerpc-linux-gnuspe/gcc-3.4.3-glibc-2.4.4/bin.
>>  Then I try to compile 2.6.10 kernel and BSP of Freescale's  
>> MPC8548 CDS board, and have following errors:
>> CC arch/ppc/math-emu/efdctsf.o
>> {standard input}: Assembler messages:
>> {standard input}: 22: Error: Unrecognized opcode: `efdctsf`
>
> That's an double precision instruction of the e500 core which your
> binutils don't recognize. You are using either the wrong binutils  
> or an
> too old version of your binutils. binutils-2.15 should have it:
> http://ecos.sourceware.org/ml/binutils/2004-10/msg00070.html
>
> Dan or Kumar can give more details here.

Not too much more.  I'd suggest taking at the compilers Freescale  
provides as part of their BSPs.  In theory you should be able to  
rebuild them w/o too much headache on a ppc host.

- k

--
For unsubscribe information see http://sourceware.org/lists.html#faq