Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@mvista.com>
To: Mark Kettenis <kettenis@science.uva.nl>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [PATCH] Make ARM/Linux build on current glibc
Date: Wed, 31 Oct 2001 08:20:00 -0000	[thread overview]
Message-ID: <20011031112035.A1749@nevyn.them.org> (raw)
In-Reply-To: <s3ilmhr23gn.fsf@debye.wins.uva.nl>

On Wed, Oct 31, 2001 at 05:12:40PM +0100, Mark Kettenis wrote:
> Daniel Jacobowitz <drow@mvista.com> writes:
> 
> > On Wed, Oct 31, 2001 at 10:57:47AM -0500, Daniel Jacobowitz wrote:
> > > <sys/user.h> no longer includes <asm/ptrace.h>.  If we want it, we've got to
> > > get it ourselves.
> > 
> > Right... include the patch..
> > 
> > Committed as obvious.
> 
> In principle we shouldn't include any <asm/*> on Linux.  Why do you
> need to include <asm/ptrace.h>?

Because <sys/user.h> used to and no longer does.  If you prefer I can
define the structure (pt_regs) in the file itself.

<sys/user.h> now uses a "struct user_regs" instead, but we can't use
that without requiring glibc 2.2.x.

-- 
Daniel Jacobowitz                           Carnegie Mellon University
MontaVista Software                         Debian GNU/Linux Developer


  parent reply	other threads:[~2001-10-31  8:20 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-31  7:57 Daniel Jacobowitz
2001-10-31  7:58 ` Daniel Jacobowitz
     [not found]   ` <s3ilmhr23gn.fsf@debye.wins.uva.nl>
2001-10-31  8:20     ` Daniel Jacobowitz [this message]
2001-10-31 10:18       ` Mark Kettenis
2001-10-31 10:57         ` Daniel Jacobowitz
2001-11-07  8:22         ` 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=20011031112035.A1749@nevyn.them.org \
    --to=drow@mvista.com \
    --cc=gdb-patches@sources.redhat.com \
    --cc=kettenis@science.uva.nl \
    /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