Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: "H . J . Lu" <hjl@lucon.org>
To: gdb@sources.redhat.com
Subject: Re: prgregset_t vs gdb_gregset_t on Linux: not the same!
Date: Mon, 11 Jun 2001 09:45:00 -0000	[thread overview]
Message-ID: <20010611094526.B28735@lucon.org> (raw)
In-Reply-To: <20010611092412.A27338@nevyn.them.org>

On Mon, Jun 11, 2001 at 09:24:12AM -0700, Daniel Jacobowitz wrote:
> > With regard to #include "tm-linux.h", I'd mimic *bsd.  That way it is 
> > clear exactly what is going on.  Regardless of the semantics of "" vs <>.
> 
> Mimic *bsd in what?  In GDB, the only BSD headers I see under config/
> are *-nbsd.h, and those have the same problem we do...
> 

IMHO, minic any *bsd config for Linux/mips is asking for trouble.
Linux/mips should minic a working, similar Linux config. I will take
a look at alpha, ia64, ppc, x86, in that order. Of course, it is always
a good idea to use <>, not "" to include xx-linux.h.


H.J.


  reply	other threads:[~2001-06-11  9:45 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
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 [this message]
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=20010611094526.B28735@lucon.org \
    --to=hjl@lucon.org \
    --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