Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Pedro Alves <palves@redhat.com>
To: Rainer Orth <ro@CeBiTec.Uni-Bielefeld.DE>,
	Andreas Schwab <schwab@suse.de>
Cc: gdb-patches@sourceware.org
Subject: Re: Obsolete/remove Solaris < 10 [was: Re: Fix gdb 8.1 Solaris compilation]
Date: Thu, 21 Sep 2017 14:39:00 -0000	[thread overview]
Message-ID: <47bb2956-5654-0ce3-26dd-9f6b76ff6e08@redhat.com> (raw)
In-Reply-To: <yddk20sp1i5.fsf_-_@CeBiTec.Uni-Bielefeld.DE>

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


  reply	other threads:[~2017-09-21 14:39 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-21 13:02 Fix gdb 8.1 Solaris compilation Rainer Orth
2017-09-21 13:17 ` Andreas Schwab
2017-09-21 14:14   ` Rainer Orth
2017-09-21 14:31     ` Obsolete/remove Solaris < 10 [was: Re: Fix gdb 8.1 Solaris compilation] Rainer Orth
2017-09-21 14:39       ` Pedro Alves [this message]
2017-09-22 14:45         ` Rainer Orth
2017-09-22 15:40           ` Pedro Alves
2017-09-26 11:20             ` Rainer Orth
2017-09-26 11:26               ` Pedro Alves
2017-09-26 13:25                 ` Rainer Orth
2017-09-26 13:45                   ` Pedro Alves
2017-09-26 13:55                     ` Rainer Orth
2017-09-26 14:18               ` Pedro Alves
2017-09-26 14:21                 ` Pedro Alves
2017-10-03 13:01                   ` Rainer Orth
2017-09-29 11:53               ` Eli Zaretskii
2017-09-21 14:21 ` Fix gdb 8.1 Solaris compilation Pedro Alves
2017-09-21 14:23   ` 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=47bb2956-5654-0ce3-26dd-9f6b76ff6e08@redhat.com \
    --to=palves@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --cc=ro@CeBiTec.Uni-Bielefeld.DE \
    --cc=schwab@suse.de \
    /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