libf2c/6288: libg2c.sl.0.0 and libobjc.sl.1.0 are linked to libgcc_s.sl in build directory after installation
dave.anglin@nrc.ca
dave.anglin@nrc.ca
Sat Apr 13 11:46:00 GMT 2002
>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:
More information about the Gcc-prs
mailing list