Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Andrew Cagney <cagney@gnu.org>
To: Michael Elizabeth Chastain <mec.gnu@mindspring.com>
Cc: gdb@sources.redhat.com, brobecker@act-europe.fr, dave@hiauly1.hia.nrc.ca
Subject: Re: Proposal: obsolete target hppa*-hp-hpux10.*
Date: Thu, 08 Jan 2004 17:12:00 -0000	[thread overview]
Message-ID: <3FFD8F84.7040100@gnu.org> (raw)
In-Reply-To: <20040108025031.4FA984B35A@berman.michael-chastain.com>

> I propose to obsolete this target in gdb 6.1 and remove it in gdb 6.2:
> 
>   hppa*-hp-hpux10.*

Ah, you've figured out my strategy: shake the tree, see what falls out 
:-) "go for it".

> This does not include hppa*-hp-hpux11.*, which has active development.
> 
> Reasons for removing this configuration:
> 
>   . gdb 6.0 does not build on this configuration.
> 
>     http://sources.redhat.com/gdb/bugs/1411
>     Build of gdb-6.0 on hppa1.1-hp-hpux10.20 fails
> 
>       This is a different build failure than the build failures
>       with hppa2.0w-hp-hpux11.11.
> 
>   . there is no development activity for this target
> 
>   . there is no QA activity for this target
> 
>   . HP's test drive cluster does not include an hp-ux 10.* machine
> 
>   . HP has discontinued and obsoleted hp-ux 10.*
> 
>     http://h21007.www2.hp.com/dspp/tech/tech_TechDocumentDetailPage_IDX/1,1701,5143,00.html
>     frequently asked questions -- hp-ux
> 
>       2002-06-30   hp-ux 10.20 removed from corporate price list
>       2003-06-30   hp-ux 10.20 product support no longer available from HP
> 
> Reasons for keeping this configuration:
> 
>   . Someone (me) is actively working on native hppa2.0w-hp-hpux11.11.

Can I guess that you're, at least in part, working on 11.11 because it 
is a stable PA RISC based platform and offers a path for getting 
GNU/Linux PA out of limbo?

>     If gdb works on hpux 11.11, the incremental effort for development
>     and QA of hpux 10.20 is not as big.

This isn't sufficient to justify requiring you spending your volunteer 
time on that system.  If someone is willing to step forward and help, 
that would be really appreciated.

>   . There is at least one user (Dave A), which means that there are
>     probably more users.
> 
> Philosophically, I see the issue as priorities.  It takes work to
> maintain and QA gdb on hpux 10.20.  It takes work even if gdb on hpux
> 11.11 is already working.  I would rather spend my attention somewhere
> else, and so would everybody else in the world, judging by the level of
> activity.

Yes.

Andrew



  parent reply	other threads:[~2004-01-08 17:12 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-08  2:50 Michael Elizabeth Chastain
2004-01-08  4:12 ` John David Anglin
2004-01-08 17:12 ` Andrew Cagney [this message]
2004-01-08 18:04 ` John David Anglin
2004-01-08 18:42 Michael Elizabeth Chastain
2004-01-08 18:53 ` John David Anglin
2004-01-08 19:42 Michael Elizabeth Chastain
2004-01-08 20:30 ` John David Anglin
2004-01-11 15:25 ` Andrew Cagney
2004-01-11 22:06 Michael Elizabeth Chastain

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=3FFD8F84.7040100@gnu.org \
    --to=cagney@gnu.org \
    --cc=brobecker@act-europe.fr \
    --cc=dave@hiauly1.hia.nrc.ca \
    --cc=gdb@sources.redhat.com \
    --cc=mec.gnu@mindspring.com \
    /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