From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 388 invoked by alias); 15 Jul 2002 15:20:13 -0000 Mailing-List: contact binutils-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: binutils-owner@sources.redhat.com Received: (qmail 367 invoked from network); 15 Jul 2002 15:20:10 -0000 Received: from unknown (HELO creeper.bmc.com) (198.207.223.228) by sources.redhat.com with SMTP; 15 Jul 2002 15:20:10 -0000 Received: from ec03-hou.bmc.com (localhost [127.0.0.1]) by creeper.bmc.com (8.10.2/8.10.2) with ESMTP id g6FFJrl07202; Mon, 15 Jul 2002 10:19:54 -0500 (CDT) Received: by ec03-hou.bmc.com with Internet Mail Service (5.5.2653.19) id ; Mon, 15 Jul 2002 10:20:08 -0500 Message-ID: From: "Dana, Eric" To: "'binutils@sources.redhat.com'" , "'gcc-bugs@gcc.gnu.org'" Subject: Using binutils-2.12.1 on sparc64-sun-solaris2.8 to build gcc-3.1 results in relocation errors Date: Mon, 15 Jul 2002 08:24:00 -0000 MIME-Version: 1.0 Content-Type: text/plain X-SW-Source: 2002-07/txt/msg00324.txt.bz2 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.