From: Joel Brobecker <brobecker@adacore.com>
To: Pierre Muller <pierre.muller@ics-cnrs.unistra.fr>
Cc: gdb-patches@sourceware.org
Subject: Re: [RFA 5/5] New patches to support --enable-targets=all for mingw64
Date: Tue, 14 Sep 2010 19:39:00 -0000 [thread overview]
Message-ID: <20100914175025.GI3845@adacore.com> (raw)
In-Reply-To: <000c01cb53e1$56476e60$02d64b20$@muller@ics-cnrs.unistra.fr>
> But shouldn't we then clearly state that we drop hpux 10.X versions
> support?
We can. I don't think this is necessary, but Eli might think differently.
In any case, it doesn't cost much to add a NEWS entry mentioning it.
> Should we remove the function get_hpux_major_release completely, or
> turn it into a function returning a variable, that could be set by
> some command like "set hpux-major-release-version XX" that would
> allow people using it on an old HPUX 10.X to still get old behavior?
For a platform such as pa-hpux, I would do the strict minimum to make
it work. I think you can just remove the function and assume version
is 11 or higher.
> Does anyone know of a good mailing list for HPUX developers to which
> we could forward that question?
It may sound harsh, but I personally think that the input from HP/UX
developers in general is only of moderate interest to us. As long as
no one steps up to the plate to support version 10.x of pa-hpux, we don't
have the necessary means to do so. In fact, pa-hpux in general hasn't
received much attention in the last few years. The only reason why
I haven't discussed its removal is because I am still planning on
contributing support for ia64-hpux, which should share a lot of code
with pa-hpux support.
My suggestion in this case is to KISS. If it turns out that this affects
a developer who wants to upgrade to gdb-7.3, then we can think of
alternative strategies, such as the one you suggested, and have him
test it. Otherwise, the user should just stay with the older version
of GDB.
--
Joel
prev parent reply other threads:[~2010-09-14 17:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-10 15:43 Pierre Muller
2010-09-13 19:14 ` Joel Brobecker
2010-09-14 11:44 ` Pierre Muller
2010-09-14 15:24 ` [RFC] hpux code fix ( was [RFA 5/5] New patches to support --enable-targets=all for mingw64) Pierre Muller
2010-09-27 17:34 ` [PING][RFC] " Pierre Muller
2010-09-27 17:43 ` Pedro Alves
2010-09-14 19:39 ` Joel Brobecker [this message]
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=20100914175025.GI3845@adacore.com \
--to=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=pierre.muller@ics-cnrs.unistra.fr \
/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