From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: palves@redhat.com, brobecker@adacore.com,
markus.t.metzger@intel.com, gdb-patches@sourceware.org
Subject: Re: [PATCH 1/3] Introduce gdb::unique_ptr
Date: Thu, 13 Oct 2016 09:07:00 -0000 [thread overview]
Message-ID: <20161013090647.GA32613@host1.jankratochvil.net> (raw)
In-Reply-To: <831szlbwqt.fsf@gnu.org>
On Wed, 12 Oct 2016 14:03:06 +0200, Eli Zaretskii wrote:
> That may all be true, but changing the system compiler is still a
> serious decision, unrelated to distribution and/or update speeds, and
> not always even in the hands of the user who wants to build his or her
> GDB which was just released.
>
> The nuisance of having to upgrade half of your system just because you
> want to have one package of the latest release is real for users who
> need to do during most of their day something other than debug build
> failures and install updated dependencies. I was hoping we didn't
> want to increase those annoyances.
GCC 4.8.1 has been released in May 2013 so any Linux distributions with at
least annual releases already have it. The only exception are LTS
https://en.wikipedia.org/wiki/Long-term_support
distributions:
{RHEL,CentOS}-5.0: gcc-4.1.1-52.el5
But there is Developer Toolset 2.1 compatible with RHEL-5 which provides:
devtoolset-2-gcc-4.8.2-15.el5
DevToolset 2.1 is still available in RHN channel for RHEL-5 customers.
Unfortunately it is currently unavailable for CentOS-5 users, hopefully it
will become available soon on this URL but I sure cannot guarantee anything:
https://www.softwarecollections.org/en/scls/?search=toolset
{RHEL,CentOS}-6.0: gcc-4.4.4-13.el6
There is DevToolset available in RHN channel and for CentOS it is freely at:
https://www.softwarecollections.org/en/scls/rhscl/devtoolset-4/
http://mirror.centos.org/centos/6/sclo/x86_64/rh/devtoolset-4/devtoolset-4-gcc-5.2.1-2.2.el6.x86_64.rpm
{RHEL,CentOS}-7.0: gcc-4.8.2-16.el7
Debian stable:
https://packages.debian.org/stable/gcc = 4:4.9.2-2
Ubuntu LTSes:
https://en.wikipedia.org/wiki/Ubuntu_(operating_system)#Releases
http://packages.ubuntu.com/search?keywords=gcc
12.04LTS = 4:4.6.3-1ubuntu5
I am not aware of anything like DevToolset for Ubuntu.
14.04LTS = 4:4.8.2-1ubuntu6
DevToolset is an add-on packaging in /opt/rh/ running independently from
system GCC producing binaries compatible even with RHELs without DevToolset.
Therefore there is no need of "changing the system compiler" or "upgrade half
of your system" to compile C++11 there.
As Pedro said the C++11 requirement is becoming common among other packages so
it is probable one needs to install DevToolset anyway.
Then there are systems without package management - like MS-Windows - where
all the recent compilers are available installable into separate
subdirectories.
Jan
next prev parent reply other threads:[~2016-10-13 9:07 UTC|newest]
Thread overview: 72+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-10 16:46 [PATCH 0/3] More cleanup elimination / gdb::unique_ptr Pedro Alves
2016-10-10 16:46 ` [PATCH 3/3] 'struct parse_expression *' -> gdb::unique_ptr<expression> Pedro Alves
2016-10-10 16:46 ` [PATCH 1/3] Introduce gdb::unique_ptr Pedro Alves
2016-10-10 17:49 ` Simon Marchi
2016-10-10 18:03 ` Pedro Alves
2016-10-11 6:48 ` Metzger, Markus T
2016-10-11 10:23 ` Pedro Alves
2016-10-11 10:53 ` Andreas Schwab
2016-10-11 11:17 ` Metzger, Markus T
2016-10-11 11:43 ` Pedro Alves
2016-10-11 13:58 ` Yao Qi
2016-10-11 14:05 ` Trevor Saunders
2016-10-11 12:16 ` Joel Brobecker
2016-10-11 13:46 ` Pedro Alves
2016-10-11 14:47 ` Joel Brobecker
2016-10-11 15:17 ` Eli Zaretskii
2016-10-11 16:24 ` Pedro Alves
2016-10-11 16:58 ` Eli Zaretskii
2016-10-11 17:41 ` Pedro Alves
2016-10-11 18:37 ` Eli Zaretskii
2016-10-11 19:19 ` Pedro Alves
2016-10-11 20:47 ` Eli Zaretskii
2016-10-11 21:32 ` Pedro Alves
2016-10-12 6:34 ` Eli Zaretskii
2016-10-12 8:11 ` Metzger, Markus T
2016-10-12 9:31 ` Eli Zaretskii
2016-10-12 10:12 ` Pedro Alves
2016-10-12 11:05 ` Eli Zaretskii
2016-10-12 11:25 ` Pedro Alves
2016-10-12 11:45 ` Eli Zaretskii
2016-10-13 12:12 ` Pedro Alves
2016-10-12 10:28 ` Pedro Alves
2016-10-12 11:07 ` Eli Zaretskii
2016-10-12 11:19 ` Pedro Alves
2016-10-12 11:41 ` Eli Zaretskii
2016-10-12 11:55 ` Pedro Alves
2016-10-13 0:38 ` [PATCH] Enable C++11 starting with gcc 4.8 (was: Re: [PATCH 1/3] Introduce gdb::unique_ptr) Pedro Alves
2016-10-13 0:45 ` [PATCH 1/2] gdb: Import AX_CXX_COMPILE_STDCXX from the GNU Autoconf Archive Pedro Alves
2016-10-13 0:45 ` [PATCH 2/2] gdb: Enable C++11 if available Pedro Alves
2016-10-12 9:37 ` [PATCH 1/3] Introduce gdb::unique_ptr Pedro Alves
2016-10-12 10:51 ` Eli Zaretskii
2016-10-12 11:15 ` Pedro Alves
2016-10-12 11:40 ` Eli Zaretskii
2016-10-12 11:45 ` Jan Kratochvil
2016-10-12 11:56 ` Luis Machado
2016-10-12 12:03 ` Eli Zaretskii
2016-10-13 9:07 ` Jan Kratochvil [this message]
2016-10-13 10:07 ` Eli Zaretskii
2016-10-13 10:27 ` Pedro Alves
2016-10-13 13:22 ` Eli Zaretskii
2016-10-13 13:36 ` Pedro Alves
2016-10-13 13:59 ` Eli Zaretskii
2016-10-13 14:04 ` Pedro Alves
2016-10-13 15:06 ` Joel Brobecker
2016-10-13 10:46 ` Jan Kratochvil
2016-10-13 11:15 ` Pedro Alves
2016-10-13 13:28 ` Eli Zaretskii
2016-10-13 13:42 ` Pedro Alves
2016-10-13 14:07 ` Eli Zaretskii
2016-10-11 19:23 ` Simon Marchi
2016-10-11 20:54 ` Eli Zaretskii
2016-10-11 21:28 ` Simon Marchi
2016-10-12 6:23 ` Eli Zaretskii
2016-10-11 21:16 ` Jan Kratochvil
2016-10-11 17:15 ` Luis Machado
2016-10-11 18:21 ` Pedro Alves
2016-10-10 16:58 ` [PATCH 0/3] More cleanup elimination / gdb::unique_ptr Pedro Alves
2016-10-16 7:05 ` Tom Tromey
2016-10-17 13:57 ` Pedro Alves
2016-10-17 14:07 ` Tom Tromey
2016-10-17 14:59 ` Pedro Alves
2016-10-20 13: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=20161013090647.GA32613@host1.jankratochvil.net \
--to=jan.kratochvil@redhat.com \
--cc=brobecker@adacore.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=markus.t.metzger@intel.com \
--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