public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: <joel@OARcorp.com>
To: binutils@sourceware.cygnus.com
Subject: include/elf/hppa.h in gdb 4.18
Date: Thu, 01 Jul 1999 00:00:00 -0000	[thread overview]
Message-ID: <Pine.LNX.4.10.9906211344120.30023-100000@oar3remote> (raw)

Target: hppa1.1-rtems (a.k.a hppa*-*-*elf* | hppa*-*-lites* |
                             hppa*-*-sysv4* )

Since this is a bfd compilation problem for the version in gdb 4.18, I
thought I would report this here first for a hint.  

gcc -DHAVE_CONFIG_H -I. -I../../gdb-4.18/bfd -I. -D_GNU_SOURCE -I.
-I../../gdb-4.18/bfd -I../../gdb-4.18/bfd/../include -I../../gdb-4.18/bfd/../intl
-I../intl -O2 -g -c ../../gdb-4.18/bfd/elf32-hppa.c
In file included from ../../gdb-4.18/bfd/elf32-hppa.h:36,
                 from ../../gdb-4.18/bfd/elf32-hppa.c:199:
../../gdb-4.18/bfd/../include/elf/hppa.h:184: `elf32_hppa_reloc_type'
redeclared as different kind of symbol
../../gdb-4.18/bfd/../include/elf/hppa.h:100: previous declaration of
`elf32_hppa_reloc_type'

When I look at the file include/elf/hppa.h, I see that around line 184 is
this:

#ifndef RELOC_MACROS_GEN_FUNC
typedef enum elf32_hppa_reloc_type elf32_hppa_reloc_type;
#endif

No other elf/*.h file has anything like this.  Is the problem solution to
remove these three lines?

--joel
Joel Sherrill, Ph.D.             Director of Research & Development
joel@OARcorp.com                 On-Line Applications Research
Ask me about RTEMS: a free RTOS  Huntsville AL 35805
   Support Available             (256) 722-9985


             reply	other threads:[~1999-07-01  0:00 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-07-01  0:00 joel [this message]
1999-07-01  0:00 ` Jeffrey A Law
1999-07-01  0:00   ` joel
1999-07-01  0:00     ` Jeffrey A Law
1999-07-01  0:00       ` joel
1999-07-01  0:00 ` joel

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=Pine.LNX.4.10.9906211344120.30023-100000@oar3remote \
    --to=joel@oarcorp.com \
    --cc=binutils@sourceware.cygnus.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).