Date: Mon, 24 Feb 2003 18:39:11 +1100 From: Sam Izzo <izzo@humbug.net> To: freebsd-questions@freebsd.org Subject: Re: linker paths & /usr/local/lib Message-ID: <20030224073911.GA10158@kalgan.vic.optushome.com.au> In-Reply-To: <20030224080534.61fa0166.flynn@energyhq.homeip.net> References: <20030223152808.GA1391@kalgan.vic.optushome.com.au> <20030223165133.79e9aa2b.flynn@energyhq.homeip.net> <20030224011724.GA296@kalgan.vic.optushome.com.au> <20030224080534.61fa0166.flynn@energyhq.homeip.net>
next in thread | previous in thread | raw e-mail | index | archive | help
> The configure scripts usually accept a parameter like > `--with-extra-libs=/usr/local/lib' that you could use. You can always > invoke configure with the --help option and check for it. Works most of > the time. Yeah, OpenPTC doesn't accept that parameter :/ > Most of the GNU tools are better documented in the info pages, as they > consider man pages legacy. info ld might turn up more detailed info. You know, I've read/heard that many times over the years, but whenever I look at the info page for whatever tool I'm after, it's exactly the same as the man page (in the ld case too). I can't stand info, mostly because I always forget the keys, and the "default" keys seem completely foreign and wrong to me that it just puts me off using it. man works well enough for me.. :-) Thanks anyway. 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?20030224073911.GA10158>