On Mon, 16 Dec 2024 at 14:41, Dennis Clarke <dclarke@xxxxxxxxxxxxx> wrote: > > On 12/16/24 09:03, Jonathan Wakely wrote: > > On Mon, 16 Dec 2024 at 13:37, Dennis Clarke via Gcc-help > > <gcc-help@xxxxxxxxxxx> wrote: > >> > ... > >> Looking at Host/Target specific installation notes for GCC : > >> > >> https://gcc.gnu.org/install/specific.html#older > >> > >> There I see : > >> > >> Starting with GCC 3.1, each release has a list of “obsoleted” > >> systems. Support for these systems is still present in that > >> release, but configure will fail unless the --enable-obsolete > >> option is given. Unless a maintainer steps forward, support for > >> these systems will be removed from the next release of GCC. > >> > >> Really? > >> > >> Where is that list? > > > > gcc/config.gcc > > > > # Obsolete configurations. > > case ${target}${target_min} in > > *-*-solaris2.11.[0-3]* \ > > | ia64*-*-* \ > > | nios2*-*-* \ > > ) > > if test "x$enable_obsolete" != xyes; then > > echo "*** Configuration ${target}${target_min} is obsolete." >&2 > > echo "*** Specify --enable-obsolete to build it anyway." >&2 > > echo "*** Support will be REMOVED in the next major release of GCC," >&2 > > echo "*** unless a maintainer comes forward." >&2 > > exit 1 > > fi;; > > esac > > > > Excellent! Thank you for the reply. This helps somewhat. I do trust > the above and question the "changes" below. Question them how? > I just did try to bootstrap > GCC 6.5.0 and did use the --enable-obsolete and then watched it fail in > stage1 regardless. An obsolete target won't even get to stage1 without --enable-obsolete, but just adding --enable-obsolete doesn't mean the bootstrap won't fail for other reasons when compiled with a modern compiler or OS which wasn't contemporary when the old release was tested. > > The changes are announced in the release notes for each releases, e.g. > > https://gcc.gnu.org/gcc-14/changes.html (ia64 and nios2 declared obsolete) > > https://gcc.gnu.org/gcc-13/changes.html (solaris 11.3 declared obsolete) > > https://gcc.gnu.org/gcc-12/changes.html (cr16, 32-bit hppa-hpux, and > > m32c declared obsolete). > > etc. > > > > OKay, this is helpful. However looking at : > > https://gcc.gnu.org/gcc-6/changes.html > > Where I see mention of "Solaris 12 is now fully supported." Ha. Ha. I'm not sure what point you're making here, sorry. > Well, yes, this is archaeology but 2018 was not really very long ago > for the release of 6.5.0. The list of targets declared obsolete in 6.5.0 is the same as the list for 6.1.0 (because we don't change it mid-release) and that's from Q2 2016. Looking at when 6.5.0 was released isn't really relevant here when it's "6.1.0 but with bug fixes", so what matters is when 6.1.0 was released. IMHO 2016 *is* quite long ago for an open source project. If you want support over that kind of time scale, you generally need to pay for it or do a lot of work (which I realise is what you're doing, so no criticism there). > I will dig around in gcc/config.gcc and see > what it says for release 5.x and even 7.x and others around the years > 2014 or thereabouts. > > Thank you very much for the good info. > > -- > -- > Dennis Clarke > RISC-V/SPARC/PPC/ARM/CISC > UNIX and Linux spoken >
