From: Yao Qi <qiyaoltc@gmail.com>
To: Jason Duerstock <jason.duerstock@gmail.com>
Cc: Binutils <binutils@sourceware.org>, Yao Qi <yao.qi@linaro.org>,
GDB Patches <gdb-patches@sourceware.org>
Subject: Re: ia64 build failure against master
Date: Thu, 08 Mar 2018 16:08:00 -0000 [thread overview]
Message-ID: <CAH=s-PMJFDmeJ_-b7dJgKfQd5dqdwMyRiFVETP965shA5LDRgw@mail.gmail.com> (raw)
In-Reply-To: <CAP5F8c+oi50ds7iqmbkfRgEuJjwOLfUe_TsackBwso3FwQreBQ@mail.gmail.com>
On Thu, Mar 8, 2018 at 3:08 PM, Jason Duerstock
<jason.duerstock@gmail.com> wrote:
> I was trying to compile the latest source on ia64 and got this error:
>
> ../../gdb/ia64-tdep.c: In function ‘register_status
> ia64_pseudo_register_read(gdbarch*, readable_regcache*, int,
> gdb_byte*)’:
> ../../gdb/ia64-tdep.c:942:64: error: invalid conversion from
> ‘readable_regcache*’ to ‘regcache*’ [-fpermissive]
> || libunwind_get_reg_special (gdbarch, regcache, regnum, buf) != 0)
> ^
> In file included from ../../gdb/ia64-tdep.h:25:0,
> from ../../gdb/ia64-tdep.c:39:
> ../../gdb/ia64-libunwind-tdep.h:73:5: note: initializing argument 2
> of ‘int libunwind_get_reg_special(gdbarch*, regcache*, int, void*)’
> int libunwind_get_reg_special (struct gdbarch *gdbarch,
> ^~~~~~~~~~~~~~~~~~~~~~~~~
> make[2]: *** [Makefile:1605: ia64-tdep.o] Error 1
> make[2]: Leaving directory '/mnt/b/native/binutils-gdb/build/gdb'
> make[1]: *** [Makefile:10421: all-gdb] Error 2
> make[1]: Leaving directory '/mnt/b/native/binutils-gdb/build'
> make: *** [Makefile:850: all] Error 2
>
> It looks related to commit 849d0ba8. My system has libunwind installed.
>
I'll take a look.
--
Yao (齐尧)
next parent reply other threads:[~2018-03-08 16:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAP5F8c+oi50ds7iqmbkfRgEuJjwOLfUe_TsackBwso3FwQreBQ@mail.gmail.com>
2018-03-08 16:08 ` Yao Qi [this message]
2018-03-09 15:40 ` [PATCH] Fix ia64 GDB build Yao Qi
2018-03-09 17:49 ` Jason Duerstock
2018-03-12 9:18 ` Yao Qi
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='CAH=s-PMJFDmeJ_-b7dJgKfQd5dqdwMyRiFVETP965shA5LDRgw@mail.gmail.com' \
--to=qiyaoltc@gmail.com \
--cc=binutils@sourceware.org \
--cc=gdb-patches@sourceware.org \
--cc=jason.duerstock@gmail.com \
--cc=yao.qi@linaro.org \
/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