Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: "H . J . Lu" <hjl@lucon.org>
To: Eli Zaretskii <eliz@is.elta.co.il>
Cc: Andrew Cagney <ac131313@cygnus.com>, gdb@sources.redhat.com
Subject: Re: prgregset_t vs gdb_gregset_t on Linux: not the same!
Date: Sun, 10 Jun 2001 01:20:00 -0000	[thread overview]
Message-ID: <20010610012039.A2982@lucon.org> (raw)
In-Reply-To: <Pine.SUN.3.91.1010610105519.5638E-100000@is>

On Sun, Jun 10, 2001 at 11:01:20AM +0300, Eli Zaretskii wrote:
> 
> On Sun, 10 Jun 2001, H . J . Lu wrote:
> 
> > The gdb configure links/copies mips/tm-littlelinux.h to tm.h. Now
> > gdb/tm.h has
> > 
> > ---
> > #ifndef TM_MIPSLITTLELINUX_H
> > #define TM_MIPSLITTLELINUX_H
> > 
> > #define TARGET_BYTE_ORDER LITTLE_ENDIAN
> > 
> > #include "mips/tm-linux.h"
> > ---
> > 
> > If in mips/tm-linux.h, there are
> > 
> > #include "mips/tm-mips.h"
> > #include "tm-linux.h"
> > 
> > mips/tm-linux.h is found by -Isrc/gdb/config. But can you guess which
> > tm-linux.h is included from mips/tm-linux.h? It is mips/tm-linux.h
> 
> This is all expected.  Perhaps it means that it's a bad idea to have 
> several headers by the same name in different directories, if some port 

It is a common practice in gcc and gdb.

> might include more than one of those headers, because small changes in 
> the order of the -I options can break the build.

It is ok to have files with the same name in src/gdb/config and
src/gdb/config/machine as long as

1. We never use -Isrc/gdb/config/machine. It has been true and I don't
think we should change.
2. We always use <> to include files in src/gdb/config/machine. That is
how it is done in gcc and I have sent a patch to do the same in gdb for
Linux:

http://sources.redhat.com/ml/gdb-patches/2001-05/msg00048.html


H.J.


  parent reply	other threads:[~2001-06-10  1:20 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-06-08 13:27 Daniel Jacobowitz
2001-06-08 15:58 ` Daniel Jacobowitz
2001-06-08 22:14   ` H . J . Lu
2001-06-09 11:50     ` Mark Kettenis
2001-06-09 13:34     ` Andrew Cagney
2001-06-10  0:23       ` H . J . Lu
     [not found]         ` <Pine.SUN.3.91.1010610105519.5638E-100000@is>
2001-06-10  1:20           ` H . J . Lu [this message]
2001-06-11  6:48         ` Andrew Cagney
2001-06-11  8:58           ` H . J . Lu
2001-06-11 10:45             ` Andrew Cagney
2001-06-11  9:24           ` Daniel Jacobowitz
2001-06-11  9:45             ` H . J . Lu
2001-06-11 10:04               ` Daniel Jacobowitz
2001-06-11 10:45                 ` H . J . Lu
2001-06-09 15:23     ` Daniel Jacobowitz
2001-06-09 11:50   ` Mark Kettenis
2001-06-09 15:42     ` Daniel Jacobowitz

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=20010610012039.A2982@lucon.org \
    --to=hjl@lucon.org \
    --cc=ac131313@cygnus.com \
    --cc=eliz@is.elta.co.il \
    --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