From: Alan Modra <amodra@bigpond.net.au>
To: Michael Elizabeth Chastain <mec.gnu@mindspring.com>
Cc: gdb@sources.redhat.com
Subject: Re: error: `som_bfd_is_group_section' undeclared
Date: Sun, 02 May 2004 06:20:00 -0000 [thread overview]
Message-ID: <20040502062032.GW2565@bubble.modra.org> (raw)
In-Reply-To: <20040501235637.290264B104@berman.michael-chastain.com>
On Sat, May 01, 2004 at 07:56:37PM -0400, Michael Elizabeth Chastain wrote:
> I'm getting a compile error when I build gdb HEAD on native
> hppa2.0w-hp-hpux11.11. It's an undeclared symbol,
> som_bfd_is_group_section .
Oops. The SOM bfd target isn't built with --enable-targets=all, because
it uses host headers (and I found all the places that needed a define by
compiling then fixing errors).
* som.c (som_bfd_is_group_section): Define.
Index: bfd/som.c
===================================================================
RCS file: /cvs/src/src/bfd/som.c,v
retrieving revision 1.40
diff -u -p -r1.40 som.c
--- bfd/som.c 28 Apr 2004 18:02:48 -0000 1.40
+++ bfd/som.c 2 May 2004 06:04:22 -0000
@@ -1,6 +1,6 @@
/* bfd back-end for HP PA-RISC SOM objects.
Copyright 1990, 1991, 1992, 1993, 1994, 1995, 1996, 1997, 1998, 1999,
- 2000, 2001, 2002, 2003
+ 2000, 2001, 2002, 2003, 2004
Free Software Foundation, Inc.
Contributed by the Center for Software Science at the
@@ -6410,6 +6410,7 @@ som_bfd_link_split_section (abfd, sec)
#define som_bfd_gc_sections bfd_generic_gc_sections
#define som_bfd_merge_sections bfd_generic_merge_sections
+#define som_bfd_is_group_section bfd_generic_is_group_section
#define som_bfd_discard_group bfd_generic_discard_group
const bfd_target som_vec = {
--
Alan Modra
IBM OzLabs - Linux Technology Centre
next prev parent reply other threads:[~2004-05-02 6:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-01 23:56 Michael Elizabeth Chastain
2004-05-02 6:20 ` Alan Modra [this message]
2004-05-02 21:14 Michael Elizabeth Chastain
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=20040502062032.GW2565@bubble.modra.org \
--to=amodra@bigpond.net.au \
--cc=gdb@sources.redhat.com \
--cc=mec.gnu@mindspring.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).