GNU bug report logs - #23034
AC_CHECK_HEADERS after GUILE_FLAGS loses $CPP

Previous Next

Package: guile;

Reported by: Bernd Jendrissek <bernd <at> bpj-code.co.za>

Date: Thu, 17 Mar 2016 01:50:01 UTC

Severity: normal

Done: Andy Wingo <wingo <at> pobox.com>

Bug is archived. No further changes may be made.

Full log

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: Bernd Jendrissek <bernd <at> bpj-code.co.za>
To: bug-guile <at> gnu.org
Subject: AC_CHECK_HEADERS after GUILE_FLAGS loses $CPP
Date: Thu, 17 Mar 2016 03:47:04 +0200

[Message part 1 (text/plain, inline)]
I have a reduced test case where adding GUILE_FLAGS in shell dead code
before a call to AC_CHECK_HEADERS causes configure to lose $CPP, which
results in warnings like this one:

checking stdarg.h usability... yes
checking stdarg.h presence... no
configure: WARNING: stdarg.h: accepted by the compiler, rejected by
the preprocessor!
configure: WARNING: stdarg.h: proceeding with the compiler's result
checking for stdarg.h... yes

Versions:

/usr/share/aclocal/guile.m4: guile-2.0-dev from Debian jessie (2.0.11+1-9)
autoconf: 2.69

Attached:

configure.ac
guile.m4

To reproduce:

Find a config.rpath somewhere (perhaps steal it from gettext).
autoreconf -fi
./configure

I noticed that a random recent git HEAD of autoconf avoids this
problem; it turns out that in commit
11f520c61d8b21f1522968d6e6afb899070f0a6f autoconf transitions to
compilation-only header checks.

[configure.ac (application/octet-stream, attachment)]
[guile.m4 (application/x-m4, attachment)]
This bug report was last modified 8 years and 144 days ago.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.