fixed: can't find .so, but it's right there.

[Steve Franks]

Bugger me!  Something, sometime, pulled a linux mplayer onto my disk,
wonder when I did that?  (It's been awhile that I've had this issue,
and I have a bad habit of dump/restoring disks between work & home
computers willy-nilly).

Anyway, /usr/bin/mplayer looked a bit funny (not in /usr/local), and
brandelf /usr/bin/mplayer caught it red-handed as an SRV4 file!
(should have been FreeBSD for anyone out there reading the archives
not familiar with brandelf).  Deleted it, and the freebsd mplayer
hiding in /usr/local/bin fired right up.

Anyway, thanks, y'all; sorry for the dumb question!

Steve


On Tue, Aug 17, 2010 at 10:31 AM, Steve Franks <bahamasfranks at gmail.com> wrote:
> On Tue, Aug 17, 2010 at 10:28 AM, Greg Larkin <glarkin at freebsd.org> wrote:
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA1
>>
>> Steve Franks wrote:
>>> What gives?  This is after portupgrade -akfO and an ldconfig just for
>>> good measure.
>>>
>>> [steve at fyre /usr/home/steve]$ cd /usr/local/lib
>>> [steve at fyre /usr/local/lib]$ ls -la | grep aa
>>> -rw-r--r--    1 root  wheel    189146 Jul 13 06:55 libaa.a
>>> -rwxr-xr-x    1 root  wheel      1077 Jul 13 06:55 libaa.la
>>> lrwxr-xr-x    1 root  wheel        10 Jul 13 06:55 libaa.so -> libaa.so.1
>>> -rwxr-xr-x    1 root  wheel    121682 Jul 13 06:55 libaa.so.1
>>> [steve at fyre /usr/local/lib]$ mplayer
>>> mplayer: error while loading shared libraries: libaa.so.1: cannot open
>>> shared object file: No such file or directory
>>> [steve at fyre /usr/local/lib]$
>>>
>>>
>>> Best,
>>> Steve
>>
>> Hi Steve,
>>
>> What is the output of the following command?
>>
>> ldd `which mplayer`
>>
>
> [steve at fyre /usr/home/steve]$ ldd `which mplayer`
> /usr/bin/mplayer:
> /usr/bin/mplayer: error while loading shared libraries: libaa.so.1:
> cannot open shared object file: No such file or directory
> /usr/bin/mplayer: exit status 127
> [steve at fyre /usr/home/steve]$
>
> I also rebuilt libaa specifically, FYI.  It's there, but mplayer can't
> get to it for some reason...
>
> Thanks,
> Steve
>