[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[sr #110394] Support optional use of the C++ compiler in AC_PROG_CXX (an
From: |
Zack Weinberg |
Subject: |
[sr #110394] Support optional use of the C++ compiler in AC_PROG_CXX (and similarly for other languages) |
Date: |
Sun, 6 Dec 2020 17:25:59 -0500 (EST) |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Firefox/78.0 |
URL:
<https://savannah.gnu.org/support/?110394>
Summary: Support optional use of the C++ compiler in
AC_PROG_CXX (and similarly for other languages)
Project: Autoconf
Submitted by: zackw
Submitted on: Sun 06 Dec 2020 10:25:57 PM UTC
Category: None
Priority: 5 - Normal
Severity: 1 - Wish
Status: None
Privacy: Public
Assigned to: None
Originator Email:
Open/Closed: Open
Discussion Lock: Any
Operating System: None
_______________________________________________________
Details:
Bug #110294 reports a regression in autoconf 2.70 on the configure script for
a program that has some C and some C++ code, but use of the C++ code is
optional. The code that broke attempts to do most of what AC_PROG_CXX does,
but *not* abort the configure script when a C++ compiler is not found.
Instead, output variables would be set so that compilation of C++ code is
disabled.
We do not want to support this particular kludge, as it would pin down the
guts of AC_PROG_CXX too much, but we _should_ support optional use of the
$LANG compiler (for all values of $LANG). Perhaps with an additional argument
to AC_PROG_CC, AC_PROG_CXX, etc, marking usage optional.
See also bug #110286.
_______________________________________________________
Reply to this item at:
<https://savannah.gnu.org/support/?110394>
_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/
- [sr #110394] Support optional use of the C++ compiler in AC_PROG_CXX (and similarly for other languages),
Zack Weinberg <=