From: Andrew Cagney <cagney@gnu.org>
To: Jason Thorpe <thorpej@wasabisystems.com>
Cc: gdb@sources.redhat.com
Subject: Re: NetBSD/VAX?
Date: Sun, 29 Feb 2004 19:02:00 -0000 [thread overview]
Message-ID: <4042373B.9000106@gnu.org> (raw)
In-Reply-To: <0E44E922-6AE4-11D8-BC14-000A957650EC@wasabisystems.com>
> On Feb 29, 2004, at 10:04 AM, Andrew Cagney wrote:
>
>> NetBSD/VAX (GDB's only VAX system) doesn't build as a native debugger (it never has). It is missing changes to configure.host that stop it configuring. I suspect it lacks other stuff.
>
>
> At one point before 5.3, I had changes to bring the vax-netbsd* target totally up-to-date. I don't exactly remember why I didn't check them in.
>
> Anyway, I can probably dig them up and try to bring them up-to-date again.
Thanks! The most immediate problem is configure.host,
config/vax/nbsd.mh, and ptrace - none of that's in place, and trying to
use vaxbsd.mh leads to build errors.
I can probably look at the frame code after that (which is actually why
I'm trying to build it :-)
Andrew
> (Sigh, I haven't had time to work on GDB in *so* long...)
prev parent reply other threads:[~2004-02-29 19:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-29 18:04 NetBSD/VAX? Andrew Cagney
2004-02-29 18:22 ` NetBSD/VAX? Jason Thorpe
2004-02-29 19:02 ` Andrew Cagney [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=4042373B.9000106@gnu.org \
--to=cagney@gnu.org \
--cc=gdb@sources.redhat.com \
--cc=thorpej@wasabisystems.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