From: Rainer Orth <ro@CeBiTec.Uni-Bielefeld.DE>
To: gdb@sourceware.org
Subject: Obsoleting Solaris 10 support
Date: Tue, 16 Oct 2018 09:42:00 -0000 [thread overview]
Message-ID: <yddpnwakz2g.fsf@CeBiTec.Uni-Bielefeld.DE> (raw)
Yesterday I've announced the obsoletion of Solaris 10 support in GCC 9
https://gcc.gnu.org/ml/gcc/2018-10/msg00139.html
I believe the same reasons cited there hold for GDB as well. Besides,
we had some build failures recently that only occured on Solaris 10,
creating work to support a rapidly dwindling or even vanished user base.
Therefore, I wonder how best to handle this in GDB.
While GCC has roughly one release a year and GCC 9, the last relase to
support Solaris 10 with --enable-obsolete, will appear sometime next
spring, GDB has a release cycle of about 6 months. Should we obsolete
Solaris 10 for GDB 8.3 now, getting a bit ahead of GCC, or rather wait
for GDB 8.4 instead? My gut feeling is that it would be better to wait
for 8.4: more often than not GCC adds support for new DWARF versions or
other extensions, and it would be good to have a GDB that supports
what's in the GCC 9 release.
Thanks.
Rainer
--
-----------------------------------------------------------------------------
Rainer Orth, Center for Biotechnology, Bielefeld University
next reply other threads:[~2018-10-16 9:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-16 9:42 Rainer Orth [this message]
2018-10-16 14:20 ` Joel Brobecker
2018-10-16 14:31 ` Rainer Orth
2018-10-16 16:39 ` Joel Brobecker
2018-10-16 18:21 ` Dennis Clarke
2018-10-17 12:39 ` Rainer Orth
2018-10-17 12:34 ` Rainer Orth
2018-10-16 18:41 ` Dennis Clarke
2018-10-17 12:42 ` Rainer Orth
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=yddpnwakz2g.fsf@CeBiTec.Uni-Bielefeld.DE \
--to=ro@cebitec.uni-bielefeld.de \
--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