Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: Ben Longbons <brlongbons@gmail.com>
Cc: gdb@sourceware.org
Subject: Re: [C++] System Requirements
Date: Sun, 15 Dec 2013 15:31:00 -0000	[thread overview]
Message-ID: <20131215153129.GA27931@host2.jankratochvil.net> (raw)
In-Reply-To: <CA+XNFZO6-rhG_mnRtg_B_y6R3FaFRWzb_ED4G=Yf1gdNs4d+gw@mail.gmail.com>

On Sat, 14 Dec 2013 01:34:17 +0100, Ben Longbons wrote:
> We have already seen the kind of trouble it takes to support old
> systems with Python 2.4

Python 2.4 has been recently decided to be discontinued:
	https://sourceware.org/ml/gdb-patches/2013-12/msg00402.html


> I propose that the minimum "development requirements" is either gcc
> 4.6 or 4.7.

I find it too strict for GDB even myself, for example RHEL-5 with gcc-4.1
still should be able to build upstream GDB even in some restricted form (such
as without the Python mentioned above).

There are enough benefits even just with C++03.  C++11 etc. extensions still
can be done incrementally in the future.

There should be first reviewed+accepted patchset, already posted at
	[PATCH 00/18] -Wc++-compat patches v2.0
	https://sourceware.org/ml/gdb-patches/2013-10/msg00641.html
plus then sure many other patches you also suggest in the other mails.


Regards,
Jan


  parent reply	other threads:[~2013-12-15 15:31 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 [this message]
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

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=20131215153129.GA27931@host2.jankratochvil.net \
    --to=jan.kratochvil@redhat.com \
    --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