public inbox for gdb-testers@sourceware.org
help / color / mirror / Atom feed
From: sergiodj+buildbot@sergiodj.net
To: gdb-testers@sourceware.org
Subject: [binutils-gdb] frame.h: Forward-declare struct ui_out
Date: Thu, 06 Oct 2016 22:11:00 -0000	[thread overview]
Message-ID: <d73f9c4bab1a0ec82007f9d36b8a7bf5d34f7bf6@gdb-build> (raw)

*** TEST RESULTS FOR COMMIT d73f9c4bab1a0ec82007f9d36b8a7bf5d34f7bf6 ***

Author: Simon Marchi <simon.marchi@ericsson.com>
Branch: master
Commit: d73f9c4bab1a0ec82007f9d36b8a7bf5d34f7bf6

frame.h: Forward-declare struct ui_out

Fixes this failure when building in C mode.  I think it's relevant for master
as well, since it's a good practice to include (or forward-declare) what you
use.

In file included from ../../binutils-gdb/gdb/gdbarch.h:38:0,
                 from ../../binutils-gdb/gdb/defs.h:653,
                 from ../../binutils-gdb/gdb/dictionary.c:23:
../../binutils-gdb/gdb/frame.h:710:48: warning: struct ui_out declared inside parameter list will not be visible outside of this definition or declaration
 extern void print_stack_frame_to_uiout (struct ui_out *uiout,

gdb/ChangeLog:

	* frame.h: Forward-declare struct ui_out.


             reply	other threads:[~2016-10-06 22:11 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-06 22:11 sergiodj+buildbot [this message]
2016-10-06 22:11 ` Failures on Fedora-x86_64-native-gdbserver-m32, branch master sergiodj+buildbot
2016-10-07  0:20 ` Failures on Ubuntu-AArch64-m64, " sergiodj+buildbot
2016-10-07  4:25 ` Failures on Debian-i686, " sergiodj+buildbot
2016-10-07  5:22 ` Failures on Debian-i686-native-extended-gdbserver, " sergiodj+buildbot
2016-10-08  6:55 ` Failures on Fedora-ppc64be-native-gdbserver-m64, " sergiodj+buildbot
2016-10-08  7:37 ` Failures on Fedora-ppc64be-native-extended-gdbserver-m64, " sergiodj+buildbot
2016-10-08  9:32 ` Failures on Fedora-ppc64le-native-extended-gdbserver-m64, " sergiodj+buildbot
2016-10-08 10:36 ` Failures on Fedora-ppc64le-native-gdbserver-m64, " sergiodj+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=d73f9c4bab1a0ec82007f9d36b8a7bf5d34f7bf6@gdb-build \
    --to=sergiodj+buildbot@sergiodj.net \
    --cc=gdb-testers@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).