[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [patches] eglibc builds and tests on mpc8540
- To: Clemens Koller <clemens@xxxxxxxxxxxxxxxxxxxx>
- Subject: Re: [patches] eglibc builds and tests on mpc8540
- From: Jim Blandy <jimb@xxxxxxxxxxxxxxxx>
- Date: Thu, 24 May 2007 13:43:20 -0700
Steven Munroe <munroesj@xxxxxxxxxx> writes:
> Clemens Koller wrote:
>
>> Hello There!
>>
>> I want to build and test a current (2.5 or latest) (e)glibc which
>> supports the powerpc e500 mpc8540 processor's SPE.
>>
>> I have a native linux system running on an mpc8540ads-like board
>> which is also my development machine.
>>
>> I am still stuck with some older 2.6.12 kernel headers until
>> I can get new headers when I am able to move over from ARCH=ppc to
>> ARCH=powerpc. (some DeviceTree / Bootloader issues).
>>
>> I have an otherwise stable system (Linux From Scratch like) with
>> binutils-2.17, gcc-3.4.6, gcc-4.1.1, gcc-4.1.2 and gcc-4.2.0
>> built in a similar way:
>>
>> root@ecam:~$ gcc -v
>> Using built-in specs.
>> Target: powerpc-unknown-linux-gnu
>> Configured with: ../gcc-4.2.0/configure --prefix=/usr
>> --libexecdir=/usr/lib --enable-languages=c,c++,objc
>> --enable-threads=posix --enable-__cxa_atexit --enable-clocale=gnu
>> --enable-shared --disable-nls --with-x=no --with-float=soft
>> --with-cpu=8540 --with-tune=8540
>> Thread model: posix
>> gcc version 4.2.0 (ckcore)
>>
>> What linux kernel headers and glibc-headers do you recommend?
>
> 2.6.12 kernel headers are ok.
>
>>
>> What build environment (hosts, binutils, gcc...) do you recommend?
>>
> You will need a gcc-4.1.1 with soft-fp long double patches from
> bugzilla 2749, for a recent gcc-4.2 and a recent binutils (2.17).
>
> libc-2.5 powerpc WILL NOT build without long double support.
http://www.eglibc.org/prerequisites is meant to explain what's needed
to build EGLIBC.
Also, EGLIBC.cross-building has reasonably detailed instructions for a
generic build from straight sources --- binutils, kernel, GCC, and
EGLIBC. We don't want to expand those instructions to describe every
possible variation in the build process, but if they're unclear or
don't work the way they claim to, we'd love to hear about it.