Date: Fri, 28 Jan 2000 00:21:28 -0500 (EST) From: Tim Pierce <twp@rootsweb.com> To: freebsd-questions@freebsd.org Subject: ldconfig treats ELF libraries as a.out? Message-ID: <200001280521.e0S5LSW85627@ma-1.rootsweb.com>
next in thread | raw e-mail | index | archive | help
Hi, folks -
This is a weird one. I don't know if it's my fault or ldconfig's.
I have installed libjpeg on my FreeBSD 3.3 machine:
# ls -l /local/lib/libjpeg.*
-rw-r--r-- 1 root wheel 164024 Dec 16 17:54 /local/lib/libjpeg.a
-rwxr-xr-x 1 root wheel 459 Dec 16 17:54 /local/lib/libjpeg.la
lrwxr-xr-x 1 root wheel 15 Dec 16 17:54 /local/lib/libjpeg.so -> libjpeg.so.62.0
-rwxr-xr-x 1 root wheel 140861 Dec 16 17:54 /local/lib/libjpeg.so.62.0
According to `file', the shared object is an ELF library:
# file /local/lib/libjpeg.so.62.0
/local/lib/libjpeg.so.62.0: ELF 32-bit LSB shared object, Intel 80386, version 1 (FreeBSD), not stripped
Yet when I do ldconfig -elf -R, it doesn't recognize libjpeg:
# ldconfig -elf -R
# ldconfig -elf -r | grep jpeg
#
(Yes, /local/lib is in ldconfig's search path.)
In order to get libjpeg added to ld.so.hints, I have to pretend that
it's an a.out file:
# ldconfig -aout /usr/lib/aout /usr/lib/compat/aout /usr/X11R6/lib/aout /local/lib /local/lib/mysql
# ldconfig -aout -r | grep jpeg
57:-ljpeg.62.0 => /local/lib/libjpeg.so.62.0
I'm mystified. Why is ldconfig treating ELF libraries as a.out files?
A couple of FreeBSD releases ago, I installed GCC 2.91.66 in
/local/bin; could that be confusing the issue?
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200001280521.e0S5LSW85627>