Hi Jan, On Mon, Jan 26, 2009 at 10:46 AM, Jan Ciger <[email protected]> wrote: > Strictly speaking, you can put the libraries wherever you want, it will > work with sufficient changes to the system config. However, it is good > to stay with the conventions others are using - it prevents a lot of > headaches.
Well many other projects are using /usr/local/lib for 64bit libs, I'm afraid from my experience that it's more prevalent than installing locally compiled libraries in /usr/local/lib64. Much as you may infer that /usr/local/lib64 is the standard and the convention, it certainly doesn't seem to be the dominant convention. Technically I would say I'd suggest /usr/local/lib64 is a better convention, but I think asserting /usr/local/lib for 64bit libs isn't appropriate is rather a stretch given it's widespread usage. > I checked on my Mandriva. I have only 32bit version available at the > moment, but it doesn't put even /usr/local/lib in the search path by > default. I have it defined in the LD_LIBRARY_PATH variable in my login > script. I think the idea has to do with security, so that if you want to > load some strange libraries, you need to enable it explicitly, but I may > be wrong there. Searching the archives it looked likes Debian used not add /usr/local/lib on the default library search path either, but now does. I can't imagine that there is really a security issue though, as you need super user to install to /usr/local/lib just as you do to /usr/lib so if a dodgy lib wants to infiltrate your system then /usr/lib is just an easy/hard a target as /usr/local/lib. > Regarding the existence of the /usr/local/lib64 folder: > > - - I have checked the existence of the folder and 64 bit Mandriva creates > the /usr/local/lib64 by default (as required by FHS) using the It's curious one would create a /usr/local/lib64 and then not provide a library path to it... Can any RedHat/CentOS/Fedora users tell use what /etc/ld.so.conf and /etc/ld.so.conf.d contain w.r.t pulling in /usr/local/lib? > The packages for stable releases will be provided either by the distros > themselves (e.g. Mandriva has OSG in the repositories like > that, but an ancient version - having a working upstream spec file would ease > the maintenance load) or somewhere online for > download, as you have for the Windows version. For OSG-2.8 I would really like to be able to get it into all the major Linux distribution repositories. Do you have a link to the Mandriva details on OSG? > If, as a developer, you require the convenience of not having to deal with > things like LD_LIBRARY_PATH, you are most likely > not going to build the SVN trunk neither and will get the pre-built binaries > for your distro instead. This is a good point, if you are going to compile from source you should at least should know about library paths etc. If you have trouble with the add to your LD_LIBRARY_PATH or patching /etc/ld.so.conf then you are going to have many other things to learn as well. Perhaps another solution would be to have CMake check where the installed library is on the search path or not, and if not to produce a suggestion of how to add it to the path. Robert. Robert. _______________________________________________ osg-users mailing list [email protected] http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
