This is the mail archive of the
mailing list for the GDB project.
Re: Obsoleting Solaris 10 support
- From: Joel Brobecker <brobecker at adacore dot com>
- To: Rainer Orth <ro at CeBiTec dot Uni-Bielefeld dot DE>
- Cc: gdb at sourceware dot org
- Date: Tue, 16 Oct 2018 07:20:24 -0700
- Subject: Re: Obsoleting Solaris 10 support
- References: <yddpnwakz2g.fsf@CeBiTec.Uni-Bielefeld.DE>
> Yesterday I've announced the obsoletion of Solaris 10 support in GCC 9
> 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.
I don't know of any particular issue that might create a strong
reason for dropping Solaris 10 support in the short term; and
I agree that it would be nice for the users on Solaris 10 to
continue providing newer versions of GDB on that platform until
GCC also stops. However, this is only really possible if contributors
like yourself stand behind it. So, in my mind, I would continue with
the default stand where we keep support by default as long as it doesn't
unduly slows the rest of GDB development.