Date: Sat, 9 Jan 1999 16:41:23 -0800 (PST) From: Brian Tiemann <btman@ugcs.caltech.edu> To: freebsd-questions@FreeBSD.ORG Subject: Linux shared libraries (RealAudio) Message-ID: <Pine.BSF.4.05.9901091626370.22985-100000@lionking.org>
next in thread | raw e-mail | index | archive | help
(please reply via e-mail; I'm not subscribed to freebsd-questions currently.) Okay... so I'm trying to use the Linux RealPlayer 5.0, since they seem to have given up on development for the FreeBSD version at 3.0 (bah). My system is 3.0-CURRENT (elf). Now, granted, it works just fine. That is, it works great if I run rvplayer from within the directory containing all the RealPlayer *.so files (i.e., the install dir). if the *.so files are somewhere else, well... that's a different story. :) What I'd love to be able to do (for instance, for firing up the player out of Netscape) is to put the shared library files into /usr/local/lib (or a subdir), and have ldconfig add those so rvplayer can find them. Real's documentation suggests setting LD_LIBRARY_PATH to the RealPlayer install directory, but I don't wanna. :) I've tried putting the *.so files into /usr/local/lib, /usr/local/lib/rvplayer, and /usr/lib/compat, and then re-running the ldconfig loop from /etc/rc. However, this doesn't register any of the new *.so files. All it seems to find are the "authorized" *.so.* files, with all the symlinks and aliases and things. So my question is this... what do I need to do in order to make ldconfig see these new files? Do I need to have that wacky symlink structure of -lwhatever.# = libwhatever.so.# -> libwhatever.so and so on? The whole ld thing is just the teensiest bit esoteric to someone who doesn't stir them around on a daily basis... :) So what's the secret? Brian 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?Pine.BSF.4.05.9901091626370.22985-100000>