Follow-up Comment #2, sr #110403 (project autoconf):
Thanks for the testsuite directory attachment. The problem is clearer now:
# Set up the scripts for CONFIG_HEADERS section.
# No need to generate them if there are no CONFIG_HEADERS.
# This happens for instance with `./config.status Makefile'.
if test -n "$CONFIG_HEADERS"; then
cat >"$ac_tmp/defines.awk" <<\_ACAWK ||
BEGIN {
D["PACKAGE_NAME"]=" \"\""
...
}
{ print }
_ACAWK as_fn_error $? "could not setup config headers machinery" "$LINENO" 5
fi # test -n "$CONFIG_HEADERS"
In a correctly generated config.status, the `as_fn_error` would not be on the
same line as `_ACAWK`. However, the code that generates this part of
config.status hasn't changed in years either, and the corresponding piece of
the configure script in this test is exactly as it ought to be:
{ print }
_ACAWK
_ACEOF
cat >>$CONFIG_STATUS <<\_ACEOF || ac_write_fail=1
as_fn_error $? "could not setup config headers machinery" "$LINENO" 5
fi # test -n "$CONFIG_HEADERS"
So I'm still suspicious of some kind of intermittent fault in the shell
executing this configure script.
> As a reminder, you have login access to this system.
I seem to have lost the message in which you told me the *name* of this
system, could you tell me what it is again?
_______________________________________________________
Reply to this item at:
<https://savannah.gnu.org/support/?110403>
_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/
