From: Pedro Alves <palves@redhat.com>
To: gdb-patches@sourceware.org
Subject: [PATCH 1/1] Build GDB as a C++ program by default
Date: Mon, 18 Apr 2016 17:27:00 -0000 [thread overview]
Message-ID: <1461000466-31668-2-git-send-email-palves@redhat.com> (raw)
In-Reply-To: <1461000466-31668-1-git-send-email-palves@redhat.com>
This makes --enable-build-with-cxx be "yes" by default.
One must now configure with --enable-build-with-cxx=no in order to
build with a C compiler.
gdb/ChangeLog:
2016-04-18 Pedro Alves <palves@redhat.com>
* build-with-cxx.m4 (GDB_AC_BUILD_WITH_CXX): Default to yes unless
building on some hosts.
* configure: Renegerate.
gdb/gdbserver/ChangeLog:
2016-04-18 Pedro Alves <palves@redhat.com>
* configure: Renegerate.
---
gdb/build-with-cxx.m4 | 2 +-
gdb/configure | 2 +-
gdb/gdbserver/configure | 2 +-
3 files changed, 3 insertions(+), 3 deletions(-)
diff --git a/gdb/build-with-cxx.m4 b/gdb/build-with-cxx.m4
index 6eb9143..6077278 100644
--- a/gdb/build-with-cxx.m4
+++ b/gdb/build-with-cxx.m4
@@ -29,7 +29,7 @@ AC_DEFUN([GDB_AC_BUILD_WITH_CXX],
*)
AC_MSG_ERROR([bad value $enableval for --enable-build-with-cxx]) ;;
esac],
- [enable_build_with_cxx=no])
+ [enable_build_with_cxx=yes])
if test "$enable_build_with_cxx" = "yes"; then
COMPILER='$(CXX)'
diff --git a/gdb/configure b/gdb/configure
index 8c2ec0f..3cf95e7 100755
--- a/gdb/configure
+++ b/gdb/configure
@@ -4965,7 +4965,7 @@ if test "${enable_build_with_cxx+set}" = set; then :
as_fn_error "bad value $enableval for --enable-build-with-cxx" "$LINENO" 5 ;;
esac
else
- enable_build_with_cxx=no
+ enable_build_with_cxx=yes
fi
diff --git a/gdb/gdbserver/configure b/gdb/gdbserver/configure
index 2082335..746218e 100755
--- a/gdb/gdbserver/configure
+++ b/gdb/gdbserver/configure
@@ -4784,7 +4784,7 @@ if test "${enable_build_with_cxx+set}" = set; then :
as_fn_error "bad value $enableval for --enable-build-with-cxx" "$LINENO" 5 ;;
esac
else
- enable_build_with_cxx=no
+ enable_build_with_cxx=yes
fi
--
2.5.5
next prev parent reply other threads:[~2016-04-18 17:27 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-18 17:27 [PATCH 0/1] " Pedro Alves
2016-04-18 17:27 ` Pedro Alves [this message]
2016-04-19 7:34 ` [PATCH 1/1] " Yao Qi
2016-04-19 13:34 ` [PATCH 0/1] " Simon Marchi
2016-04-19 14:18 ` Pedro Alves
2016-04-19 14:48 ` Eli Zaretskii
2016-04-19 15:03 ` Pedro Alves
2016-04-19 15:23 ` Eli Zaretskii
2016-04-19 15:40 ` Pedro Alves
2016-04-19 15:59 ` Eli Zaretskii
2016-04-19 16:20 ` Pedro Alves
2016-04-19 16:31 ` Eli Zaretskii
2016-04-19 15:41 ` Simon Marchi
2016-04-19 16:32 ` Eli Zaretskii
[not found] ` <AC542571535E904D8E8ADAE745D60B19445B1C11@IRSMSX104.ger.corp.intel.com>
[not found] ` <5716425B.3050707@intel.com>
[not found] ` <57164325.8020408@redhat.com>
2016-04-19 15:20 ` Walfred Tedeschi
2016-04-20 19:56 ` Pedro Alves
2016-04-20 22:16 ` Pedro Alves
2016-04-21 15:18 ` John Baldwin
2016-04-21 16:41 ` Pedro Alves
2016-04-19 15:47 ` Simon Marchi
2016-04-19 15:50 ` Pedro Alves
2016-04-20 22:27 ` Pedro Alves
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1461000466-31668-2-git-send-email-palves@redhat.com \
--to=palves@redhat.com \
--cc=gdb-patches@sourceware.org \
/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