Ralf Corsepius <[EMAIL PROTECTED]> writes:
[snip]
> Meanwhile, I think to have found the cause.
>
> Somehow, after having touched configure or configure.in, "make" runs
> the "include check" by recursively running make.
>
> Due to recursively running make, __gmake__ emits a "Entering
> directory ..." message to __stdout__, which interferes with
> autoconf's AM_MAKE_INCLUDE check, which expects a string containing
> plain "done" instead of
> "make[1]:Entering directory ..done", which it actually seems to
> receive.
That makes sense. I think those are supressed when you run GNU make
with the '-s' option. (The -s option was present in Unix 7th Edition
too, so it can pretty much be used with impunity.)
- Hari
--
Raja R Harinath ------------------------------ [EMAIL PROTECTED]
"When all else fails, read the instructions." -- Cahn's Axiom
"Our policy is, when in doubt, do the right thing." -- Roy L Ash
