From: Daniel Jacobowitz <drow@mvista.com>
To: Michael Snyder <msnyder@redhat.com>
Cc: "H . J . Lu" <hjl@lucon.org>, gdb-patches@sources.redhat.com
Subject: Re: Bad checkin breaks Linux
Date: Mon, 14 Jan 2002 14:47:00 -0000 [thread overview]
Message-ID: <20020114174713.A16250@nevyn.them.org> (raw)
In-Reply-To: <3C433357.602055C3@redhat.com>
On Mon, Jan 14, 2002 at 11:36:55AM -0800, Michael Snyder wrote:
> Well, that's kind of bogus! ;-(
> Seems to me that HAVE_PTRACE_GETFPXREGS should mean that
> we have ptrace_getfpxregs. Maybe MIPS should not define
> it if it doesn't use it.
>
> OK, I don't see how to resolve this easily -- I'll just
> remove the fpxregs from the gcore file for now (so that
> it will build for mips).
We'll need to autoconf for the appropriate types as well, I expect -
but I'm all for putting that off until we have a proper framework for
'extra' register sets.
--
Daniel Jacobowitz Carnegie Mellon University
MontaVista Software Debian GNU/Linux Developer
prev parent reply other threads:[~2002-01-14 22:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-12 16:32 H . J . Lu
2002-01-14 8:39 ` Elena Zannoni
2002-01-14 11:42 ` Michael Snyder
2002-01-14 14:47 ` Daniel Jacobowitz [this message]
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=20020114174713.A16250@nevyn.them.org \
--to=drow@mvista.com \
--cc=gdb-patches@sources.redhat.com \
--cc=hjl@lucon.org \
--cc=msnyder@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