Bug 12500 - ldconfig - errors file/link exception reports
ldconfig - errors file/link exception reports
Status: CLOSED RAWHIDE
Product: Red Hat Linux
Classification: Retired
Component: compat-egcs (Show other bugs)
7.1
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Jakub Jelinek
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2000-06-18 23:33 EDT by R P Herrold
Modified: 2008-05-01 11:37 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2000-08-08 22:41:23 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description R P Herrold 2000-06-18 23:33:46 EDT
Possibly an RPM artifact -- see: Bug 3252

 Subject: ldconfig-errors
 
ldconfig: /usr/lib/libstdc++.so.2.9 is not a symbolic link
 
ldconfig: /usr/lib/libstdc++-libc6.1-1.so.2 is not a symbolic link

(ldconfig should run silently)

The two listed files _should_ be links, rather than direct files:

[root@localhost src]# cat /etc/ld.so.conf 
/usr/X11R6/lib
/usr/kerberos/lib
/usr/i486-linux-libc5/lib
/usr/lib
[root@localhost src]# ls -al  /usr/lib/libstdc++.so.2.9
-rwxr-xr-x    1 root     root         5380 May 26 12:29
/usr/lib/libstdc++.so.2.9
[root@localhost src]# ls -al /usr/lib/libstdc++-libc6.1-1.so.2
-rwxr-xr-x    1 root     root      1185378 May 26 12:29
/usr/lib/libstdc++-libc6.1-1.so.2
[root@localhost src]# 

Reproduce the error thus:

 src]# ldconfig -v > /dev/null
ldconfig: Path `/usr/lib' given more than once
ldconfig: /usr/lib/libstdc++.so.2.9 is not a symbolic link

ldconfig: /usr/lib/libstdc++-libc6.1-1.so.2 is not a symbolic link

[root@localhost src]#
Comment 1 Cristian Gafton 2000-08-08 22:41:20 EDT
assigned to jakub
Comment 2 Jakub Jelinek 2000-08-25 12:12:06 EDT
No, this was actually a bug in libstdc++-compat (now compat-libstdc++)
packagin.g

Note You need to log in before you can comment on or make changes to this bug.