Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "Richard Earnshaw (lists)" <Richard.Earnshaw@arm.com>
To: Pedro Alves <palves@redhat.com>, gdb-patches@sourceware.org
Subject: Re: [PATCH 0/2] gdb: Require a C++11 compiler
Date: Tue, 01 Nov 2016 11:00:00 -0000	[thread overview]
Message-ID: <2f6931ce-8286-9b97-3a67-8228becfa424@arm.com> (raw)
In-Reply-To: <1477596094-3244-1-git-send-email-palves@redhat.com>

On 27/10/16 20:21, Pedro Alves wrote:
> As previously discussed, this patch set makes GDB require a C++11
> compiler.
> 
> You'll find the previous discussions referenced here:
>   https://sourceware.org/ml/gdb-patches/2016-10/msg00607.html
> 
> This is basically the same as I had sent here:
>   https://sourceware.org/ml/gdb-patches/2016-10/msg00336.html
> 
> The only difference is a single-line change that makes C++11 a
> mandatory instead of enabling it iff supported.
> 
> Pedro Alves (2):
>   gdb: Import AX_CXX_COMPILE_STDCXX from the GNU Autoconf Archive
>   gdb: Require C++11
> 
>  gdb/Makefile.in              |   6 +-
>  gdb/acinclude.m4             |   2 +
>  gdb/ax_cxx_compile_stdcxx.m4 | 567 +++++++++++++++++++++++++
>  gdb/config.in                |   3 +
>  gdb/configure                | 981 ++++++++++++++++++++++++++++++++++++++++++-
>  gdb/configure.ac             |   4 +
>  gdb/gdbserver/Makefile.in    |   5 +-
>  gdb/gdbserver/acinclude.m4   |   2 +
>  gdb/gdbserver/config.in      |   3 +
>  gdb/gdbserver/configure      | 981 ++++++++++++++++++++++++++++++++++++++++++-
>  gdb/gdbserver/configure.ac   |   4 +
>  11 files changed, 2552 insertions(+), 6 deletions(-)
>  create mode 100644 gdb/ax_cxx_compile_stdcxx.m4
> 

Sorry, I have to say I think this is too soon (having just found out the
hard way) :-( ).

Half of the machines I use are still running RHE5 and this change means
I can no-longer use the system compiler for building GDB.  A change that
requires use of a non-standard compiler significantly complicates the
process of building (and worse, productizing) GDB builds as now you have
to mess with either forcing static linking or worse, forcing uses to
mess with non-standard LD_LIBRARY paths at run time.

R.


  parent reply	other threads:[~2016-11-01 11:00 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-27 19:21 Pedro Alves
2016-10-27 19:21 ` [PATCH 2/2] gdb: Require C++11 Pedro Alves
     [not found]   ` <20161028104718.540c10ed@ThinkPad>
2016-10-28  9:03     ` Pedro Alves
2016-10-28 10:44       ` Philipp Rudo
2016-11-03 15:39   ` Yao Qi
2016-11-03 15:58     ` Pedro Alves
2016-11-03 16:11       ` Yao Qi
2016-10-27 19:21 ` [PATCH 1/2] gdb: Import AX_CXX_COMPILE_STDCXX from the GNU Autoconf Archive Pedro Alves
2016-10-28 12:07 ` [PATCH 0/2] gdb: Require a C++11 compiler Yao Qi
2016-10-28 15:08   ` Pedro Alves
2016-10-28 17:17     ` [PATCH] gdb/NEWS: Mention C++11 requirement Pedro Alves
2016-10-29  6:13       ` Eli Zaretskii
2016-10-29 15:18         ` Pedro Alves
2016-10-29 15:29           ` Eli Zaretskii
2016-10-29 15:35             ` Pedro Alves
2016-11-01 11:00 ` Richard Earnshaw (lists) [this message]
2016-11-01 16:53   ` [PATCH 0/2] gdb: Require a C++11 compiler Pedro Alves
2016-11-02 14:51     ` Richard Earnshaw (lists)
2016-11-02 15:58       ` Pedro Alves
2016-11-04 13:31     ` Maciej W. Rozycki
2016-11-04 14:46       ` 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=2f6931ce-8286-9b97-3a67-8228becfa424@arm.com \
    --to=richard.earnshaw@arm.com \
    --cc=gdb-patches@sourceware.org \
    --cc=palves@redhat.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