bug-autoconf
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[sr #110425] autoconf 2.70 generated configure file does not enable -std


From: Bruno Haible
Subject: [sr #110425] autoconf 2.70 generated configure file does not enable -std=gnu99 on Mac OS X 10.5
Date: Sat, 16 Jan 2021 05:50:00 -0500 (EST)
User-agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:84.0) Gecko/20100101 Firefox/84.0

URL:
  <https://savannah.gnu.org/support/?110425>

                 Summary: autoconf 2.70 generated configure file does not
enable -std=gnu99 on Mac OS X 10.5
                 Project: Autoconf
            Submitted by: haible
            Submitted on: Sat 16 Jan 2021 11:49:59 AM CET
                Category: None
                Priority: 5 - Normal
                Severity: 3 - Normal
                  Status: None
                 Privacy: Public
             Assigned to: None
        Originator Email: 
             Open/Closed: Open
         Discussion Lock: Any
        Operating System: Mac OS

    _______________________________________________________

Details:

This is a regression in autoconf 2.70, compared to version 2.69:

Take a tarball with C source code that makes use of C99 features. For
example:

./gnulib-tool --create-testdir --dir=../testdir5 --single-configure dfa

(with current gnulib).

Build it on Mac OS X 10.5, with CC="gcc -m64".

With autoconf 2.69, the config.status file contains

S["CC"]="gcc -m64 -std=gnu99"

and the compilation goes through.

With autoconf 2.70, the config.status file contains

S["CC"]="gcc -m64"

and the compilation fails with errors such as "error: 'for' loop initial
declaration used outside C99 mode".






    _______________________________________________________

Reply to this item at:

  <https://savannah.gnu.org/support/?110425>

_______________________________________________
  Message sent via Savannah
  https://savannah.gnu.org/




reply via email to

[Prev in Thread] Current Thread [Next in Thread]