On Mon, 2002-02-11 at 23:21, Kenneth Porter wrote: > Unfortunately the configure script can hide error messages that could > help in debugging this kind of thing. Find the spot in the script where > it makes the -ldrac test, run that part manually without the redirection > of stderr to /dev/null, and see what the real error message is.
I just looked at the script and it saves all redirected output to config.log. So you can inspect the end of that to see what really went wrong. I seem to recall a bug in the script that blames drac when something else is missing, but I don't recall the details.
