From: Michael Eager <eager@eagerm.com>
To: Jan Kratochvil <jan.kratochvil@redhat.com>
Cc: Joel Brobecker <brobecker@adacore.com>, gdb-patches@sourceware.org
Subject: Re: [patch] Remove HPUX
Date: Wed, 19 Nov 2014 19:39:00 -0000 [thread overview]
Message-ID: <546CF204.2030803@eagerm.com> (raw)
In-Reply-To: <20141119185431.GA2360@host2.jankratochvil.net>
On 11/19/14 10:54, Jan Kratochvil wrote:
> On Fri, 17 Oct 2014 19:18:48 +0200, Michael Eager wrote:
>> On 10/17/14 06:26, Joel Brobecker wrote:
>>>> There is a LinkedIn HP-UX Users group with almost 4000 members.
>>>> I don't know whether it is active or moribund. It might be nice
>>>> to see if anyone in the group cares before pulling the plug.
>>>
>>> Would you mind sending them a link to this message, and ask if
>>> any of them would like to step up for it? FWIW, I don't have
>>> any idea of the status of the debugger. On PA, the last version
>>> I used was 6.3; on ia64, it was 7.5.
>>
>> I posted messages about dropping GDB support in HP-UX in
>> several LinkedIn groups related to HP-UX. Some messages are
>> awaiting approval.
>
> Are the messages still awaiting approval?
Folks on LinkedIn were mostly concerned that changes in FSF
GDB support would affect their use of HP's WDB debugger. I
assured them that this was not the case.
I was in touch with people in HP's debugger group about a week
ago. They have a version of gdb based on gdb-6.5 and their
changes have not been pushed back to FSF. They only use GDB
for GCC compilations, which they no longer support. (They
only support their aC++ compiler and wdb debugger.) They said
that they were aware of the proposal to drop HPUX support from
FSF GDB.
My contact at HP said that he had reached out to others
at HP to see if there was interest for keeping HPUX support
in FSF GDB alive, but hadn't received any positive responses.
As McCoy said "It's dead, Jim."
--
Michael Eager eager@eagercon.com
1960 Park Blvd., Palo Alto, CA 94306 650-325-8077
next prev parent reply other threads:[~2014-11-19 19:39 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-16 23:00 Jan Kratochvil
2014-10-17 0:21 ` Michael Eager
2014-10-17 13:26 ` Joel Brobecker
2014-10-17 17:18 ` Michael Eager
2014-11-19 18:54 ` Jan Kratochvil
2014-11-19 19:39 ` Michael Eager [this message]
2014-11-21 9:32 ` Pedro Alves
2015-03-13 19:26 ` [commit] " Jan Kratochvil
2015-03-13 19:43 ` Pedro Alves
2015-03-13 19:46 ` Jan Kratochvil
2015-03-13 19:55 ` Pedro Alves
2015-03-13 19:57 ` Jan Kratochvil
2015-03-10 5:04 ` Sergio Durigan Junior
2015-03-10 14:23 ` Michael Eager
2014-11-21 3:20 ` Yao Qi
2015-03-13 19:17 ` [testsuite patch] Remove gdb.hp [Re: [patch] Remove HPUX] Jan Kratochvil
2015-03-18 14:58 ` Remove --xdb? (Re: [testsuite patch] Remove gdb.hp [Re: [patch] Remove HPUX]) Pedro Alves
2015-03-20 16:17 ` [commit] [testsuite patch] Remove gdb.hp Jan Kratochvil
2015-03-20 17:48 ` [patch] Re: Remove --xdb? (Re: [testsuite patch] Remove gdb.hp) Jan Kratochvil
2015-04-10 19:27 ` Pedro Alves
2015-04-11 17:06 ` [doc patch] Remove --xdb Jan Kratochvil
2015-04-11 17:40 ` Eli Zaretskii
2015-04-11 17:54 ` [commit] " Jan Kratochvil
2014-12-01 14:21 ` [patch] Remove HPUX Simon Marchi
2015-03-11 21:57 ` Jan Kratochvil
2015-03-12 17:05 ` Pedro Alves
2015-03-13 18:34 ` Jan Kratochvil
2015-03-13 19:40 ` Pedro Alves
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=546CF204.2030803@eagerm.com \
--to=eager@eagerm.com \
--cc=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=jan.kratochvil@redhat.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