From: gdb@thewrittenword.com
To: gdb@sources.redhat.com
Cc: "Coleman, Michael" <MKC@Stowers-Institute.org>
Subject: Re: status of gdb on Tru64 5.1?
Date: Thu, 27 Sep 2001 07:42:00 -0000 [thread overview]
Message-ID: <20010927094202.B89616@oolong.il.thewrittenword.com> (raw)
In-Reply-To: <20010927093935.A89616@oolong.il.thewrittenword.com>
On Thu, Sep 27, 2001 at 09:39:35AM -0500, gdb@thewrittenword.com wrote:
> On Tue, Sep 25, 2001 at 08:58:55AM -0500, Coleman, Michael wrote:
> > Does anyone know the status of gdb on Tru64 5.1? Neither the latest release
> > nor the CVS head currently compile. (The CVS head seems to have problems
> > with the register definitions used in alpha-nat.c:101-108.)
>
> I can build the 5.1 branch on Tru64 UNIX 5.1. I have not tested yet
> though.
Oops, scratch that:
cc -c -std -I. -I. -I./config -DHAVE_CONFIG_H -I./../include/opcode
-I./../readline/.. -I../bfd -I./../bfd -I./../include -I../intl
-I./../intl -DMI_OUT=1 -DUI_OUT=1 alpha-nat.c
cc: Error: alpha-nat.c, line 101: In the initializer for
core_reg_mapping[0], "EF_V0" is not declared. (undeclared)
EF_V0, EF_T0, EF_T1, EF_T2, EF_T3, EF_T4, EF_T5, EF_T6,
----^
cc: Error: alpha-nat.c, line 101: In the initializer for
core_reg_mapping[1], "EF_T0" is not declared. (undeclared)
EF_V0, EF_T0, EF_T1, EF_T2, EF_T3, EF_T4, EF_T5, EF_T6,
-----------^
cc: Error: alpha-nat.c, line 101: In the initializer for
core_reg_mapping[2], "EF_T1" is not declared. (undeclared)
...
--
albert chin (china@thewrittenword.com)
prev parent reply other threads:[~2001-09-27 7:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-25 7:01 Coleman, Michael
2001-09-26 21:44 ` [5.1] " Andrew Cagney
2001-09-27 1:03 ` Joel Brobecker
2001-09-27 7:47 ` gdb
2001-09-27 8:45 ` Joel Brobecker
2001-09-27 7:39 ` gdb
2001-09-27 7:42 ` gdb [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=20010927094202.B89616@oolong.il.thewrittenword.com \
--to=gdb@thewrittenword.com \
--cc=MKC@Stowers-Institute.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