On 2010-11-30 17:21:35 +0000, Jonathan Wakely wrote: > Vincent, rather than using LIBRARY_PATH (which doesn't do what you > want when gcc-4.3.1 decides to look in $LIBRARY_PATH/../lib64) you > could use -L to ensure it looks in the directories you want. My example was just a simple test. In the reality, I use things like configure/make and so on, so that -L is not possible. I also want to avoid options that would need to be used potentially for any compilation. > Or you could add lib64 symlinks pointing to $HOME/gmp/athlon64/lib > and $HOME/x86_64/lib, so that you get consistent behaviour from > Debian's gcc and FSF gcc. Yes, I thought about that. And perhaps add a cron script that would check that I haven't forgotten anything (that would be useful if I add a new lib directory in a few years). Thanks for the answers. -- Vincent Lefèvre <vincent@xxxxxxxxxx> - Web: <http://www.vinc17.net/> 100% accessible validated (X)HTML - Blog: <http://www.vinc17.net/blog/> Work: CR INRIA - computer arithmetic / Arénaire project (LIP, ENS-Lyon)
