From: Pedro Alves <palves@redhat.com>
To: "Richard Earnshaw (lists)" <Richard.Earnshaw@arm.com>,
gdb-patches@sourceware.org
Subject: Re: [PATCH 0/2] gdb: Require a C++11 compiler
Date: Wed, 02 Nov 2016 15:58:00 -0000 [thread overview]
Message-ID: <9dbf91d5-5d06-5f4c-2e6e-c6d232ce9252@redhat.com> (raw)
In-Reply-To: <cc271c0f-67c7-51d8-fdde-5c8fd36ea29d@arm.com>
On 11/02/2016 02:51 PM, Richard Earnshaw (lists) wrote:
> On 01/11/16 16:53, Pedro Alves wrote:
>> Hi Richard,
>>
>> On 11/01/2016 11:00 AM, Richard Earnshaw (lists) wrote:
>>
>>> Sorry, I have to say I think this is too soon (having just found out the
>>> hard way) :-( ).
>>
>> Sorry for causing you trouble. :-(
>>
>>> 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
>>
>> Fortunately, there are gcc 4.8 packages for RHEL5 in DTS2:
>>
>
> Which are not installed on any of our machines and, frankly, I wouldn't
> want to take a wager on persuading our IT admins to do that. :-( It's
> certainly unlikely to happen in short order.
I don't want to sound presumptuous, but I can't imagine why they'd refuse
to install a RH-validated package on a RH system, package which was made
exactly for purposes like the one at hand. C++11 is only becoming more
common and a dependency of many upstream projects. clang/llvm just
recently started requiring gcc 4.8 too (for full C++11 support),
for example.
Thanks,
Pedro Alves
next prev parent reply other threads:[~2016-11-02 15:58 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 ` [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 [this message]
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=9dbf91d5-5d06-5f4c-2e6e-c6d232ce9252@redhat.com \
--to=palves@redhat.com \
--cc=Richard.Earnshaw@arm.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