From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 6761 invoked by alias); 13 Apr 2002 18:46:08 -0000 Mailing-List: contact gcc-prs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-prs-owner@gcc.gnu.org Received: (qmail 6733 invoked by uid 71); 13 Apr 2002 18:46:05 -0000 Resent-Date: 13 Apr 2002 18:46:05 -0000 Resent-Message-ID: <20020413184605.6732.qmail@sources.redhat.com> Resent-From: gcc-gnats@gcc.gnu.org (GNATS Filer) Resent-To: nobody@gcc.gnu.org Resent-Cc: gcc-prs@gcc.gnu.org, gcc-bugs@gcc.gnu.org Resent-Reply-To: gcc-gnats@gcc.gnu.org, dave.anglin@nrc.ca Received:(qmail 4720 invoked by uid 61); 13 Apr 2002 18:39:18 -0000 Message-Id:<20020413183918.4719.qmail@sources.redhat.com> Date: Sat, 13 Apr 2002 11:46:00 -0000 From: dave.anglin@nrc.ca Reply-To: dave.anglin@nrc.ca To: gcc-gnats@gcc.gnu.org X-Send-Pr-Version:gnatsweb-2.9.3 (1.1.1.1.2.31) Subject: libf2c/6288: libg2c.sl.0.0 and libobjc.sl.1.0 are linked to libgcc_s.sl in build directory after installation X-SW-Source: 2002-04/txt/msg00725.txt.bz2 List-Id: >Number: 6288 >Category: libf2c >Synopsis: libg2c.sl.0.0 and libobjc.sl.1.0 are linked to libgcc_s.sl in build directory after installation >Confidential: no >Severity: serious >Priority: medium >Responsible: unassigned >State: open >Class: sw-bug >Submitter-Id: net >Arrival-Date: Sat Apr 13 11:46:04 PDT 2002 >Closed-Date: >Last-Modified: >Originator: Dave Anglin >Release: gcc 3.1 (prerelease) >Organization: >Environment: hppa[1.1,2.0w]-hp-hpux[10,11].* >Description: In the process, I discovered that libg2c.sl.0.0 and libobjc.sl.1.0 are linked to libgcc_s.sl in the build directory after installation: # chatr libg2c.sl.0.0 [...] internal name: libg2c.sl.0 shared library list: dynamic /usr/lib/libm.2 dynamic /usr/lib/libc.2 dynamic /xxx/gnu/gcc-3.1/objdir/gcc/libgcc_s.sl The installation/build process has incorrectly linked against libgcc_s.sl in my build directory rather than against the newly installed version in the installation directory. When libgcc_s.sl is removed from the build directory, the dynamic loader is unable to find libgcc_s.sl and applications linked against the libraries nolonger run. >How-To-Repeat: >Fix: >Release-Note: >Audit-Trail: >Unformatted: