public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Mark Wielaard <mark@klomp.org>
To: Jan Beulich <jbeulich@suse.com>
Cc: binutils@sourceware.org
Subject: Re: ☠ Buildbot (GNU Toolchain): binutils-gdb - failed compile (failure) (master)
Date: Mon, 13 Jun 2022 10:18:39 +0200	[thread overview]
Message-ID: <Yqby31VCjuZj4OUa@wildebeest.org> (raw)
In-Reply-To: <20220613081348.197C73853540@sourceware.org>

Hi Jan,

On Mon, Jun 13, 2022 at 08:13:48AM +0000, builder--- via Binutils wrote:
> A new failure has been detected on builder binutils-debian-amd64 while building binutils-gdb.
> 
> Full details are available at:
>     https://builder.sourceware.org/buildbot/#builders/68/builds/194
> 
> Build state: failed compile (failure)
> Revision: 384e201e5aec29412a18b8386aa0a1ab6743e6cb
> Worker: bb2
> Build Reason: (unknown)
> Blamelist: Jan Beulich <jbeulich@suse.com>
> 
> Steps:
> 
> - 0: worker_preparation ( success )
> 
> - 1: git checkout ( success )
>     Logs:
>         - stdio: https://builder.sourceware.org/buildbot/#builders/68/builds/194/steps/1/logs/stdio
> 
> - 2: rm -rf binutils-build ( success )
>     Logs:
>         - stdio: https://builder.sourceware.org/buildbot/#builders/68/builds/194/steps/2/logs/stdio
> 
> - 3: configure ( success )
>     Logs:
>         - stdio: https://builder.sourceware.org/buildbot/#builders/68/builds/194/steps/3/logs/stdio
> 
> - 4: make ( failure )
>     Logs:
>         - stdio: https://builder.sourceware.org/buildbot/#builders/68/builds/194/steps/4/logs/stdio
>         - warnings (7): https://builder.sourceware.org/buildbot/#builders/68/builds/194/steps/4/logs/warnings__7_

Looks like this failed on builder that do --enable-target=all with:

../../binutils-gdb/opcodes/i386-dis.c: In function ‘print_insn’:
../../binutils-gdb/opcodes/i386-dis.c:9827:13: error: invalid type argument of ‘->’ (have ‘instr_info’)
 9827 |     if (*ins->op_out[i] != '\0')
      |             ^~

Cheers,

Mark


  reply	other threads:[~2022-06-13  8:18 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-13  8:13 builder
2022-06-13  8:18 ` Mark Wielaard [this message]
2022-06-13  9:08   ` Jan Beulich
  -- strict thread matches above, loose matches on Subject: below --
2023-01-09 23:57 builder
2023-01-09 23:46 builder
2022-12-16 12:24 builder
2022-12-12  9:54 builder
2022-12-07  4:25 builder
2022-12-05  0:18 builder
2022-11-30 16:24 builder
2022-11-30 16:21 builder
2022-11-11  6:30 builder
2022-11-01  9:58 builder
2022-10-31 13:36 builder
2022-10-19  9:14 builder
2022-07-08 10:24 builder
2022-06-27 11:11 builder
2022-06-21 10:32 builder
2022-06-21 16:40 ` Mark Wielaard
2022-06-09  0:20 builder
     [not found] ` <CAG_eJLfRrgsK62e7UX_HF7p5O+czBnTm6z+8K=KnDsasadkp5Q@mail.gmail.com>
2022-06-09  3:36   ` Mark Wielaard
2022-06-02 11:05 builder

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=Yqby31VCjuZj4OUa@wildebeest.org \
    --to=mark@klomp.org \
    --cc=binutils@sourceware.org \
    --cc=jbeulich@suse.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).