From: Richard Earnshaw <rearnsha@arm.com>
To: Michael Snyder <msnyder@redhat.com>
Cc: Richard.Earnshaw@arm.com, gdb@sources.redhat.com,
binutils@sources.redhat.com
Subject: Re: GDB arm-netbsd build failure.
Date: Thu, 10 Jan 2002 06:30:00 -0000 [thread overview]
Message-ID: <200201101430.OAA07844@cam-mail2.cambridge.arm.com> (raw)
In-Reply-To: Your message of "Thu, 10 Jan 2002 14:21:14 GMT." <200201101421.OAA06940@cam-mail2.cambridge.arm.com>
> An arm-elf cross build now fails when building opcodes/arm-dis.c since the
> one of the prototypes you added in elf-bfd.h uses pid_t, which isn't
> defined at that point.
Hmm, thinking about it, pid_t is a very Unix-centric type anyway; so it is
somewhat dubious that this appears at all in the BFD libraries.
R.
next prev parent reply other threads:[~2002-01-10 14:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-09 11:45 Richard Earnshaw
2002-01-09 12:43 ` Michael Snyder
2002-01-10 6:21 ` Richard Earnshaw
2002-01-10 6:30 ` Richard Earnshaw [this message]
2002-01-10 9:25 ` 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=200201101430.OAA07844@cam-mail2.cambridge.arm.com \
--to=rearnsha@arm.com \
--cc=Richard.Earnshaw@arm.com \
--cc=binutils@sources.redhat.com \
--cc=gdb@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