Date: Fri, 3 Jan 2003 22:46:01 -0600 From: Dan Nelson <dnelson@allantgroup.com> To: Justin Hopper <jhopper@spry.com> Cc: Matthew Emmerton <matt@gsicomp.on.ca>, freebsd-questions@FreeBSD.ORG Subject: Re: Mysterious problem with ldconfig and ld Message-ID: <20030104044600.GB4996@dan.emsphone.com> In-Reply-To: <1041654912.27258.36.camel@home.gusalmighty.com> References: <1041652526.27245.29.camel@home.gusalmighty.com> <004001c2b3a6$b3c4fe10$1200a8c0@gsicomp.on.ca> <1041654912.27258.36.camel@home.gusalmighty.com>
next in thread | previous in thread | raw e-mail | index | archive | help
In the last episode (Jan 03), Justin Hopper said: > Hmmm, I guess I just assumed that since ldconfig had cached the > absolute path to the library, ld would not need to know the library > path as well, but for some reason it did. > > What ultimately fixed the problem was hardcoding the -L > /usr/local/lib in the configure script, since it refused to pick up > that directory any other way. > > Thanks for your help. As a point of curiosity, I'd still like to > know why ld would still need the -L /usr/local/lib if the full path > to the library is already in the cache? what cache? ld and the run-time linker are separate entities and share no inrofmation. -- Dan Nelson dnelson@allantgroup.com 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?20030104044600.GB4996>