Date: Mon, 24 Feb 2003 12:17:24 +1100 From: Sam Izzo <izzo@humbug.net> To: freebsd-questions@freebsd.org Subject: Re: linker paths & /usr/local/lib Message-ID: <20030224011724.GA296@kalgan.vic.optushome.com.au> In-Reply-To: <20030223165133.79e9aa2b.flynn@energyhq.homeip.net> References: <20030223152808.GA1391@kalgan.vic.optushome.com.au> <20030223165133.79e9aa2b.flynn@energyhq.homeip.net>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi On Sun, Feb 23, 2003 at 04:51:33PM +0100, Miguel Mendez wrote: > > and the command-line: > > > > gcc test.c -o test -lHermes > > > > You probably want something like this: > > cc -o test test.c -L/usr/local/lib -lHermes > Yeah that's all well and good for me compiling my own programs, but the OpenPTC `configure' checks for Hermes by writing the test program that I posted and linking with the above line :-) It doesn't put -L/usr/local/lib in. I suppose I can just hack the `configure' script but surely there's a better solution? > IIRC, ld.so.conf only affects the runtime dynamic linker, in a similar > way LD_LIBRARY_PATH does. Ahh, darn, that's not what the ld man page says :) But it didn't work when I put the paths in ld.so.conf so I guess it's wrong.. Thanks for your suggestions. sam 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?20030224011724.GA296>