From: Andy Wingo <wingo@pobox.com>
To: Bernd Jendrissek <bernd@bpj-code.co.za>
Cc: 23034-done@debbugs.gnu.org
Subject: bug#23034: AC_CHECK_HEADERS after GUILE_FLAGS loses $CPP
Date: Tue, 28 Feb 2017 16:03:28 +0100 [thread overview]
Message-ID: <87tw7el5mn.fsf@pobox.com> (raw)
In-Reply-To: <CAF7PVPoL48NgDOw6p7YnWOGG_ppHwGBqbzk6Pa9iTjU1785Ong@mail.gmail.com> (Bernd Jendrissek's message of "Thu, 17 Mar 2016 03:47:04 +0200")
On Thu 17 Mar 2016 02:47, Bernd Jendrissek <bernd@bpj-code.co.za> writes:
> 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.
AFAIU then this is an autoconf bug? Weird. Weird also that autoconf is
just not releasing these days! I guess we close this from the Guile
point of view though, no?
Regarding autoconf releases:
http://lists.gnu.org/archive/html/autoconf/2016-12/msg00005.html
So, I will optimistically close this and this problem will go away once
autoconf 2.70 is out.
Andy
prev parent reply other threads:[~2017-02-28 15:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-17 1:47 bug#23034: AC_CHECK_HEADERS after GUILE_FLAGS loses $CPP Bernd Jendrissek
2017-02-28 15:03 ` Andy Wingo [this message]
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=87tw7el5mn.fsf@pobox.com \
--to=wingo@pobox.com \
--cc=23034-done@debbugs.gnu.org \
--cc=bernd@bpj-code.co.za \
/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).