[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
as 2.12, 2.13 on sparc -m64: error when linking: relocation trunc ated t
From: |
kneel |
Subject: |
as 2.12, 2.13 on sparc -m64: error when linking: relocation trunc ated to fit: R_SPARC_DISP32 .gnu.linkonce.t.NewAlloc |
Date: |
Wed, 18 Sep 2002 14:06:45 -0700 |
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!
Kevin Neel
Problem with linking on 64 bit sparc solaris 2.7
* From: Teemu Torma <tot at trema dot com>
* To: bug-binutils at gnu dot org
* Date: Tue, 16 Jul 2002 17:19:02 +0200
* Subject: Problem with linking on 64 bit sparc solaris 2.7
* Organization: Trema Group
I am trying to use gcc 3.1 to build 64 sparc solaris binaries with binutils,
and have a problem with C++ linking. All plain C links just fine, and small
C++ bits, but C++ which involves bigger shared libraries fail in the final
linking phase.
The messages I receive are always like (this example is from omniORB, when
it
tries to link omniNames):
NamingContext_i.o:itimerspec/../../../../src/appl/omniNames/NamingContext_i.
cc:56:
relocation truncated to fit: R_SPARC_DISP32
.gnu.linkonce.t._ZN5CORBA7releaseEPNS_6ObjectE
All the errors (about 50) are for .gnu.linkonce.t section. I have tried
with
binutils 2.12 and with todays CVS version with same results. This happens
only with the final linking, no problem when building shared libraries.
Any ideas what this could be? I don't know internals of binutils well, so
any
advice what to look for? I tried to debug whether the message was valid
one,
and it seems to be--the linker is complaining becase the address it is
checking needs 33 bits.
btw, I am not on this mailing list, so please include me directly.
Thanks in advance,
Teemu
- as 2.12, 2.13 on sparc -m64: error when linking: relocation trunc ated to fit: R_SPARC_DISP32 .gnu.linkonce.t.NewAlloc,
kneel <=