[Openal] OpenAL Link problem

Sven Panne Sven.Panne at BenQ.com
Thu Sep 21 00:49:20 PDT 2006


> -----Original Message-----
> From: openal-bounces at opensource.creative.com 
> [mailto:openal-bounces at opensource.creative.com] On Behalf Of 
> Louis Desjardins
> Sent: Mittwoch, 20. September 2006 22:00
> To: openal at opensource.creative.com
> Subject: RE: [Openal] OpenAL Link problem
> 
> [...]
> no idea really why it didnt work in /usr/local/lib though
> [...]

The question is: Where does the dynamic linker on your platform look for
dynamic libraries and does it use some form of caching? On most (all?)
Linux versions ld.so is the dynamic linker, so "man ld.so" might give
you some hints about what is going on. ld.so normally looks into /lib
and /usr/lib only, but can be told to look into other directories via
/etc/ld.so.conf, as Jason already mentioned. The second gotcha is that
one might have to run "ldconfig" to update the dynamic linker's cache of
candidate directories/libraries and the symbolic links you have already
encountered.

On my SuSE Linux, /usr/local/lib is mentioned in /etc/ld.so.conf and the
YaST package installer runs ldconfig automatically. If you compile and
install by hand and don't want to set LD_LIBRARY_PATH every time, you
can either edit ld.so.conf (but this might be against your
distribution's "spirit") or you can specify "--prefix /usr" in the
configuration stage, so everything will go into /usr instead of
/usr/local. Or even better: Use rpmbuild to build the packages for
yourself and install these packages then, .spec files are provided with
the OpenAL SI and freealut.

Cheers,
   S.



More information about the Openal mailing list