From: Eli Zaretskii <eliz@gnu.org>
To: Ben Longbons <brlongbons@gmail.com>
Cc: gdb@sourceware.org
Subject: Re: [C++] System Requirements
Date: Mon, 16 Dec 2013 19:05:00 -0000 [thread overview]
Message-ID: <83y53kd3bw.fsf@gnu.org> (raw)
In-Reply-To: <CA+XNFZO6-rhG_mnRtg_B_y6R3FaFRWzb_ED4G=Yf1gdNs4d+gw@mail.gmail.com>
> Date: Fri, 13 Dec 2013 16:34:17 -0800
> From: Ben Longbons <brlongbons@gmail.com>
>
> I propose that the minimum "development requirements" is either gcc
> 4.6 or 4.7.
IMO, it makes very little sense to require the bleeding edge, or
thereabouts. I still use GCC 3.4 on one of my main development
machines; the other one was upgraded to 4.7.2 a few months ago, and
I'm still lamenting the two-fold increase in build times that this
caused.
As another data point, the GNU shell server fencepost.gnu.org, a
Trisquel system, offers GCC 4.4.3.
> gcc 4.8.1 is the first fully-compliant C++11 release.
So what? Why do we need this full compliance is the important part.
prev parent reply other threads:[~2013-12-16 19:05 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-14 0:34 Ben Longbons
2013-12-14 0:40 ` Ben Longbons
2013-12-15 12:28 ` Michael Veksler
2013-12-17 2:29 ` Andrew Pinski
2013-12-17 4:02 ` Ben Longbons
2013-12-18 12:47 ` Michael Veksler
2013-12-18 19:16 ` Ben Longbons
2013-12-15 15:31 ` Jan Kratochvil
2013-12-15 17:04 ` Ben Longbons
2013-12-15 19:53 ` Mark Kettenis
2013-12-16 13:03 ` Ivo Raisr
2013-12-16 13:52 ` Phi Debian
2013-12-17 5:35 ` Sergio Durigan Junior
2013-12-16 19:10 ` Eli Zaretskii
2013-12-16 20:09 ` Ben Longbons
2013-12-16 19:05 ` Eli Zaretskii [this message]
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=83y53kd3bw.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=brlongbons@gmail.com \
--cc=gdb@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