Re: why is g++ relocation error linking only showing when listing objects explicitly?

[Andrew Haley <aph@redhat.com>]

On 12/21/2012 03:10 PM, Mark Galeck (CW) wrote:
>> Aha!  The error is in crtbeginS.o.  This is important: it is not one of the files you compiled.  Therefore, no matter what you do with -mlongcall", it won't help.  It may be that recompiling crtbeginS.o with
> 
> -mlongcall" would help, but we'd need a PPC export to confirm that.
> 
> Out of the question... :(   can't recompile any system stuff.  
> 
>> It may be easier simply to split the shared library.
> 
> Also out of the question I am afraid.  Has to be one lib.

Well, that's the trouble.  There are a couple of correct ways to fix
your problem, but you reject them because you aren't allowed.

> Well, the thing is, there is one particular order of the .o files,
> that seems to work.  It's just that, I am using a different order.
> I don't want to use that other order, besides, it's like
> hit-and-miss, one day (perhaps tomorrow), someone will add another
> object and it won't work any more.

Exactly.  That's why it's the wrong thing to do.

Andrew.