autoconf-patches
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

AIX 4.3.3 failure: 245 AC_NO_EXECUTABLES (broken linker)


From: Ralf Wildenhues
Subject: AIX 4.3.3 failure: 245 AC_NO_EXECUTABLES (broken linker)
Date: Sat, 31 Oct 2009 17:25:56 +0100
User-agent: Mutt/1.5.20 (2009-08-09)

Failure like this:

#                             -*- compilation -*-
245. c.at:232: testing ...
../../autoconf/tests/c.at:232: autoconf --force -W obsolete
../../autoconf/tests/c.at:232: autoheader 
../../autoconf/tests/c.at:232: ./configure $configure_options -C
stdout:
configure: creating cache config.cache
checking for gcc... no
checking for cc... cc
checking whether we are cross compiling... yes
checking for suffix of object files... o
checking whether we are using the GNU C compiler... no
checking whether cc accepts -g... yes
checking for cc option to accept ISO C89... -qlanglvl=extc89
configure: updating cache config.cache
configure: creating ./config.status
config.status: creating config.h
../../autoconf/tests/c.at:232: at_check_env
../../autoconf/tests/c.at:232: ./configure $configure_options -C
stdout:
configure: loading cache config.cache
checking whether we are cross compiling... yes
checking for suffix of object files... (cached) o
checking whether we are using the GNU C compiler... (cached) no
checking whether cc accepts -g... (cached) yes
checking for cc option to accept ISO C89... (cached) -qlanglvl=extc89
configure: creating ./config.status
config.status: creating config.h
config.status: config.h is unchanged
../../autoconf/tests/c.at:232: at_check_env
0a1,2
> 8a9
> > conftest.err
../../autoconf/tests/c.at:232: exit code was 1, expected 0


The other notable thing is that the 'cc --version' invocation still puts
the whole compiler manpage in config.log, which was supposed to be fixed
by _AC_DO_LIMIT.  Gah, I wonder if later XLC releases produced that on
stderr or why I didn't catch that bug when writing _AC_DO_LIMIT.

I think that one bug is that _AC_RUN_LOG_LIMIT only removes conftest.err
if it is nonempty, and the other that we don't limit output from stdout.
The latter is a bit less obvious to do right though; at least it might
be valuable to have more than 10 lines from a decent --version output.

Anyway, the regression part of this is the leftover file only, which is
fixed by the patch below.  OK?

Thanks,
Ralf

commit 49fa7a12364563b24f328f9733620ca5b2611099
Author: Ralf Wildenhues <address@hidden>
Date:   Sat Oct 31 17:24:05 2009 +0100

    Fix testsuite failure on AIX 4.3.3.
    
    * lib/autoconf/general.m4 (_AC_RUN_LOG_LIMIT): Remove conftest.err
    also if it is empty.
    
    Signed-off-by: Ralf Wildenhues <address@hidden>

diff --git a/ChangeLog b/ChangeLog
index 27b0992..8370ecc 100644
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,5 +1,9 @@
 2009-10-31  Ralf Wildenhues  <address@hidden>
 
+       Fix testsuite failure on AIX 4.3.3.
+       * lib/autoconf/general.m4 (_AC_RUN_LOG_LIMIT): Remove conftest.err
+       also if it is empty.
+
        Fix testsuite failure on IRIX and AIX.
        * tests/torture.at (Substitute and define special characters):
        Double the backslash before the double-quote in
diff --git a/lib/autoconf/general.m4 b/lib/autoconf/general.m4
index bd19e82..03c0bf2 100644
--- a/lib/autoconf/general.m4
+++ b/lib/autoconf/general.m4
@@ -2305,8 +2305,9 @@ AC_DEFUN([_AC_RUN_LOG_LIMIT],
 ... rest of stderr output deleted ...
          m4_default([$3], [10])q' conftest.err >conftest.er1
     cat conftest.er1 >&AS_MESSAGE_LOG_FD
-    rm -f conftest.er1 conftest.err
+    rm -f conftest.er1
   fi
+  rm -f conftest.err
   _AS_ECHO_LOG([\$? = $ac_status])
   test $ac_status = 0; }])
 




reply via email to

[Prev in Thread] Current Thread [Next in Thread]