> Correct, the -L I am aware of. My problem is that I am trying to compile a
> program that uses a configure script to check certain things, among which
> are that ld can find all libraries specified with the -l flag. The problem
> is that that this particular configure script does not honor my -L flags
> that I try to pass it, so it fails.
Almost all of these script things understand being told about extra
library search paths.
> The whole thing works on Linux, which
> is where this particular program was developed (I think).
This was probably a mistake.
> I can get it to
> work by making symlinks from the libs in /usr/local/lib to /usr/lib, but
> this completely defeats the purpose of having a /usr/local/lib... I could
> hack the configure script, but aside from being a pain in the butt (it is a
> 44,000 line configure script!) I don't want to have to do that for every
> program that I try to install that expects ld to be able to find standard
> libraries.
These aren't "standard" libraries, which is why they're not in /usr/lib.
Unfortunately, fixing the configuration script is the only way to go. If
it's been generated by autoconf, fix the autoconf input and save yourself
a lot of grief.
> Any insight would be greatly appreciated.
You're too kind, I think. 8)
--
... every activity meets with opposition, everyone who acts has his
rivals and unfortunately opponents also. But not because people want
to be opponents, rather because the tasks and relationships force
people to take different points of view. [Dr. Fritz Todt]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
