Re: 'make check' test 6 fail, native hppa2.0w-hp-hpux11.00, autoconf 2.50 and autoconf 2.50b

[Akim Demaille]

| It looks like the problem occurs when an "^..." construct comes after
| the "_AC_" construct.   Look at this:
| 
|   address@hidden tmp]$ /bin/awk '/_AC_|^FORBIDDEN$/ { print "-: " $0}'
|   NOT_AC_ALLOWED
|   address@hidden tmp]$ /bin/awk '/_AC_|^FORBIDDEN/ { print "-: " $0}'
|   NOT_AC_ALLOWED
|   address@hidden tmp]$ /bin/awk '/_AC_|FORBIDDEN/ { print "-: " $0}'
|   NOT_AC_ALLOWED
|   -: NOT_AC_ALLOWED
| 
| And finally:
| 
|   address@hidden tmp]$ /bin/awk 
'/^m4_|^dnl$|^_?AS_|^_?A[CHUM]_|_AC_|FORBIDDEN$/ { print "-: " $0}'
|   NOT_AC_ALLOWED
|   -: NOT_AC_ALLOWED
| 
|   address@hidden tmp]$ /bin/awk 
'/^m4_|^dnl$|^_?AS_|^_?A[CHUM]_|^FORBIDDEN$|_AC_/ { print "-: " $0}'
|   NOT_AC_ALLOWED
|   -: NOT_AC_ALLOWED

Wow!

That's very weird.  It is usual to find RE engines that fail to handle
properly anchors when they are not first/last, but that's the first
time I find an engine that seems to handle them partly.

Anyway, I need to find a means not to use this AWK...

Just for my information, I'd like to have some more information about
it:

echo 'FORBIDDEN' | /bin/awk '/^FORBIDDEN$|_AC_/ { print "MATCH: " $0}'
echo '^FORBIDDEN' | /bin/awk '/^FORBIDDEN$|_AC_/ { print "MATCH: " $0}'
echo 'FORBIDDEN$' | /bin/awk '/^FORBIDDEN$|_AC_/ { print "MATCH: " $0}'
echo '^FORBIDDEN$' | /bin/awk '/^FORBIDDEN$|_AC_/ { print "MATCH: " $0}'

echo 'FORBIDDEN' | /bin/awk '/_AC_|^FORBIDDEN$/ { print "MATCH: " $0}'
echo '^FORBIDDEN' | /bin/awk '/_AC_|^FORBIDDEN$/ { print "MATCH: " $0}'
echo 'FORBIDDEN$' | /bin/awk '/_AC_|^FORBIDDEN$/ { print "MATCH: " $0}'
echo '^FORBIDDEN$' | /bin/awk '/_AC_|^FORBIDDEN$/ { print "MATCH: " $0}'

Also, could you remind me the characteristics of your machine? The
references of that AWK.  Is it the actual AWK that was chosen by
Autoconf's own configure?  I mean, what does

~/src/ace % grep AWK= autoconf                                   nostromo 10:03
: ${AWK=mawk}

answer?