[Top][All Lists]

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

[bug #63097] 0.21 build setup breaks Automake "compile" wrapper script

From: Peter Williams
Subject: [bug #63097] 0.21 build setup breaks Automake "compile" wrapper script
Date: Fri, 23 Sep 2022 11:28:16 -0400 (EDT)


                 Summary: 0.21 build setup breaks Automake "compile" wrapper
                 Project: GNU gettext
               Submitter: pkgw
               Submitted: Fri 23 Sep 2022 03:28:15 PM UTC
                Category: Build
                Severity: 3 - Normal
              Item Group: None
                  Status: None
                 Privacy: Public
             Assigned to: None
             Open/Closed: Open
         Discussion Lock: Any


Follow-up Comments:

Date: Fri 23 Sep 2022 03:28:15 PM UTC By: Peter Williams <pkgw>
In attempting to build gettext with MSVC on Windows, I've discovered that the
build system of the 0.21 release has an issue that breaks Automake's "compile"
wrapper script, used to support compilers that don't accept "-c" and "-o" at
the same time or have other quirky behavior.

The problem is easy to demonstrate. There isn't even a "compile" script in the
"build-aux" subdirectory, as can be found in previous releases.

The issue appears to be the new "std-gnu11.m4" gnulib script. Unlike other
scripts that alter the C compiler detection, this script completely overwrites
the definition of the AC_PROG_CC macro. This seems to erase the work done in
aclocal's "init.m4" file, which extends AC_PROG_CC to also invoke
_AM_PROG_CC_C_O. A variety of other M4 files seem to also extend AC_PROG_CC in
a similar way, and the behavior of the std-gnu11 script may break those as

If, as an example workaround, I blank out the std-gnu11.m4 files in the
gettext source tree and run "autoreconf", the "compile" script starts
appearing in build-aux and the relevant code is re-added to the output
"configure" script.

I'd say that this is essentially a bug in gnulib, but there's a question as to
the right course of action to work around it here in gettext.


Reply to this item at:


Message sent via Savannah

reply via email to

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