Bryan Kadzban wrote: > Bruce Dubbs wrote: >> I just noticed that we do not create /usr/local/lib64. Should be make >> /usr/local/lib64 a symlink to /usr/local/lib the way we have: >> >> ln -sv lib /lib64 >> ln -sv lib /usr/lib64 >> >> What I found was that some programs (e.g. gcc) will create a separate >> /usr/local/lib64 if installing in /usr/local. > > Yeah, there are a few packages I've run into that do "if config.guess > says something that looks like x86_64, use lib64". Which is exactly the > right thing to do for an x86_64 system, actually, but the standard > autoconf macros don't set libdir that way. > > #include <abi_spec_comment.h> :-) > > Of course, taken to an extreme, that would end up creating stuff like > /opt/<package>/lib64 symlinks. Which I don't think is feasible. > > But /usr/local/lib64 is probably fine. Or any other lib directory we > create (I don't think there are any others, but just in case).
Right now in /opt I have ant, jdk, kde, qt, xorg, and texlive that have lib directories, but only xorg has a lib64 and that's a symlink to lib. The only different location I have is in /usr/local and the only reason I have that is because I built the optional compilers for gcc and decided to put them in /usr/local. -- Bruce -- http://linuxfromscratch.org/mailman/listinfo/lfs-dev FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
