Follow-up Comment #5, sr #110403 (project autoconf):
I just ran the autoconf testsuite myself on this system, using the tip of
branch-2.70. I do *not* see AC_TYPE_INTMAX_T fail, but I *do* see two other
failures which appear to have the same root cause: config.status files with a
missing line break at the end of a here-document in the parent configure
script.
SHELL=${CONFIG_SHELL-/bin/sh}
export SHELL## -------------------- ##
## M4sh Initialization. ##
and
test -n "$AWK" || AWK=awk# The default lists apply if the user does not
specify any file.
In Bourne shell syntax, `#` only begins a comment if it is the *beginning* of
a shell word, so both of these turn into syntax errors.
To my surprise, this is *not* an intermittent fault. It happens every single
time I run the configure script for one of the tests that fails for me.
However, it doesn't happen if I run `bash ./configure` instead of
`./configure`, and it goes away if I add a single blank line near the top of
the offending configure script.
I think what we're looking at here is a bug in OmniOS /bin/sh, in which
here-documents lose their final \n character if they are at particular offsets
within a shell script. I'll see if I can come up with a precise test for that
hypothesis.
_______________________________________________________
Reply to this item at:
<https://savannah.gnu.org/support/?110403>
_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/
