RE: Cross toolchain for ppc405 (virtex-4)

[rodolfo <rodolfo@lesc.ufc.br>]

I'm sorry.

I want build kernel linux 2.6 for ml403. 
Did I have to change the predefined compiler flags for ppc_4xx? The default
value is -mcpu=403.

On Wed, 28 May 2008 13:32:51 -0600, "John Linn" <John.Linn@xilinx.com>
wrote:
> I don't know, I'm not familiar with what you are doing and it's not clear
> from the message.
>  
> -- John
> 
> ________________________________
> 
> From: rodolfo [mailto:rodolfo@lesc.ufc.br]
> Sent: Wed 5/28/2008 12:05 PM
> To: John Linn
> Cc: Mirek23; linuxppc-embedded@ozlabs.org
> Subject: RE: Cross toolchain for ppc405 (virtex-4)
> 
> 
> 
> Hi Jonh,
> 
> If I use ml403 (with PPC 405) Did i change the predefined compiler flags
> for ppc_4xx? The default value is -mcpu=403.
> 
> On Wed, 28 May 2008 11:16:41 -0600, "John Linn" <John.Linn@xilinx.com>
> wrote:
>> Hi Miroslaw,
>>
>> I'm not sure on what version of gcc and glibc it's using, but I have
> been
>> using ELDK 4.1 from denx.com. There are newer versions.
>>
>> Thanks,
>> John
>>
>>
>>
>> -----Original Message-----
>> From: linuxppc-embedded-bounces+john.linn=xilinx.com@ozlabs.org on
> behalf
>> of Mirek23
>> Sent: Wed 5/28/2008 9:54 AM
>> To: linuxppc-embedded@ozlabs.org
>> Subject: Cross toolchain for ppc405 (virtex-4)
>> 
>>
>> Hi All,
>>
>> I am using for some time the crosstool tool-chain (crosstool-0.43) for
> the
>> ppc405 of my virtex-4.
>> It seems to be that the crosstool was not updated for awhile but the
> glibc
>> and gcc compiler has changed a bit meanwhile.
>>
>> The latest working configuration to build the toolchain for ppc405 is
>> gcc-4.1.0-glibc-2.3.6.dat
>> Does any body has tried to adapt the crosstools to use for example glibc
>> 2.7
>> ?
>>
>> Another alternative would be to use another tool than crosstool. Could
>> somebody recommend something which can refer to newer version of gcc and
>> glibc .
>>
>> Best Regards
>>
>> Miroslaw Dach
>>
>>
> 
> 
> 
> 
> 
> 
> This email and any attachments are intended for the sole use of the named
> recipient(s) and contain(s) confidential information that may be
> proprietary, privileged or copyrighted under applicable law. If you are
not
> the intended recipient, do not read, copy, or forward this email message
or
> any attachments. Delete this email message and any attachments
immediately.