Re: [GNU Autoconf 2.61] testsuite: 18 99 110 136 177 251 failed

[Eric Blake]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hello Valery, and thanks for the report,

According to Valery Brodskiy on 9/24/2007 10:03 PM:

> uname -r = 2.2.14-5.0
> uname -s = Linux

Are there any known kernel bugs that might be fixed by upgrading to a
newer kernel?  I'm personally not familiar enough with how this might
affect your results.

| SHELL=${CONFIG_SHELL-'/bin/bash'}

It looks like autoconf prefers bash for your shell.  What version of bash
are you using?  Also, what version of perl do you have installed?

Many of your failures are of the form:

> 18. tools.at:682: testing ...
> ./tools.at:696: autoupdate
> --- /dev/null   Tue May  5 16:32:27 1998
> +++ /root/autoconf-2.61/tests/testsuite.dir/at-stderr   Mon Sep 24
21:37:18 2007
> @@ -0,0 +1 @@
> +/root/autoconf-2.61/tests/autom4te: Can't reopen pipe to command
substitution (fd 3): No child processes
> 18. tools.at:682: 18. autoupdating OLD to NEW (tools.at:682): FAILED
(tools.at:696)

Weird.  I don't think I've ever seen that from a shell before.  Do you
have some sort of ulimit set up that restricts the number of child
processes or file handles you can created?

On the other hand,

> 99. torture.at:568: testing ...
> ./torture.at:575: autoconf --force
> ./torture.at:575: /bin/sh -n configure
> ./torture.at:575: exit code was 139, expected 0
> 99. torture.at:568: 99. Define to a 2000-byte string (torture.at:568):
FAILED (torture.at:575)

here, you managed to cause a core dump in /bin/sh.  What shell do you have
installed as /bin/sh?  Is this a portability limit we need to code around?
 Could it also be a bug in this /bin/sh that is causing the 'no child
processes' command substitution problems?

Finally,

> 110. torture.at:1038: testing ...
...
> automake (GNU automake) 1.4
That's pretty old; perhaps you should upgrade to 1.9.6 or 1.10.
> automake: configure.in: installing `./install-sh'
>     error while copying

That sure didn't give us much details into the failure in copying.  Can
you determine anything further as to what went wrong?

- --
Don't work too hard, make some time for fun as well!

Eric Blake             address@hidden
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Cygwin)
Comment: Public key at home.comcast.net/~ericblake/eblake.gpg
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFG+cWv84KuGfSFAYARAlirAJsHfikp2amMv6trArU0VS4GUiLx2gCeILRZ
FoChl/qwkKG6vdF6z/rFuVg=
=xFV8
-----END PGP SIGNATURE-----