[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: autoconf-2.72d on Solaris 11 OpenIndiana: testsuite: 260 445 446 510
From: |
Zack Weinberg |
Subject: |
Re: autoconf-2.72d on Solaris 11 OpenIndiana: testsuite: 260 445 446 510 failed |
Date: |
Sat, 02 Dec 2023 11:24:43 -0500 |
User-agent: |
Cyrus-JMAP/3.9.0-alpha0-1178-geeaf0069a7-fm-20231114.001-geeaf0069 |
On Sat, Dec 2, 2023, at 6:05 AM, Bruno Haible wrote:
> On Solaris OpenIndiana/x86_64, with
> - GNU m4 version 2022-12-24
> - 'awk --version' => awk version Aug 27, 2018
> - no bison, but yacc
> "make check" gives 4 test failures.
>
> Failed tests:
> GNU Autoconf 2.72d test suite test groups:
>
> NUM: FILE-NAME:LINE TEST-GROUP-NAME
> KEYWORDS
>
> 260: torture.at:189 AC_CONFIG_FILES, HEADERS, LINKS and COMMANDS
> 445: semantics.at:1255 AC_PROG_LEX with noyywrap
> 446: semantics.at:1257 AC_PROG_LEX with yywrap
> 510: acprograms.at:22 AC_DECL_YYTEXT
I can reproduce the lex-related failures (445/446/510) on
OmniOS/x86_64 using a custom PATH that excludes bison and flex; expect
a patch shortly.
I have not been able to reproduce the failure of test #260. Comparing
your test log file to mine, it looks like this might depend on
specifics of awk and/or sh. (The OmniOS system I’m using has a
/bin/sh that describes itself as “sh (AT&T Research) 93t+ 2010-03-05”,
and a bare ‘awk’ that has no version number and is not the same as
nawk or gawk, both of which are also available on the base system.
config.status specifically uses /bin/sh [to begin with], and bare awk,
regardless of what other tools are available.)
(your #260)
| ../../tests/torture.at:324: ./config.status --header=-:input </dev/null
>/dev/full || exit 1
| stderr:
| awk: i/o error occurred while closing /dev/stdout
| input record number 1, file input
| source line number 38
| stdout:
| ../../tests/torture.at:324: exit code was 0, expected 1
(my #260)
| ../../autoconf-2.72d/tests/torture.at:324: ./config.status --header=-:input
</dev/null >/dev/full || exit 1
| stderr:
| ./config.status[978]: printf: write to 1 failed [No space left on device]
| config.status: error: could not create -
| stdout:
In order to figure out exactly what happened here, it would be really
helpful if you could go into tests/testsuite.dir/260 and run this
command and send me the *complete and unedited* output:
$ /bin/sh -x ./config.status --header=-:input </dev/null >/dev/full; echo $?
zw