public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Jim Wilson <jimw@sifive.com>
To: Nelson Chu <nelson.chu@sifive.com>
Cc: Binutils <binutils@sourceware.org>
Subject: Re: [PATCH] RISC-V: Fix the error when building RISC-V linux native gdbserver.
Date: Tue, 2 Jun 2020 13:43:20 -0700	[thread overview]
Message-ID: <CAFyWVaYsGT05rBcePE_YFPQRG20iXsgfANkR98p+fEvW=mNsRA@mail.gmail.com> (raw)
In-Reply-To: <1591067065-5438-1-git-send-email-nelson.chu@sifive.com>

On Mon, Jun 1, 2020 at 8:04 PM Nelson Chu <nelson.chu@sifive.com> wrote:
> Inlcude the bfd.h in the include/opcode/riscv.h may cause gdbserver fail
> to build.  I just want to use the `bfd_boolean` in the opcodes/riscv-opc.c,
> but I didn't realize this cause the build failed.  Fortunately, I can also
> use the `int` as the function return types just like others in the
> opcodes/riscv-opc.c.

OK.  Thanks for the fix.

Jim

  reply	other threads:[~2020-06-02 20:43 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-02  3:04 Nelson Chu
2020-06-02 20:43 ` Jim Wilson [this message]
2020-06-03  1:24   ` Nelson Chu

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='CAFyWVaYsGT05rBcePE_YFPQRG20iXsgfANkR98p+fEvW=mNsRA@mail.gmail.com' \
    --to=jimw@sifive.com \
    --cc=binutils@sourceware.org \
    --cc=nelson.chu@sifive.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).