Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: Sergio Durigan Junior <sergiodj@redhat.com>
Cc: gdb-patches@sourceware.org, Joel Brobecker <brobecker@adacore.com>
Subject: Re: [patch+8.0] release branch: Fix: --enable-werror
Date: Sat, 22 Apr 2017 16:34:00 -0000	[thread overview]
Message-ID: <20170422162616.GA16968@host1.jankratochvil.net> (raw)
In-Reply-To: <87y3usv2h5.fsf@redhat.com>

On Sat, 22 Apr 2017 18:20:06 +0200, Sergio Durigan Junior wrote:
> On Friday, April 21 2017, Jan Kratochvil wrote:
> > gdb-8.0-branch
> > ./configure --enable-werror --enable-targets=all
> > aarch64-tdep.c:3045:13: error: ‘void selftests::aarch64_process_record_test()’ declared ‘static’ but never defined [-Werror=unused-function]
> > arm-tdep.c:9601:13: error: ‘void selftests::arm_record_test()’ declared ‘static’ but never defined [-Werror=unused-function]
...
> > Sergio: Shouldn't it be also buildbot-tested?
> 
> Yes, it should.  We have an Arch64 builder managed by Yao.  It should
> be possible to set up builders for the 8.0 branch.

FYI no specific arch is required for the builder, it even happened for me on
my x86_64.  These were *-tdep.c files so --enable-targets=all is enough to
trigger it.

Sure more archs would make better coverage even for nat/* files.


Jan


      reply	other threads:[~2017-04-22 16:34 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-21  8:52 Jan Kratochvil
2017-04-21 14:04 ` Pedro Alves
2017-04-21 14:18   ` [commit+8.0] " Jan Kratochvil
2017-04-22 16:20 ` Sergio Durigan Junior
2017-04-22 16:34   ` Jan Kratochvil [this message]

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=20170422162616.GA16968@host1.jankratochvil.net \
    --to=jan.kratochvil@redhat.com \
    --cc=brobecker@adacore.com \
    --cc=gdb-patches@sourceware.org \
    --cc=sergiodj@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