Gary V. Vaughan wrote:
> Peter's patch works perfectly fine
Thanks to both of you. I changed the AC_LINK_IFELSE to an AC_COMPILE_IFELSE
and added stricter check that it really works. Also I changed the indentation
to match gnulib style.
Tested:
- GNU C -> yes
- OSF/1 "cc"-
On Jul 24, 2007, at 8:50 PM, Gary V. Vaughan wrote:
On Jul 23, 2007, at 6:14 PM, Peter O'Gorman wrote:
On Mon, 2007-07-23 at 23:27 +0200, Bruno Haible wrote:
Hello,
mkdir confdir1
mkdir confdir2
echo ... > confdir1/conftest.h
echo ... > confdir2/conftest.h
save_CPPFLAGS="$CPPFLAGS"
On Jul 23, 2007, at 6:14 PM, Peter O'Gorman wrote:
On Mon, 2007-07-23 at 23:27 +0200, Bruno Haible wrote:
Hello,
mkdir confdir1
mkdir confdir2
echo ... > confdir1/conftest.h
echo ... > confdir2/conftest.h
save_CPPFLAGS="$CPPFLAGS"
CPPFLAGS="$CPPFLAGS -Iconfdir1 -Iconfdir2"
AC_PREP
On Mon, 2007-07-23 at 23:27 +0200, Bruno Haible wrote:
> Hello,
> mkdir confdir1
> mkdir confdir2
> echo ... > confdir1/conftest.h
> echo ... > confdir2/conftest.h
> save_CPPFLAGS="$CPPFLAGS"
> CPPFLAGS="$CPPFLAGS -Iconfdir1 -Iconfdir2"
> AC_PREPROC_IFELSE([#include ], ...)
> CPPFLA
Hello,
Peter O'Gorman wrote:
> include_next.m4 incorrectly deduces that this compiler understands
> #include_next. The compiler issues a warning rather than an error when
> it sees it.
>
> This should fix:
> --- m4/include_next.m4~ 2007-07-18 03:21:47.089858027 +
> +++ m4/include_next.m4 20
On Sun, 2007-07-22 at 17:50 -0400, Gary V. Vaughan wrote:
>
> The compile completes. I suspect the problem affects all @INCLUDE_NEXT@
> using files on this host (stdio_.h is the only one that I've tripped
> over
> so far).
include_next.m4 incorrectly deduces that this compiler understands
#inc
A few weeks ago it worked, but updating my gnulib repository and
rerunning
gnulib-tool now breaks my builds on powerpc-ibm-aix4.3.3.0 as follows:
xlc -DHAVE_CONFIG_H -I. -I. -I.. -DCAIRO_NO_MUTEX -O2 -qro -
qroconst -qmaxmem=-1 -qarch=com -c printf-args.c -DPIC -o .libs/
printf-args.o
".
