"A. van Werven" wrote:
>
> Cobalt:
>
> [Checking X lasts forever]
>
> First, let me assure you that waiting times of 30 mins or more are ridicu-
> lous, there must be something wrong.
>
> I'm afraid you'll have to dig into the configure script at the point where
> it starts checking for X.
>
> I know that most people find configure scripts bitches to read, but here's
> what I suggest: find where it starts checking (do a search in your
> favorite editor) and insert echos after each step. This might help you
> pinpoint where things go wrong (even something like "checking for foo",
> which seems like a single step to the outside world, actually consists of
> multiple steps).
>
> Seems like configure is waiting for something to terminate which doesn't.
A better way, might be to do a "sh -x configure" if you are lazy, and
look at the last lines before it stops. Or as in this case it might go
on and on in an endless loop, so you might have to terminate it with
CTRL+C when you see a repeating pattern.
Geir Kristiansen
