Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "Maciej W. Rozycki" <macro@imgtec.com>
To: Pedro Alves <palves@redhat.com>
Cc: "Richard Earnshaw (lists)" <Richard.Earnshaw@arm.com>,
	<gdb-patches@sourceware.org>
Subject: Re: [PATCH 0/2] gdb: Require a C++11 compiler
Date: Fri, 04 Nov 2016 13:31:00 -0000	[thread overview]
Message-ID: <alpine.DEB.2.00.1611040430310.24498@tp.orcam.me.uk> (raw)
In-Reply-To: <7437e071-2020-2e0d-0f8b-8269767d157b@redhat.com>

On Tue, 1 Nov 2016, Pedro Alves wrote:

> > to mess with either forcing static linking or worse, forcing uses to
> > mess with non-standard LD_LIBRARY paths at run time.
> 
> Note that just like gcc, gdb builds with -static-libstdc++ -static-libgcc.

 Are you sure?  All my recent cross-built `gdbserver' executables failed 
to run without a pain of getting `libstdc++.so' in the right place on the 
target.  Or do you mean GDB proper only?  I didn't even realise there was
intention to use static `libstdc++' and/or `libgcc' libraries.

 Also I've not been particularly happy with the project moving over to C++ 
let alone C++11, however I have just decided I couldn't afford the effort 
to go through all the discussion, which always takes time pinched from 
other commitments.  Being a CPU target maintainer only and with my rusty 
1995-vintage C++ programming skills -- making it difficult to me to assess 
what the advantages of modern C++ dialects might be -- I didn't want to 
stand in the way of core developers if they think a move to C++ will make 
their job easier, improving code quality and reducing maintenance burden.

 FWIW,

  Maciej


  parent reply	other threads:[~2016-11-04 13:31 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 1/2] gdb: Import AX_CXX_COMPILE_STDCXX from the GNU Autoconf Archive 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-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 ` [PATCH 0/2] gdb: Require a C++11 compiler Richard Earnshaw (lists)
2016-11-01 16:53   ` 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 [this message]
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=alpine.DEB.2.00.1611040430310.24498@tp.orcam.me.uk \
    --to=macro@imgtec.com \
    --cc=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