Obsolete/remove Solaris < 10 [was: Re: Fix gdb 8.1 Solaris compilation]
Pedro Alves
palves@redhat.com
Thu Sep 21 14:39:00 GMT 2017
On 09/21/2017 03:30 PM, Rainer Orth wrote:
> This bad interaction between gnulib and fixed Solaris 9 headers may be
> fixable, but even trying to seems like a total waste of time.
>
> How is obsoletion/removal handled in gdb? In gcc, in one release a
> target is obsoleted and trying to build it yields an error which can be
> overridden with --enable-obsolete. Unless someone steps up to continue
> maintenance, the code is removed in the next release.
GDB is more aggressive:
https://sourceware.org/gdb/wiki/Internals%20Obsoleting-code
For Solaris, I believe it's been a while that the only maintenance
we've seen comes from you. Which kind of makes you the de-facto
maintainer. :-) Since gcc obsoleted Solaris 9 years ago, and nobody
all these years stepped forward, I think we should be able to just drop
it. I think you've proposed this in the past, even. I very
much doubt anyone would step forward this time.
> Does gdb go for immediate removal instead? I have no idea which release
> last built/worked on Solaris 9. I have a build of 7.11 lying around,
> but never tried anything later.
Thanks,
Pedro Alves
More information about the Gdb-patches
mailing list