From: "Rude, Randy [Cont]" <Randy.Rude@gdcanada.com>
To: 'Andrew Cagney' <ac131313@ges.redhat.com>
Cc: gdb@sources.redhat.com
Subject: RE: Problem building 5.2 for m68k-elf on Solaris
Date: Thu, 27 Jun 2002 14:56:00 -0000 [thread overview]
Message-ID: <83E3831A88E65844B01DB1A73FB66F930168463A@CSDNT99.cdcgy.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 122 bytes --]
>
> Can you try moving the #include "bcache.h" from symtab.h to
> objfiles.h?
That fixes it. Thanks Andrew!
Randy
[-- Attachment #2: bcache.patch --]
[-- Type: application/octet-stream, Size: 947 bytes --]
diff -Nwupr gdb-5.2-orig/gdb/objfiles.h gdb-5.2/gdb/objfiles.h
--- gdb-5.2-orig/gdb/objfiles.h Fri Oct 12 13:07:07 2001
+++ gdb-5.2/gdb/objfiles.h Thu Jun 27 14:34:53 2002
@@ -22,6 +22,8 @@
#if !defined (OBJFILES_H)
#define OBJFILES_H
+#include "bcache.h"
+
/* This structure maintains information on a per-objfile basis about the
"entry point" of the objfile, and the scope within which the entry point
exists. It is possible that gdb will see more than one objfile that is
diff -Nwupr gdb-5.2-orig/gdb/symtab.h gdb-5.2/gdb/symtab.h
--- gdb-5.2-orig/gdb/symtab.h Thu Feb 21 17:17:13 2002
+++ gdb-5.2/gdb/symtab.h Thu Jun 27 15:01:49 2002
@@ -28,7 +28,6 @@
#include "obstack.h"
#define obstack_chunk_alloc xmalloc
#define obstack_chunk_free xfree
-#include "bcache.h"
/* Don't do this; it means that if some .o's are compiled with GNU C
and some are not (easy to do accidentally the way we configure
next reply other threads:[~2002-06-27 21:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-27 14:56 Rude, Randy [Cont] [this message]
2002-06-28 14:04 ` Andrew Cagney
-- strict thread matches above, loose matches on Subject: below --
2002-06-28 8:49 Rude, Randy [Cont]
2002-06-27 10:48 Rude, Randy [Cont]
2002-06-27 12:04 ` Andrew Cagney
2002-06-10 14:02 Rude, Randy [Cont]
2002-06-26 20:38 ` Andrew Cagney
2002-06-10 10:13 Rude, Randy [Cont]
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=83E3831A88E65844B01DB1A73FB66F930168463A@CSDNT99.cdcgy.com \
--to=randy.rude@gdcanada.com \
--cc=ac131313@ges.redhat.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