From: Richard Earnshaw <rearnsha@arm.com>
To: Andrew Cagney <ac131313@cygnus.com>
Cc: Richard.Earnshaw@arm.com, gdb-patches@sources.redhat.com
Subject: Re: [patch] arm-netbsd clean up native include file.
Date: Wed, 15 May 2002 10:07:00 -0000 [thread overview]
Message-ID: <200205151706.SAA13455@cam-mail2.cambridge.arm.com> (raw)
In-Reply-To: Your message of "Wed, 15 May 2002 13:01:53 EDT." <3CE29481.4010207@cygnus.com>
> > /* Get generic NetBSD native definitions. */
> > ! #include <nm-nbsd.h>
>
> Use "config/nm-nbsd.h". That way there is no question as to where it is
> comming from.
Nor should there be with <nm-nbsd.h>, since config/arm isn't on the
include path. This is the convention in all the other include files I've
seen that play this sort of game.
R.
next prev parent reply other threads:[~2002-05-15 17:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-15 9:25 Richard Earnshaw
2002-05-15 10:01 ` Andrew Cagney
2002-05-15 10:07 ` Richard Earnshaw [this message]
2002-05-15 10:31 ` Andrew Cagney
2002-05-15 10:41 ` Richard Earnshaw
2002-05-16 7:01 ` Richard Earnshaw
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=200205151706.SAA13455@cam-mail2.cambridge.arm.com \
--to=rearnsha@arm.com \
--cc=Richard.Earnshaw@arm.com \
--cc=ac131313@cygnus.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