From: Michael Chastain <mec.gnu@mindspring.com>
To: Mark_Helzer@adp.com, gdb@sources.redhat.com
Subject: Re: Problem compiling 6.2 on dec alpha
Date: Wed, 01 Sep 2004 20:47:00 -0000 [thread overview]
Message-ID: <41363575.nailLXE17MYO9@mindspring.com> (raw)
In-Reply-To: <86F706952883A445B8B6D8ACF27C2B76E0178D@nexus.plaza.ds.adp.com>
Hmmm, try editing bfd-in.h and bfd-in2.h and adding
this line near the top:
#include "bfdlink.h"
I suspect that the Digital Unix compiler is bitching about a parameter
mismatch because it has an incomplete definition of struct bfd_link_info
when it parses the prototype for bfd_get_relocated_section_contents, and
then later on it has a complete definition of struct bfd_link_info when
it parses definition for bfd_get_relocated_section_contents.
Or, you could try using gcc to build gdb. I recently built gdb 6.0 on
native alphaev56-dec-osf4.0g with gcc 3.3.4. I can't build any later
gdb's because they run into PR gdb/1626. I haven't tried actually
*running* gdb on osf 4.0 after I built it, though.
Hope this helps,
Michael Chastain
prev parent reply other threads:[~2004-09-01 20:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-01 20:09 Mark Helzer
2004-09-01 20:47 ` Michael Chastain [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=41363575.nailLXE17MYO9@mindspring.com \
--to=mec.gnu@mindspring.com \
--cc=Mark_Helzer@adp.com \
--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