* [PATCH] top-level: Fix comment about --enable-libstdcxx in configure
@ 2022-03-11 18:38 Jonathan Wakely
2022-03-14 13:13 ` Jonathan Wakely
0 siblings, 1 reply; 2+ messages in thread
From: Jonathan Wakely @ 2022-03-11 18:38 UTC (permalink / raw)
To: gcc-patches
I'm going to push this as obvious, but do I need to do anything special
to sync it with binutils, or will that happen next time somebody needs a
proper fix?
-- >8 --
The custom option for enabling/disabling libstdc++ is not spelled the
same as the directory name:
AC_ARG_ENABLE(libstdcxx,
AS_HELP_STRING([--disable-libstdcxx],
[do not build libstdc++-v3 directory])
The comment referring to it later use the wrong name.
ChangeLog:
* configure.ac: Fix incorrect option in comment.
* configure: Regenerate.
---
configure | 2 +-
configure.ac | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/configure b/configure
index 9c2d7df1bb2..f7e0fa46c9c 100755
--- a/configure
+++ b/configure
@@ -3390,7 +3390,7 @@ case "${target}" in
esac
# Disable libstdc++-v3 for some systems.
-# Allow user to override this if they pass --enable-libstdc++-v3
+# Allow user to override this if they pass --enable-libstdcxx
if test "${ENABLE_LIBSTDCXX}" = "default" ; then
case "${target}" in
*-*-vxworks*)
diff --git a/configure.ac b/configure.ac
index 68cc5cc31fe..434b1a267a4 100644
--- a/configure.ac
+++ b/configure.ac
@@ -649,7 +649,7 @@ case "${target}" in
esac
# Disable libstdc++-v3 for some systems.
-# Allow user to override this if they pass --enable-libstdc++-v3
+# Allow user to override this if they pass --enable-libstdcxx
if test "${ENABLE_LIBSTDCXX}" = "default" ; then
case "${target}" in
*-*-vxworks*)
--
2.34.1
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: [PATCH] top-level: Fix comment about --enable-libstdcxx in configure
2022-03-11 18:38 [PATCH] top-level: Fix comment about --enable-libstdcxx in configure Jonathan Wakely
@ 2022-03-14 13:13 ` Jonathan Wakely
0 siblings, 0 replies; 2+ messages in thread
From: Jonathan Wakely @ 2022-03-14 13:13 UTC (permalink / raw)
To: gcc-patches
Pushed to trunk now.
On 11/03/22 18:38 +0000, Jonathan Wakely wrote:
>I'm going to push this as obvious, but do I need to do anything special
>to sync it with binutils, or will that happen next time somebody needs a
>proper fix?
>
>-- >8 --
>
>The custom option for enabling/disabling libstdc++ is not spelled the
>same as the directory name:
>
>AC_ARG_ENABLE(libstdcxx,
>AS_HELP_STRING([--disable-libstdcxx],
> [do not build libstdc++-v3 directory])
>
>The comment referring to it later use the wrong name.
>
>ChangeLog:
>
> * configure.ac: Fix incorrect option in comment.
> * configure: Regenerate.
>---
> configure | 2 +-
> configure.ac | 2 +-
> 2 files changed, 2 insertions(+), 2 deletions(-)
>
>diff --git a/configure b/configure
>index 9c2d7df1bb2..f7e0fa46c9c 100755
>--- a/configure
>+++ b/configure
>@@ -3390,7 +3390,7 @@ case "${target}" in
> esac
>
> # Disable libstdc++-v3 for some systems.
>-# Allow user to override this if they pass --enable-libstdc++-v3
>+# Allow user to override this if they pass --enable-libstdcxx
> if test "${ENABLE_LIBSTDCXX}" = "default" ; then
> case "${target}" in
> *-*-vxworks*)
>diff --git a/configure.ac b/configure.ac
>index 68cc5cc31fe..434b1a267a4 100644
>--- a/configure.ac
>+++ b/configure.ac
>@@ -649,7 +649,7 @@ case "${target}" in
> esac
>
> # Disable libstdc++-v3 for some systems.
>-# Allow user to override this if they pass --enable-libstdc++-v3
>+# Allow user to override this if they pass --enable-libstdcxx
> if test "${ENABLE_LIBSTDCXX}" = "default" ; then
> case "${target}" in
> *-*-vxworks*)
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2022-03-14 13:14 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2022-03-11 18:38 [PATCH] top-level: Fix comment about --enable-libstdcxx in configure Jonathan Wakely
2022-03-14 13:13 ` Jonathan Wakely
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).