[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: as 2.12, 2.13 on sparc -m64: error when linking: relocation t runc a
From: |
kneel |
Subject: |
RE: as 2.12, 2.13 on sparc -m64: error when linking: relocation t runc ated to fit: R_SPARC_DISP32 .gnu.linkonce.t.NewAlloc |
Date: |
Mon, 23 Sep 2002 11:51:01 -0700 |
Thanks for the fix in your other email! I'l try that out. To (try to) answer
your question, our biggest non-debug executable (using Sun's tools) is 28MB.
It can use multi-gigabyte segments of data.
I of course can't comment on Teemu's app.
-----Original Message-----
From: Alan Modra [mailto:address@hidden
Sent: Saturday, September 21, 2002 12:56 AM
To: address@hidden; Teemu Torma
Cc: address@hidden
Subject: Re: as 2.12, 2.13 on sparc -m64: error when linking: relocation
trunc ated to fit: R_SPARC_DISP32 .gnu.linkonce.t.NewAlloc
On Wed, Sep 18, 2002 at 02:06:45PM -0700, address@hidden wrote:
> I get the same error as below whether I use Sun's ld or binutils ld, so I
> assume the problem is as. Any ideas? I've not seen a response to the npte
> below. Thanks!
It also might be a gcc problem. I see sparc64 uses 32-bit displacements
for eh data, to save memory. Just how big is this application?
> Problem with linking on 64 bit sparc solaris 2.7
[snip]
>
NamingContext_i.o:itimerspec/../../../../src/appl/omniNames/NamingContext_i.
> cc:56:
> relocation truncated to fit: R_SPARC_DISP32
> .gnu.linkonce.t._ZN5CORBA7releaseEPNS_6ObjectE
Hmm, the above doesn't help much in tracking down this sort of problem.
I'll see about tweaking ld's error messages.
--
Alan Modra
IBM OzLabs - Linux Technology Centre
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- RE: as 2.12, 2.13 on sparc -m64: error when linking: relocation t runc ated to fit: R_SPARC_DISP32 .gnu.linkonce.t.NewAlloc,
kneel <=