-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
James Sparenberg wanted us to know:
>> [EMAIL PROTECTED] ~]$ urpmf libaudio.so
>> libnas2:/usr/X11R6/lib/libaudio.so.2
>> libnas2:/usr/X11R6/lib/libaudio.so.2.3
>> libnas2-devel:/usr/X11R6/lib/libaudio.so
>locate libaudio.so
>/usr/X11R6/lib/libaudio.so.2.3
>/usr/X11R6/lib/libaudio.so.2
Those two are the runtime libraries. Note how they're provided by the
libnas2 package. When linking, it will use the "-laudio" flag which
means it wants to look for libaudio.so. It doesn't want the .2 or .2.3
at the end. It wants only lib + {link target} + .so and that's it.
That file name convention is provided by the -devel package, in this
case, libnas2-devel.
>Even though I have the rpm in question installed. I don't have that 3rd
>level of linking. Where so.2 and so link to so.2.3. So what I've found
>is often when I get the above error. I have 3 steps. One, the one you
>took. Two, make sure that that 3rd link (the libaudio.so one) is
>there. and finally I've had to add a bunch to ld.so.conf. things like
>/usr/lib/ even though the libs are there for reasons unknown some
>builds don't pick it up unless I had the dir to ld.so.conf and re-run
>ldconfig. I know this isn't supposed to happen... but. If it works
>repeatedly I keep repeating it.
I think there's something else going on here. /lib and /usr/lib are
default paths for ldconfig. Witness another example:
[EMAIL PROTECTED] ~]$ locate libncurses\. | grep lib | grep -v "a$"
/usr/lib/libncurses.so.5.3
/usr/lib/libncurses.so.5
/usr/lib/libncurses.so
/lib/libncurses.so.5.3
/lib/libncurses.so.5
/lib/libncurses.so
[EMAIL PROTECTED] ~]$ locate libncurses\. | grep lib | grep -v "a$" | xargs rpm
- -qf
libncurses5-5.3-1.20030215.1mdk
libncurses5-5.3-1.20030215.1mdk
libncurses5-devel-5.3-1.20030215.1mdk
libncurses5-5.3-1.20030215.1mdk
libncurses5-5.3-1.20030215.1mdk
libncurses5-devel-5.3-1.20030215.1mdk
So libncurses.so is provided by the libncurses5-devel package and
libncurses.so.* is provided by the libncurses5 package. The first is
the development package because it's used when compiling programs that
will use ncurses. The second is the runtime libraries because programs
that are linked with ncurses need this library to be present to run.
Unfortunately, I seem to be using a bit of circular logic, maybe someone
else can explain it a bit better.
- --
Blue skies... Todd
| Get a bigger hammer! | I vowed revenge on the soul |
| http://www.mrball.net | of Bingbong. |
| http://faq.mrball.net | Doug Glanville on espn.go.com |
Linux kernel 2.4.19-24mdk load average: 0.00, 0.03, 0.06
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (GNU/Linux)
Comment: http://www.mrball.net/todd.asc
iD8DBQE/Hg+GIBT1264ScBURAqnOAKDTjj00RGTjbjntqmkbXYrNge/diQCeOA91
s2hCNALL/S0jv851XkBsa1Y=
=X6sA
-----END PGP SIGNATURE-----
Want to buy your Pack or Services from MandrakeSoft?
Go to http://www.mandrakestore.com
