[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [GNU Autoconf 2.60] testsuite: 3 133 135 failed
From: |
Ralf Wildenhues |
Subject: |
Re: [GNU Autoconf 2.60] testsuite: 3 133 135 failed |
Date: |
Thu, 26 Oct 2006 07:02:57 +0200 |
User-agent: |
Mutt/1.5.13 (2006-08-11) |
Hello Jeph,
Thanks for the report.
* Jeph Cowan wrote on Wed, Oct 25, 2006 at 06:33:13PM CEST:
>
> Attached is the testsuite.log file with more info on the failed tests.
The failure of test 3 is due to a bug in Autoconf's test suite; it can
safely be ignored.
The failures of the AC_F77_WRAPPERS and AC_FC_WRAPPERS tests look like
an installation problem with either GCC or the assembler on your system,
all compilation tests fail:
> configure:2858: checking whether we are using the GNU C compiler
> configure:2895: gcc -c conftest.c >&5
> Assembler:
> /tmp//cchBVANa.s: line 9: Only .llong should be used for relocatable
> expressions.
> configure:2901: $? = 1
> configure: failed program was:
> | /* confdefs.h. */
> | #define PACKAGE_NAME ""
> | #define PACKAGE_TARNAME ""
> | #define PACKAGE_VERSION ""
> | #define PACKAGE_STRING ""
> | #define PACKAGE_BUGREPORT ""
> | /* end confdefs.h. */
> |
> | #ifdef F77_DUMMY_MAIN
> |
> | # ifdef __cplusplus
> | extern "C"
> | # endif
> | int F77_DUMMY_MAIN() { return 1; }
> |
> | #endif
> | int
> | main ()
> | {
> | #ifndef __GNUC__
> | choke me
> | #endif
> |
> | ;
> | return 0;
> | }
> configure:2935: result: no
Once you figure out how to fix that, those tests should pass.
> Also
> note that the 'make check' was started at 8:28AM and finished the following
> morning at 00:46, some 16+ hours later. Am I doing something wrong?
No. The native AIX shell really is so much slower than a decent shell
when handling large and complex shell scripts. It helps _a lot_ to use
bash on AIX. I think you can do that by configuring packages this way,
assuming bash is installed as /bin/bash:
CONFIG_SHELL=/bin/bash /bin/bash ./configure CONFIG_SHELL=/bin/bash
> The
> same check ran in about 20 minutes on one of our linux systems. Are there
> serious repercussions due to the failed tests so that I shouldn't install
> the software?
No, except maybe that Autoconf should find and a better shell by itself.
It's not so easy however to efficiently test for "is this shell
agonizingly slow" in a configure script. You can install Autoconf
and use it as you like.
Cheers,
Ralf