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 [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-questions" in the body of the message