This is the mail archive of the mailing list for the crossgcc project.

See the CrossGCC FAQ for lots more information.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

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


That seemed to be the trick! You are a life saver. I left the
'-fno-stack-protector' in there, not sure that it was needed, but rather
be safe. 

I'll attach the newest, working configuration incase Yann wants to add
another example to the PowerPC configurations, with updated Linux kernel
and GCC, as well as threading, FP and shared cores. 

Thanks again Andy,


-----Original Message-----
From: Andy Gibbs [] 
Sent: Thursday, June 17, 2010 3:46 AM
To: McConnell, Christopher (GE Global Research)
Subject: Re: PowerPC target with gcc-4.4.x build failure


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


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!


----- Original Message -----
From: "McConnell, Christopher (GE Global Research)" <>
To: <>
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...

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


I'm looking to get a toolchain going for a target PowerPC 8548 e500v2,
running Linux 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

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

Thanks in advance,

Chris McConnell
Edison Engineering Development Program - Software


> --
> For unsubscribe information see 

Attachment: powerpc_64_4.4.x.config
Description: powerpc_64_4.4.x.config

For unsubscribe information see

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]