This is the mail archive of the binutils@sources.redhat.com mailing list for the binutils project.

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

Using binutils-2.12.1 on sparc64-sun-solaris2.8 to build gcc-3.1 results in relocation errors

From: "Dana, Eric" <Eric_Dana at bmc dot com>
To: "'binutils at sources dot redhat dot com'" <binutils at sources dot redhat dot com>, "'gcc-bugs at gcc dot gnu dot org'" <gcc-bugs at gcc dot gnu dot org>
Date: Mon, 15 Jul 2002 10:20:05 -0500
Subject: Using binutils-2.12.1 on sparc64-sun-solaris2.8 to build gcc-3.1 results in relocation errors

When building some of our 64-bit libraries in C++, we are seeing
R_SPARC_DISP32 errors:

../../../obj/sun/sparc-solaris2.7W/monitor/lib/Agent/libAgent.a(alert.o):iti
merspec/alert.C:37:
    relocation truncated to fit: R_SPARC_DISP32
.gnu.linkonce.t._ZN10printClass5printEiPKc
../../../obj/sun/sparc-solaris2.7W/monitor/lib/Agent/libAgent.a(alert.o):iti
merspec/alert.C:37: 
    relocation truncated to fit: R_SPARC_DISP32
.gnu.linkonce.t._ZN10printClass6indentEi
../../../obj/sun/sparc-solaris2.7W/monitor/lib/Agent/libAgent.a(agentConditi
on.o):itimerspec/agentCondition.C:50:
    relocation truncated to fit: R_SPARC_DISP32
.gnu.linkonce.t._ZN10printClass5printEiPKcm
and many, many more...

This happens on Solaris 2.7/2.8 when linking  64-bit objects.
Below is a reference from another developer (taken from the binutils
archives)

   2002-05/msg01920.html   

At this time we have no workaround. Can a previous version of binutils be
used on Solaris with 64-bit linking
with GCC 3.1 or later?

--Eric Dana--
BMC Software Inc.

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