From: Pedro Alves <palves@redhat.com>
To: Simon Marchi <simon.marchi@ericsson.com>,
Eli Zaretskii <eliz@gnu.org>,
Joel Brobecker <brobecker@adacore.com>
Cc: gdb-patches@sourceware.org
Subject: Re: GDB 7.11.90 available for testing
Date: Wed, 03 Aug 2016 16:10:00 -0000 [thread overview]
Message-ID: <a7187a5c-d33f-ae6b-c23d-4ceafe1649de@redhat.com> (raw)
In-Reply-To: <25824359-cb4e-6fb3-531b-e2e994da4712@ericsson.com>
On 08/03/2016 04:44 PM, Simon Marchi wrote:
> On 16-08-03 11:10 AM, Pedro Alves wrote:
>> On 08/02/2016 04:29 PM, Eli Zaretskii wrote:
>>
>>> . The default compiler is now g++, but "configure --help" still says
>>> "--enable-build-with-cxx", which hints that it is by default
>>> disabled. I suggest to update the --help text.
>>
>> I don't see that in my builds. Looking at print_gdb_configuration,
>> I can't see where that would be coming from either. Do you have a
>> local patch, perhaps?
>
> It's in gdb's configure:
Ah, for some reason I misread and understood that Eli was talking
about gdb --configuration. Sorry about that.
>
> $ ./gdb/configure --help
> ...
> --enable-build-with-cxx build with C++ compiler instead of C compiler
> ...
>
>
> It should probably say:
>
> --disable-build-with-cxx build with C compiler instead of C++ compiler
>
Fine with me. Guess I should amend my NEWS patch to talk about that
instead.
Thanks,
Pedro Alves
next prev parent reply other threads:[~2016-08-03 16:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-01 16:10 Joel Brobecker
2016-08-02 15:29 ` Eli Zaretskii
2016-08-03 15:10 ` Pedro Alves
2016-08-03 15:50 ` Simon Marchi
2016-08-03 16:10 ` Pedro Alves [this message]
2016-08-03 16:28 ` Eli Zaretskii
2016-08-05 16:00 ` Pedro Alves
2016-08-05 16:53 ` Eli Zaretskii
2016-08-03 16:27 ` Eli Zaretskii
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=a7187a5c-d33f-ae6b-c23d-4ceafe1649de@redhat.com \
--to=palves@redhat.com \
--cc=brobecker@adacore.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=simon.marchi@ericsson.com \
/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