Re: [GNU Autoconf 2.65] testsuite: 74 192 283 284 285 286 289 failed

[Ralf Wildenhues]

Hello,

thanks for the report.  See below for questions.

* address@hidden wrote on Tue, Mar 09, 2010 at 05:03:30PM CET:
> uname -m = i686
> uname -r = 2.6.24.5-smp
> uname -s = Linux
> uname -v = #2 SMP Wed Apr 30 13:41:38 CDT 2008
[...]

> 74. m4sh.at:250: testing ...
> ./m4sh.at:287: autom4te --language=m4sh script.as -o script 
> ./m4sh.at:288: $CONFIG_SHELL ./script
> --- /dev/null 2005-11-21 03:22:37.000000000 +0000
> +++ /root/autoconf-2.65/tests/testsuite.dir/at-groups/74/stderr       
> 2010-03-09 15:31:46.000000000 +0000
> @@ -0,0 +1,2 @@
> +./script: line 391: unexpected EOF while looking for matching ``'
> +./script: line 397: syntax error: unexpected end of file
> ./m4sh.at:288: exit code was 2, expected 0
> 74. m4sh.at:250: 74. AS_ECHO and AS_ECHO_N (m4sh.at:250): FAILED (m4sh.at:288)

Which shell is your /bin/sh?

> 192. autotest.at:1436: testing ...
> ./autotest.at:1488: autom4te --language=autotest -o suite suite.at
> ./autotest.at:1496: autoconf --force 
> ./autotest.at:1496: /bin/sh -n configure
> ./autotest.at:1497: ./configure $configure_options 
> --- /dev/null 2005-11-21 03:22:37.000000000 +0000
> +++ /root/autoconf-2.65/tests/testsuite.dir/at-groups/192/stderr      
> 2010-03-09 15:33:42.000000000 +0000
> @@ -0,0 +1,3 @@
> +configure: error: in `/root/autoconf-2.65/tests/testsuite.dir/192':
> +configure: error: test Erlang program execution failed
> +See `config.log' for more details.
> stdout:
> checking for erl... /usr/bin/erl
> checking for erlc... /usr/bin/erlc
> checking for Erlang/OTP 'eunit' library subdirectory... ./autotest.at:1497: 
> exit code was 1, expected 0
> t/suite.log:
> sed: can't read t/suite.log: No such file or directory
> config.log:
[...]
> > configure:1746: checking for erl
> > configure:1764: found /usr/bin/erl
> > configure:1776: result: /usr/bin/erl
> > configure:1851: checking for erlc
> > configure:1869: found /usr/bin/erlc
> > configure:1881: result: /usr/bin/erlc
> > configure:1911: checking for Erlang/OTP 'eunit' library subdirectory
> > configure:1942: $ERLC $ERLCFLAGS -b beam conftest.$ac_ext >&5 && echo 
> > "#!/bin/sh" > conftest$ac_exeext && $as_echo "\"$ERL\" -run conftest start 
> > -run init stop -noshell" >> conftest$ac_exeext && chmod +x 
> > conftest$ac_exeext
> > File has wrong extension: beam
> > configure:1942: $? = 1
> > configure: program exited with status 1
> > configure: failed program was:
> > | -module(conftest).
> > | -export([start/0]).
> > | 
> > | start() ->
> > |       ReturnValue = case code:lib_dir("eunit") of
> > |       {error, bad_name} ->
> > |           file:write_file("conftest.out", "not found\n"),
> > |           1;
> > |       LibDir ->
> > |           file:write_file("conftest.out", LibDir),
> > |           0
> > |       end,
> > |       halt(ReturnValue)
> > | .
> > | 
> > configure:1947: error: in `/root/autoconf-2.65/tests/testsuite.dir/192':
> > configure:1950: error: test Erlang program execution failed

What does it mean for $ERLC to reject extension 'beam'?  Is this a
broken Erlang installation, or an unlelated program?  Let's CC: the
Erlang expert on this.

Cheers,
Ralf