Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Pedro Alves <palves@redhat.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH+7.12 1/1] gdb/NEWS: Mention C++ is now the default
Date: Fri, 05 Aug 2016 16:16:00 -0000	[thread overview]
Message-ID: <e4a1cca7-c655-8a4d-7fd0-bbd4d2800de2@redhat.com> (raw)
In-Reply-To: <837fbxn7kd.fsf@gnu.org>

On 08/03/2016 05:25 PM, Eli Zaretskii wrote:

> The text is okay, but I think "./configure --help" should mention
> "--disable-build-with-cxx", as it does with all the other options that
> are enabled by default.
> 

That's now done, so here's what I'm pushing to master and 7.12,
updated to talk about --disable-build-with-cxx.

From 71cf9b4a255d120100391d1f661fbaf556fccea7 Mon Sep 17 00:00:00 2001
From: Pedro Alves <palves@redhat.com>
Date: Fri, 5 Aug 2016 17:09:31 +0100
Subject: [PATCH] gdb/NEWS: Mention that C++ is now the default

gdb/ChangeLog:
2016-08-05  Pedro Alves  <palves@redhat.com>

	* NEWS: Mention that GDB and GDBserver build with a C++ compiler by
	default.
---
 gdb/NEWS | 7 +++++++
 1 file changed, 7 insertions(+)

diff --git a/gdb/NEWS b/gdb/NEWS
index 4d72027..b08d8a0 100644
--- a/gdb/NEWS
+++ b/gdb/NEWS
@@ -5,6 +5,13 @@
 
 *** Changes in GDB 7.12
 
+* GDB and GDBserver now build with a C++ compiler by default.
+
+  The --enable-build-with-cxx configure option is now enabled by
+  default.  One must now explicitly configure with
+  --disable-build-with-cxx in order to build with a C compiler.  This
+  option will be removed in a future release.
+
 * GDBserver now supports recording btrace without maintaining an active
   GDB connection.
 
-- 
2.5.5



  reply	other threads:[~2016-08-05 16:16 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-03 14:49 [PATCH+7.12 0/1] " Pedro Alves
2016-08-03 14:49 ` [PATCH+7.12 1/1] " Pedro Alves
2016-08-03 16:25   ` Eli Zaretskii
2016-08-05 16:16     ` Pedro Alves [this message]
2016-08-03 16:30 ` [PATCH+7.12 0/1] " Yao Qi
2016-08-03 17:52   ` 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=e4a1cca7-c655-8a4d-7fd0-bbd4d2800de2@redhat.com \
    --to=palves@redhat.com \
    --cc=eliz@gnu.org \
    --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