From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: Andy Wingo Newsgroups: gmane.lisp.guile.bugs Subject: bug#23034: AC_CHECK_HEADERS after GUILE_FLAGS loses $CPP Date: Tue, 28 Feb 2017 16:03:28 +0100 Message-ID: <87tw7el5mn.fsf@pobox.com> References: NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: blaine.gmane.org 1488295228 14465 195.159.176.226 (28 Feb 2017 15:20:28 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Tue, 28 Feb 2017 15:20:28 +0000 (UTC) User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/25.1 (gnu/linux) Cc: 23034-done@debbugs.gnu.org To: Bernd Jendrissek Original-X-From: bug-guile-bounces+guile-bugs=m.gmane.org@gnu.org Tue Feb 28 16:20:22 2017 Return-path: Envelope-to: guile-bugs@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by blaine.gmane.org with esmtp (Exim 4.84_2) (envelope-from ) id 1cijZd-00033y-EW for guile-bugs@m.gmane.org; Tue, 28 Feb 2017 16:20:21 +0100 Original-Received: from localhost ([::1]:33859 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1cijZj-0006fi-E2 for guile-bugs@m.gmane.org; Tue, 28 Feb 2017 10:20:27 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:51118) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1cijJv-0000lW-U0 for bug-guile@gnu.org; Tue, 28 Feb 2017 10:04:09 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1cijJq-0001GO-AP for bug-guile@gnu.org; Tue, 28 Feb 2017 10:04:07 -0500 Original-Received: from debbugs.gnu.org ([208.118.235.43]:33949) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1cijJq-0001GG-7O for bug-guile@gnu.org; Tue, 28 Feb 2017 10:04:02 -0500 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1cijJp-0000yH-Qt for bug-guile@gnu.org; Tue, 28 Feb 2017 10:04:01 -0500 Resent-From: Andy Wingo Original-Sender: "Debbugs-submit" Resent-To: bug-guile@gnu.org Resent-Date: Tue, 28 Feb 2017 15:04:01 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: cc-closed 23034 X-GNU-PR-Package: guile X-GNU-PR-Keywords: Mail-Followup-To: 23034@debbugs.gnu.org, wingo@pobox.com, bernd@bpj-code.co.za Original-Received: via spool by 23034-done@debbugs.gnu.org id=D23034.14882942193697 (code D ref 23034); Tue, 28 Feb 2017 15:04:01 +0000 Original-Received: (at 23034-done) by debbugs.gnu.org; 28 Feb 2017 15:03:39 +0000 Original-Received: from localhost ([127.0.0.1]:60379 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1cijJS-0000xZ-NK for submit@debbugs.gnu.org; Tue, 28 Feb 2017 10:03:38 -0500 Original-Received: from pb-sasl2.pobox.com ([64.147.108.67]:63340 helo=sasl.smtp.pobox.com) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1cijJQ-0000xR-Vq for 23034-done@debbugs.gnu.org; Tue, 28 Feb 2017 10:03:37 -0500 Original-Received: from sasl.smtp.pobox.com (unknown [127.0.0.1]) by pb-sasl2.pobox.com (Postfix) with ESMTP id B69E75F465; Tue, 28 Feb 2017 10:03:36 -0500 (EST) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=pobox.com; h=from:to:cc :subject:references:date:in-reply-to:message-id:mime-version :content-type; s=sasl; bh=AYTbtBaZ5xhqhQznEA88nFyZvck=; b=TNezG0 kupUJoqa2VtjhpyFGl8ZSQBVJ5d2eRnujYNSfptdegPOCKXQBATHCwxToewt2EDV Q9OZyXPYqMVdvZ0SNhf3plC5ZvuBR9GHM1H2uZ+QQfA8gL1nESUpKG/Sd1rxIQQ7 ZWIvnso/1EQhJfytWyjY5WJgQKEJtDGn4tRkc= DomainKey-Signature: a=rsa-sha1; c=nofws; d=pobox.com; h=from:to:cc :subject:references:date:in-reply-to:message-id:mime-version :content-type; q=dns; s=sasl; b=hHyOdrtmDDZsBQW5P7+oUcLD7O+8p2es fXArOKZjcve4vMW5pSvkHOpXTslCDwk2Nu6x3TtNo2HA6zzE2BBuLml0hEN53FKp bikekv8zsWU8WLaf7dkYhW8ZuP8Waj+YZGlhGtqGNbgG9/sHXvx6FLVuaFlChHqB Ar9lSenBikg= Original-Received: from pb-sasl2.nyi.icgroup.com (unknown [127.0.0.1]) by pb-sasl2.pobox.com (Postfix) with ESMTP id AE3FF5F464; Tue, 28 Feb 2017 10:03:36 -0500 (EST) Original-Received: from clucks (unknown [88.160.190.192]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by pb-sasl2.pobox.com (Postfix) with ESMTPSA id C47785F463; Tue, 28 Feb 2017 10:03:35 -0500 (EST) In-Reply-To: (Bernd Jendrissek's message of "Thu, 17 Mar 2016 03:47:04 +0200") X-Pobox-Relay-ID: 1432CD02-FDC7-11E6-AE04-6141F2301B6D-02397024!pb-sasl2.pobox.com X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 208.118.235.43 X-BeenThere: bug-guile@gnu.org List-Id: "Bug reports for GUILE, GNU's Ubiquitous Extension Language" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-guile-bounces+guile-bugs=m.gmane.org@gnu.org Original-Sender: "bug-guile" Xref: news.gmane.org gmane.lisp.guile.bugs:8589 Archived-At: On Thu 17 Mar 2016 02:47, Bernd Jendrissek 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