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:41:00 -0000 [thread overview]
Message-ID: <200205151740.SAA16546@cam-mail2.cambridge.arm.com> (raw)
In-Reply-To: Your message of "Wed, 15 May 2002 13:31:09 EDT." <3CE29B5D.4070801@cygnus.com>
> >
> > 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.
>
> True. GDB tends to play this game:
>
> config/i386/nm-nbsd.h:#include "config/nm-nbsd.h"
> config/i386/tm-nbsd.h:#include "config/tm-nbsd.h"
> config/sparc/nm-nbsd.h:#include "config/nm-nbsd.h"
>
> So the question of <> behavour is avoided.
>
True. I'll change it.
BTW
for i in `find . -name \*.h -print`
do
base=`basename $i`
fgrep \"$base\" $i /dev/null |grep include
done
./alpha/nm-linux.h:#include "nm-linux.h"
./arm/nm-linux.h:#include "nm-linux.h"
./arm/tm-linux.h:#include "tm-linux.h"
./arm/xm-nbsd.h:#include "xm-nbsd.h"
./i386/nm-gnu.h:#include "nm-gnu.h"
./i386/nm-m3.h:#include "nm-m3.h"
./i386/nm-linux.h:#include "nm-linux.h"
./i386/tm-linux.h:#include "tm-linux.h"
./i386/tm-vxworks.h:#include "tm-vxworks.h"
./i386/xm-nbsd.h:#include "xm-nbsd.h"
./ia64/nm-linux.h:#include "nm-linux.h"
./ia64/tm-linux.h:#include "tm-linux.h"
./m68k/nm-linux.h:#include "nm-linux.h"
./m68k/nm-nbsd.h:#include "nm-nbsd.h"
./m68k/nm-sysv4.h:#include "nm-sysv4.h"
./m68k/tm-linux.h:#include "tm-linux.h"
./m68k/tm-nbsd.h:#include "tm-nbsd.h"
./m68k/xm-nbsd.h:#include "xm-nbsd.h"
./mips/nm-linux.h:#include "nm-linux.h"
./mips/tm-linux.h:#include "tm-linux.h"
./ns32k/nm-nbsd.h:#include "nm-nbsd.h"
./ns32k/tm-nbsd.h:#include "tm-nbsd.h"
./ns32k/xm-nbsd.h:#include "xm-nbsd.h"
./powerpc/nm-linux.h:#include "nm-linux.h"
./powerpc/nm-nbsd.h:#include "nm-nbsd.h"
./powerpc/tm-linux.h:#include "tm-linux.h"
./powerpc/tm-nbsd.h:#include "tm-nbsd.h"
./powerpc/tm-vxworks.h:#include "tm-vxworks.h"
./rs6000/xm-aix4.h:#include "xm-aix4.h"
./sh/tm-linux.h:#include "tm-linux.h"
./sparc/nm-linux.h:#include "nm-linux.h"
./sparc/tm-linux.h:#include "tm-linux.h"
./sparc/tm-nbsd.h:#include "tm-nbsd.h"
./sparc/xm-nbsd.h:#include "xm-nbsd.h"
next prev parent reply other threads:[~2002-05-15 17:41 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
2002-05-15 10:31 ` Andrew Cagney
2002-05-15 10:41 ` Richard Earnshaw [this message]
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=200205151740.SAA16546@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