The first, reported by David re a ppc32 build failure. I don't understand why gcc_no_link would be true in that case, but it does point out a real bug. And possibly the same one that was reported against darwin overnight.
The second, pointed out by Jason re enabling maintainer mode. Both committed. r~
* acinclude.m4 (LIBAT_TEST_ATOMIC_BUILTIN): Handle compilation failure in gcc_no_link path. * configure: Rebuild. diff --git a/libatomic/acinclude.m4 b/libatomic/acinclude.m4 index 13206f0..65d9a22 100644 --- a/libatomic/acinclude.m4 +++ b/libatomic/acinclude.m4 @@ -74,6 +74,8 @@ AC_DEFUN([LIBAT_TEST_ATOMIC_BUILTIN],[ else eval $2=yes fi + else + eval $2=no fi CFLAGS="$old_CFLAGS" fi
diff --git a/libatomic/configure.ac b/libatomic/configure.ac index 18d1dea..1b4f325 100644 --- a/libatomic/configure.ac +++ b/libatomic/configure.ac @@ -144,6 +144,7 @@ AC_PROG_INSTALL AM_PROG_LIBTOOL AC_SUBST(enable_shared) AC_SUBST(enable_static) +AM_MAINTAINER_MODE # For libtool versioning info, format is CURRENT:REVISION:AGE libtool_VERSION=1:0:0