[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: powerpc executable size limit question

From: John Van Horne
Subject: RE: powerpc executable size limit question
Date: Thu, 4 Apr 2002 15:23:41 -0800

Never mind.  The issue was someone was building a shared library without the -fPIC option.

Sorry for the bother.

-----Original Message-----
> From:         John Van Horne 
> Sent: Thursday, April 04, 2002 2:08 PM
> To:   'address@hidden'
> Cc:   John Van Horne
> Subject:      powerpc executable size limit question
> Sorry for posting twice, but I inadvertantly forgot to put a
> subject in the mail.  I not a subscriber to the list,
> and after posting this I looked at the archives and saw the
> number of unwanted messages.   I thought I'd better make sure
> that my message wasn't ignored.  Thanks.
> Hi,
> I hope this is an appropriate place for this question.
> We are using
> Linux Kernel 2.4.4 (Yellow Dog Linux 2.0) for PowerPC
> gcc 2.95.2
> binutils 2.10
> glibc 2.2.1
> We've got a huge executable which gets the following error
> when it tries to run:
> /ipnos.nohw.ctl: error while loading shared libraries:
> /dvlp/hpoliset/sharedLibs/libOB.so.3.3.4: R_PPC_REL24
> relocation at 0x0e2c7000 for symbol `g_varRC11OBStrForSeq'
> out of range
> When I do a 'size' of the executable I get a text size over
> 30MB.  When I do a size of the shared library, I get
> something over 3MB.  It looks to me as though the library was
> built with the -fPIC option.
> Are we hitting a limit in the size of a linked executable for
> Linux on PPC?  We've hit a limit of 32MB for statically
> linked images.  Does this also apply when the image is
> dynamically linked as well?
> You _may_ encounter problems responding to this mail, due to
> our corporate IT folks :-{  If so, could you please respond
> to me at address@hidden
> Thanks,
> -John

reply via email to

[Prev in Thread] Current Thread [Next in Thread]