From: mec.gnu@mindspring.com (Michael Elizabeth Chastain)
To: cagney@gnu.org
Cc: brobecker@gnat.com, gdb@sources.redhat.com
Subject: Re: [Fwd: native hppa2.0w-hp-hpux11.11]
Date: Mon, 08 Dec 2003 23:53:00 -0000 [thread overview]
Message-ID: <20031208235324.28E474B412@berman.michael-chastain.com> (raw)
> I think the most useful thing to find is a copy of the relevant ABI.
> With that it should be possible to revamp the code, bringing it up to
> scratch.
I'm not close to that yet.
. readline does not build with gcc. I decided to tackle this first.
I'm creating some patches for the standalone readline and I will
submit them to Chet Ramey, the readline maintainer. If he likes them,
then I will ask Elena to put them in our local readline as well.
. I have to decide which compilers to build gdb with. There are
four compilers to choose from: gcc, the bundled cc, the unbundled
ansi c compiler, and the aC++ compiler.
The bundled cc isn't even installed on the HP test drive machines
so I expect that I will just punt on that. I think that all the
others need to work though.
. I have to decide which compilers to build test programs with,
and figure out which debug formats make sense to test. Also there is
32-bit versus 64-bit and pre-standard-c++-library versus
standard-c++-library.
. I have to do something about all the little cheats in migchain and
migbat where they are not really set up for multiple architectures
yet. I don't really have to fix them, but I have to get them to the
point where I can do work with them.
And here's a big one:
. What do we do about hpux 10.20?
There's no hpux 10.20 in the HP test drive pool. HP has a good reason
for this: they discontinued hpux 10.20 on 2002-06-30, and obsoleted it
on 2003-06-30!
http://h21007.www2.hp.com/dspp/tech/tech_TechDocumentDetailPage_IDX/1,1701,5143,00.html
All of hpux10* is no longer supported by HP. So we have no maintainer
and no machine. But we do have a recent PR, PR gdb/1411.
I would like to give hppa*-hp-hpux10* the boot. Put it through the
obsoletion process, and then remove any test code which is
hpux10-specific, and then not worry about breaking hpux10 while I am
fixing hpux11.
What do you think of that?
Michael C
next reply other threads:[~2003-12-08 23:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-08 23:53 Michael Elizabeth Chastain [this message]
2003-12-09 0:03 ` Joel Brobecker
-- strict thread matches above, loose matches on Subject: below --
2003-12-09 0:28 Michael Elizabeth Chastain
2003-12-12 22:39 ` Andrew Cagney
2003-12-08 23:27 Andrew Cagney
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=20031208235324.28E474B412@berman.michael-chastain.com \
--to=mec.gnu@mindspring.com \
--cc=brobecker@gnat.com \
--cc=cagney@gnu.org \
--cc=gdb@sources.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