From: Daniel Jacobowitz <drow@mvista.com>
To: gdb-patches@sources.redhat.com, msnyder@redhat.com
Subject: linux-core support broke i386 compilation
Date: Wed, 09 Jan 2002 12:20:00 -0000 [thread overview]
Message-ID: <20020109152110.A1564@nevyn.them.org> (raw)
You reference a type 'gdb_fpxregset_t'. It doesn't appear to be defined
anywhere.
I'm also not sure that that's the right #ifdef for the check; PowerPC was
sounding like it would have an fpxregset (well, an xregset, really - no FP
involved) but without PTRACE_GETFPXREGS. fill_fpxregset also appears to
lack a prototype.
--
Daniel Jacobowitz Carnegie Mellon University
MontaVista Software Debian GNU/Linux Developer
next reply other threads:[~2002-01-09 20:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-09 12:20 Daniel Jacobowitz [this message]
2002-01-09 12:45 ` Daniel Jacobowitz
2002-01-09 14:32 ` Michael Snyder
2002-01-09 12:49 ` Michael Snyder
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=20020109152110.A1564@nevyn.them.org \
--to=drow@mvista.com \
--cc=gdb-patches@sources.redhat.com \
--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