From: Randolph Chung <randolph@tausq.org>
To: Andrew Cagney <cagney@gnu.org>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [patch/commit] Fix nested header include in infttrace.h
Date: Wed, 26 May 2004 16:57:00 -0000 [thread overview]
Message-ID: <20040526165722.GB7207@tausq.org> (raw)
In-Reply-To: <40B4CA7D.7080302@gnu.org>
> Unfortunatly this is a GCC extension. It sounds like a header file is
really?! wow...
fwiw, this works with the ANSI C hp compiler too, and hpux is the only
thing that uses infttrace.h ....
> missing:
> #ifndef FOO_H
> #define FOO_H
> #endif
> wrappers? Adding them is ``obvious''.
no, it's not that... this brings in target.h "too early", so that when
a C file tries to include tm.h, we cannot override some #defines.
the alternative is:
+#undef PC_REQUIRES_RUN_BEFORE_USE
#define PC_REQUIRES_RUN_BEFORE_USE(pc) hppa_pc_requires_run_before_use (pc)
in config/pa/tm-hppa.h.
randolph
--
Randolph Chung
Debian GNU/Linux Developer, hppa/ia64 ports
http://www.tausq.org/
next prev parent reply other threads:[~2004-05-26 16:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-26 15:41 Randolph Chung
2004-05-26 16:48 ` Andrew Cagney
2004-05-26 16:57 ` Randolph Chung [this message]
2004-05-26 19:29 ` Andrew Cagney
2004-06-07 18:04 ` Andrew Cagney
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=20040526165722.GB7207@tausq.org \
--to=randolph@tausq.org \
--cc=cagney@gnu.org \
--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