From: Bernd Jendrissek <bernd@bpj-code.co.za>
To: 23034@debbugs.gnu.org
Subject: bug#23034: AC_CHECK_HEADERS after GUILE_FLAGS loses $CPP
Date: Thu, 17 Mar 2016 03:47:04 +0200 [thread overview]
Message-ID: <CAF7PVPoL48NgDOw6p7YnWOGG_ppHwGBqbzk6Pa9iTjU1785Ong@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 870 bytes --]
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.
[-- Attachment #2: configure.ac --]
[-- Type: application/octet-stream, Size: 209 bytes --]
AC_INIT([guileflags], [1.5.0], [foo@example.com])
AC_PREREQ(2.54)
# Checks for programs.
AC_PROG_CC
if false
then
GUILE_FLAGS
fi
AC_CHECK_HEADERS([stdarg.h])
echo "ac_cpp=$ac_cpp CPP=$CPP" >&6
AC_OUTPUT
[-- Attachment #3: guile.m4 --]
[-- Type: application/x-m4, Size: 13059 bytes --]
next reply other threads:[~2016-03-17 1:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-17 1:47 Bernd Jendrissek [this message]
2017-02-28 15:03 ` bug#23034: AC_CHECK_HEADERS after GUILE_FLAGS loses $CPP Andy Wingo
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAF7PVPoL48NgDOw6p7YnWOGG_ppHwGBqbzk6Pa9iTjU1785Ong@mail.gmail.com \
--to=bernd@bpj-code.co.za \
--cc=23034@debbugs.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).