From: "Mark Kettenis" <mark.kettenis@xs4all.nl>
To: "John David Anglin" <dave@hiauly1.hia.nrc.ca>
Cc: "Daniel Jacobowitz" <drow@false.org>,
gdb@sourceware.org, dave.anglin@nrc-cnrc.gc.ca,
brobecker@adacore.com
Subject: Re: Likely obsolete pieces of GDB
Date: Sun, 17 Dec 2006 11:46:00 -0000 [thread overview]
Message-ID: <23697.82.92.89.47.1166355987.squirrel@webmail.xs4all.nl> (raw)
In-Reply-To: <200612170123.kBH1NfVF025104@hiauly1.hia.nrc.ca>
> > hppa*-*-hiux*
>
> Definitely obsolete.
However, there is no real benefit in dropping this, since the configuration
is identical to hppa*-*-hpux*.
> > vax-*-*
> >
> > (But not NetBSD or OpenBSD)
>
> Ultrix still might work but I doubt anybody other than myself still
> has such a machine running. There still some interest in linux.
I lost my SIMH Ultrix image to a disk crash a while ago. However, I'm
somewhat attached to vax-nat.c, since it is the best example of the
way the traditional UNIX ptrace() worked.
>
> > osf-share
> >
> > Something from this directory is used to build hpux-thread.o.
> > The rest of it is unused. hpux-thread.o is only enabled for
> > CMA threads, and PROBLEMS says (build/1411) that this hasn't
> > built at least since GDB 6.5. HP/UX has deprecated CMA threads
> > as of 11i.
> >
> > Is support for CMA threads still useful? Note that I'm talking
> > just about hpux-thread.o, not about support for HP/UX 10.20. The
> > PR is still open and still listed in PROBLEMS, but it looks like
> > Dave Anglin fixed it on 2004-11-22, so maybe it is. Or maybe
> > support for that platform is useful but not support for OSF
> > threads.
>
> I think CMA threads is still useful for HP-UX 10. GCC 4.3 still builds
> on this target with DCE/CMA thread support. I will continue to support
> HP-UX 10 in GCC at least for HP-UX 10. This generation of HP machines
> have proved very reliable and many are still running.
>
> I have built 6.5 on HP-UX 10.20. I will report back on the current
> status of the cvs source.
The build problems on HP-UX 10.20 seem to depend on which OS patches are
installed.
next prev parent reply other threads:[~2006-12-17 11:46 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-16 20:59 Daniel Jacobowitz
2006-12-16 21:23 ` Christopher Faylor
2007-02-10 21:42 ` Pedro Alves
2007-02-10 23:50 ` Daniel Jacobowitz
2007-02-19 1:25 ` Pedro Alves
2006-12-17 1:24 ` John David Anglin
2006-12-17 11:46 ` Mark Kettenis [this message]
2007-01-01 16:34 ` Daniel Jacobowitz
2006-12-18 3:03 ` John David Anglin
2006-12-18 3:43 ` John David Anglin
2006-12-20 16:07 ` John David Anglin
2006-12-20 17:41 ` John David Anglin
2007-01-01 16:33 ` Daniel Jacobowitz
2007-01-01 16:47 ` John David Anglin
2007-01-01 17:10 ` Mark Kettenis
2007-01-01 17:20 ` John David Anglin
2006-12-17 1:36 ` Russell Shaw
2006-12-17 12:20 ` Mark Kettenis
2006-12-17 14:26 ` Stephen & Linda Smith
2006-12-17 15:37 ` Daniel Jacobowitz
2006-12-20 6:01 ` Joel Brobecker
2006-12-17 13:40 ` Joel Brobecker
2007-01-01 16:46 ` Daniel Jacobowitz
2007-01-01 16:58 ` Mark Kettenis
2007-01-03 23:55 ` Jim Blandy
2007-02-10 20:50 ` Daniel Jacobowitz
2007-02-12 17:35 ` Joel Brobecker
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=23697.82.92.89.47.1166355987.squirrel@webmail.xs4all.nl \
--to=mark.kettenis@xs4all.nl \
--cc=brobecker@adacore.com \
--cc=dave.anglin@nrc-cnrc.gc.ca \
--cc=dave@hiauly1.hia.nrc.ca \
--cc=drow@false.org \
--cc=gdb@sourceware.org \
/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