Re: PowerPC target with gcc-4.4.x build failure

["Andy Gibbs" <andyg1001 at hotmail dot co dot uk>]

Chris,

I had the same or a similar problem.  You may want to try setting the 
following flags in your crosstool configuration:

CT_LIBC_GLIBC_EXTRA_CFLAGS="-U_FORTIFY_SOURCE -fno-stack-protector"

The first part, "-U_FORTIFY_SOURCE" gets around the an unimplemented 
function inside eglibc.  The second part "-fno-stack-protector" I needed 
because eglibc/glibc was giving me segmentation faults on the target (an 
MPC5200B).  You may not need this of course...

Hope this helps!

Andy



----- Original Message ----- 
From: "McConnell, Christopher (GE Global Research)" <mcconnel@ge.com>
To: <crossgcc@sourceware.org>
Sent: Wednesday, June 16, 2010 8:19 PM
Subject: RE: PowerPC target with gcc-4.4.x build failure



Sorry, it could help if I remembered the configuration file...

Chris
-----Original Message-----
From: McConnell, Christopher (GE Global Research)
Sent: Wednesday, June 16, 2010 2:17 PM
To: crossgcc@sourceware.org
Cc: McConnell, Christopher (GE Global Research)
Subject: PowerPC target with gcc-4.4.x build failure

All,

I'm looking to get a toolchain going for a target PowerPC 8548 e500v2,
running Linux 2.6.33.2 and a compiler with at least a gcc-4.4.x
(preferably 4.4.3).

[...]

I've been researching for a while now and found other users trying to
get gcc-4.4.x to work for other target architectures, however they seem
to hit a wall as well (some similar to the one above, others are not).

I was hoping someone has come across this problem before and I've some
how missed a patch, or configuration option that should get over this
hurdle.

Any help/thoughts/suggestions/comments will be very appreciated.

Thanks in advance,

Chris McConnell
Edison Engineering Development Program - Software
K1-3A42



--------------------------------------------------------------------------------


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


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