From: Tom Tromey <tom@tromey.com>
To: gdb-buildbot@sergiodj.net
Cc: gdb-patches@sourceware.org, Tom Tromey <tom@tromey.com>
Subject: Re: Breakage on builder Solaris11-sparcv9-m64, revision 098f9ed48e1c94a2624c825ba93d72b163d41196
Date: Thu, 18 Jul 2019 13:59:00 -0000 [thread overview]
Message-ID: <87muhbxx33.fsf@tromey.com> (raw)
In-Reply-To: <E1hnurB-0005kq-33@gdb-buildbot.osci.io> (gdb-buildbot's message of "Wed, 17 Jul 2019 21:05:13 -0400")
>>>>> ">" == gdb-buildbot <gdb-buildbot@sergiodj.net> writes:
>> CXX tui/tui-out.o
>> ../../binutils-gdb/gdb/tui/tui-layout.c: In function void show_data(tui_layout_type):
>> ../../binutils-gdb/gdb/tui/tui-layout.c:682:72: error: no matching function for call to tui_win_info::reset(int&, int, int, int)
>> tui_win_list[DATA_WIN]->reset (data_height, tui_term_width (), 0, 0);
>> ^
>> In file included from ../../binutils-gdb/gdb/tui/tui-layout.c:31:0:
>> ../../binutils-gdb/gdb/tui/tui-data.h:64:16: note: candidate: virtual void tui_gen_win_info::reset(tui_win_type, int, int, int, int)
>> virtual void reset (enum tui_win_type win_type,
>> ^~~~~
>> ../../binutils-gdb/gdb/tui/tui-data.h:64:16: note: candidate expects 5 arguments, 4 provided
Sorry about that. I didn't rebuild every patch in the series during all
the rebasing and whatnot. I'll make sure to do that with the next
series.
Tom
next prev parent reply other threads:[~2019-07-18 13:59 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-18 1:05 Oh dear. I regret to inform you that commit 098f9ed48e1c94a2624c825ba93d72b163d41196 might be unfortunate gdb-buildbot
2019-07-18 1:05 ` Breakage on builder Solaris11-sparcv9-m64, revision 098f9ed48e1c94a2624c825ba93d72b163d41196 gdb-buildbot
2019-07-18 13:59 ` Tom Tromey [this message]
2019-07-18 1:36 ` Breakage on builder Solaris11-amd64-m64, " gdb-buildbot
2019-07-18 2:32 ` Breakage on builder NetBSD-x86_64-m64, " gdb-buildbot
2019-07-19 12:56 ` Breakage on builder Fedora-x86_64-cc-with-index, " gdb-buildbot
2019-07-19 12:58 ` Breakage on builder Fedora-x86_64-m32, " gdb-buildbot
2019-07-19 13:03 ` Breakage on builder Fedora-x86_64-m64, " gdb-buildbot
2019-07-19 13:06 ` Breakage on builder Fedora-x86_64-native-extended-gdbserver-m32, " gdb-buildbot
2019-07-19 13:10 ` Breakage on builder Fedora-x86_64-native-extended-gdbserver-m64, " gdb-buildbot
2019-07-19 13:13 ` Breakage on builder Fedora-x86_64-native-gdbserver-m64, " gdb-buildbot
2019-07-19 14:14 ` Breakage on builder Fedora-x86_64-native-gdbserver-m32, " gdb-buildbot
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=87muhbxx33.fsf@tromey.com \
--to=tom@tromey.com \
--cc=gdb-buildbot@sergiodj.net \
--cc=gdb-patches@sourceware.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).