Wonderful...partly. This worked to get the lib in ldconfig, but then I noticed that
it still couldn't find the lib. Trussing 'ld -liconv' revealed that it was only
looking in /usr/lib. I have a LD_LIBRARY_PATH, and even went so far as to create a
LD_FLAGS var. Neither of these things made ld even glance beyond /usr/lib.
Lost.
but thanks anyway.
On Sat, Feb 17, 2001 at 09:07:32AM -0600, Jacques A. Vidrine wrote:
> On Fri, Feb 16, 2001 at 09:34:22PM -0600, Maximus <[EMAIL PROTECTED]> wrote:
> > I installed libiconv-1.5.1 on my 4.1.1-release system with the following results:
> >
> > -rw-r--r-- 1 root wheel 452 Feb 16 09:05 libiconv.la
> > lrwxr-xr-x 1 root wheel 15 Feb 16 09:05 libiconv.so -> libiconv.so.2.2
> > -rw-r--r-- 1 root wheel 646265 Feb 16 09:05 libiconv.so.2.2
> ^^^^^^
> ELF libraries should only have a major version, not a major+minor
> version. Install the port instead of compiling it yourself, and this
> will be handled.
>
> > Once finished I run 'ldconfig -m /usr/local/lib /usr/lib'. No errors
> > to this point.
>
> I believe that ELF ldconfig will ignore libraries with more than one
> version number tagged on. But it doesn't matter much -- the hints file
> is not used with ELF.
>
> > Once done I run 'ldconfig -r | grep icon' and nothing is there. The
> > library is not making it into the hints file.
> >
> > Running file on the .so.2.2 file I get the following:
> >
> > libiconv.so.2.2: ELF 32-bit LSB shared object, Intel 80386, version 1
> > (FreeBSD), not stripped
> >
> > Obviously I'm missing something. What?
> >
> > Any pointer would be appreciated. At the minimum, where would I find
> > the source for ldconfig? Which package?
>
> Package? ldconfig is in the base system, and a good guess would be:
>
> $ which ldconfig
> /sbin/ldconfig
> $ cd /usr/src/sbin/ldconfig
> $ ls
> Makefile elfhints.c ldconfig.8 ldconfig.c ldconfig.h
>
> Hope this helps!
>
> Cheers,
> --
> Jacques Vidrine / [EMAIL PROTECTED] / [EMAIL PROTECTED] / [EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
