Date: Mon, 29 Mar 1999 09:53:05 +0100 From: Karl Pielorz <kpielorz@tdx.co.uk> Cc: freebsd-questions@FreeBSD.ORG Subject: Re: Seeing new libs in /usr/local/lib? (ldconfig?) Message-ID: <36FF3F71.E418E120@tdx.co.uk> References: <36FEC784.BC51505E@tdx.co.uk> <19990328181433.B32089@bear.berkeleycs.ml.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Spam Me Here wrote: > > Their are two things you can do, first for ldconfig, to get it to scan > /usr/local/lib, you would type > > ldconfig /usr/local/lib > > to get your program to find libraries in /usr/local/lib, you should > set LD_LIBRARY_PATH to /usr/local/lib Thanks for the reply... Sadly neither of the above worked. The compilation process still bombs out while looking for 'libttf.a' - which is blatently in /usr/local/lib If I run 'ldconfig -v -aout' I get a huge stream of library names pass by... If I do the same with 'ldconfig -v -elf' I get nothing - is this right? I've read the man page for ldconfig, but I'm really much more enlightened... :( The library was built recently on my machine - so I assume it's going to be elf? - I'm still not sure why it will see the libgd.a, but not libttf.a - If I even just symlink libttf.a to /usr/lib the compile goes OK, but I don't really want to do this... Anything else I can try? Regards, Karl 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?36FF3F71.E418E120>