bug-gnulib@gnu.org mirror (unofficial)
 help / color / mirror / Atom feed
From: Zack Weinberg <zackw@panix.com>
To: Ross Burton <ross@burtonini.com>
Cc: Autoconf <autoconf@gnu.org>, Gnulib bugs <bug-gnulib@gnu.org>
Subject: Re: Request to revert the C version change
Date: Sun, 20 Dec 2020 09:49:55 -0500	[thread overview]
Message-ID: <CAKCAbMgncJtGr39rPY73+SRDYXxFzb4d8Fn0u8OSDZqtz_mJWw@mail.gmail.com> (raw)
In-Reply-To: <CAKCAbMjSsJK8hkgkT+OTGcOrUqJGUvptZmK3AeC9ZsmVGAD1TQ@mail.gmail.com>

On Wed, Dec 16, 2020 at 2:02 PM Zack Weinberg <zackw@panix.com> wrote:
> On Wed, Dec 16, 2020 at 1:52 PM Ross Burton <ross@burtonini.com> wrote:
> > | checking for gcc  option to enable C11 features... none needed
> > | ../bison-3.7.4/configure: line 6187: syntax error near unexpected
> > token `ac_cv_prog_cc_stdc=$ac_cv_prog_cc_c89'
> > | ../bison-3.7.4/configure: line 6187: `
> > ac_cv_prog_cc_stdc=$ac_cv_prog_cc_c89'
> >
> > gettext failed in the same manner.
> >
> > I can bisect and identify where it broke tomorrow.
>
> Thanks.  This is definitely not a failure I saw in my testing, but it
> smells like another typo in the shell code, so hopefully not hard to
> fix.

The problem appears to be that gnulib's std-gnu11.m4 replaces *most*
of the definition of AC_PROG_CC, in a way that conflicts with the
refactor.  I'm looking for a way to avoid the conflict within autoconf
proper, but a workaround is to apply this patch to std-gnu11.m4:

$ diff -u m4/std-gnu11.m4{~,}
--- m4/std-gnu11.m4~    2020-08-30 11:27:01.000000000 -0400
+++ m4/std-gnu11.m4    2020-12-20 09:43:13.001477099 -0500
@@ -27,6 +27,8 @@
 # François Pinard, Karl Berry, Richard Pixley, Ian Lance Taylor,
 # Roland McGrath, Noah Friedman, david d zuhn, and many others.

+m4_version_prereq([2.70], [], [
+

 # AC_PROG_CC([COMPILER ...])
 # --------------------------
@@ -822,3 +824,5 @@
 dnl with extended modes being tried first.
 [[-std=gnu++11 -std=c++11 -std=gnu++0x -std=c++0x
-qlanglvl=extended0x -AA]], [$1], [$2])[]dnl
 ])# _AC_PROG_CXX_CXX11
+
+])# m4_version_prereq

I recommend this patch be applied in Gnulib proper.  It may be wise to
go through all of gnulib's m4 files and see if any others need the
same treatment.  (Any m4 file that backports code from the development
series leading up to 2.70 is a candidate.)

zw


       reply	other threads:[~2020-12-20 14:50 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAAnfSTuEDX_Wv+GtdRuRVtr72qP5oZQEJ12BVOMyTHx9mtMNCg@mail.gmail.com>
     [not found] ` <CAKCAbMic4FXC-aDz1BRXH6T-obyQEbTLKCA1-YFc-82jDbF6Fg@mail.gmail.com>
     [not found]   ` <CAAnfSTu5zYm=4zrpHf-i8x9tyXBLJ-4yy+BJLKM-HFncLvm3zw@mail.gmail.com>
     [not found]     ` <CAKCAbMjSsJK8hkgkT+OTGcOrUqJGUvptZmK3AeC9ZsmVGAD1TQ@mail.gmail.com>
2020-12-20 14:49       ` Zack Weinberg [this message]
2020-12-20 16:46         ` Request to revert the C version change Bruno Haible
2020-12-20 16:54           ` Ross Burton
2020-12-20 17:09             ` Zack Weinberg
2020-12-20 17:48               ` Zack Weinberg
2020-12-23 19:20               ` Zack Weinberg
2021-01-04 14:23                 ` Ross Burton
2020-12-20 17:02           ` Zack Weinberg
2020-12-23 20:04         ` gnulib / autoconf sync Bruno Haible
2020-12-23 20:13           ` Bruno Haible
2020-12-24  0:58             ` Autoconf version number after 2.70 Paul Eggert

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://lists.gnu.org/mailman/listinfo/bug-gnulib

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAKCAbMgncJtGr39rPY73+SRDYXxFzb4d8Fn0u8OSDZqtz_mJWw@mail.gmail.com \
    --to=zackw@panix.com \
    --cc=autoconf@gnu.org \
    --cc=bug-gnulib@gnu.org \
    --cc=ross@burtonini.com \
    /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).