From: Andrew Cagney <ac131313@ges.redhat.com>
To: Joel Brobecker <brobecker@gnat.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFA] Missing #include in objfiles.h?
Date: Thu, 01 Aug 2002 13:48:00 -0000 [thread overview]
Message-ID: <3D499E85.9080506@ges.redhat.com> (raw)
In-Reply-To: <20020801192836.GY683@gnat.com>
> I'm not sure if this is intended or not, but objfiles.h relies on
> symfile.h for the definition of certain structures. However, objfiles
> does not #include symfile. So my attempt to include objfiles without
> prior including symfile caused a compilation error.
What exactly? A mindless grep suggests opaque references but not a hard
dependency. Adding an opaque ``struct sym_fns;'' to avoid an include is ok.
> This patch adds the #include, assuming this was not intentional. Tested
> by "./configure; make".
>
> 2002-08-01 Joel Brobecker <brobecker@gnat.com>
>
> * objfiles.h: Add missing #include "symfile.h"
>
> * Makefile.in (objfiles_h): Add dependency on symfile.h and dependents.
>
> Ok to apply?
If there is a direct dependency then, yes, it should include it.
> + #include "symfile.h"
Suggest a comment mentioning what was needed.
enjoy,
Andrew
PS: I've this memory of, on true64 or hpux, there being a tangled mess
of includes that stopped the above from being added. That, however, is
a true64/hppa problem and is likely fixed by multi-arching.
next prev parent reply other threads:[~2002-08-01 20:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-01 12:28 Joel Brobecker
2002-08-01 13:48 ` Andrew Cagney [this message]
2002-08-02 20:10 ` Joel Brobecker
2002-08-03 16:25 ` Andrew Cagney
2002-08-05 9:18 ` Joel Brobecker
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=3D499E85.9080506@ges.redhat.com \
--to=ac131313@ges.redhat.com \
--cc=brobecker@gnat.com \
--cc=gdb-patches@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