From: Mark Kettenis <kettenis@gnu.org>
To: mec.gnu@mindspring.com
Cc: gdb@sources.redhat.com
Subject: Re: [RFC] HP-UX native support
Date: Mon, 18 Oct 2004 17:32:00 -0000 [thread overview]
Message-ID: <200410162156.i9GLucWf005983@elgar.sibelius.xs4all.nl> (raw)
In-Reply-To: <41713868.nailIAJ11B157@mindspring.com> (message from Michael Chastain on Sat, 16 Oct 2004 11:04:08 -0400)
Date: Sat, 16 Oct 2004 11:04:08 -0400
From: Michael Chastain <mec.gnu@mindspring.com>
Some scraps of thought:
In general, I'm okay with dropping support for follow-fork and
other hpux-only features.
It's not unimaginable that I'll re-implement some of these features in
a more general way. But I shouldn't make any promises about that.
Most of the PR's for hp-ux are about build problems, rather than
advanced features. So if building gdb gets better or stays the
same, that's okay.
My main motiviation for this is to scrap a lot of ugly
native-dependent code. This simplification means that building GDB
can only get better.
hpux 10.20 is obsolete and HP no longer supports it.
However, many people still use it.
Yup. At JIVE (www.jive.nl), we're still using 10.20 for "production".
Currently I'm working on our Correlator Control Software that runs on
the machine.
gdb has to work on hpux 11.00 and hpux 11.11 as well.
I can take care of testing those.
My current patches don't touch the code for 11.xx at all. So there's
no real need to test those. However, I'll probably attack 11.xx after
I'm finished with 10.20.
Mark
prev parent reply other threads:[~2004-10-16 21:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-16 15:04 Mark Kettenis
2004-10-16 16:59 ` Michael Chastain
2004-10-16 17:46 ` Daniel Jacobowitz
2004-10-18 17:32 ` Mark Kettenis [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=200410162156.i9GLucWf005983@elgar.sibelius.xs4all.nl \
--to=kettenis@gnu.org \
--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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).