public inbox for gdbadmin@sourceware.org
help / color / mirror / Atom feed
From: Andrew Burgess <aburgess@redhat.com>
To: builder@sourceware.org,
	GDB Administrator <gdbadmin@sourceware.org>,
	Tom Tromey <tom@tromey.com>
Subject: Re: ☠ Buildbot (GNU Toolchain): binutils-gdb - failed compile (failure) (master)
Date: Thu, 09 Jun 2022 10:32:23 +0100	[thread overview]
Message-ID: <87v8tafahk.fsf@redhat.com> (raw)
In-Reply-To: <20220609002024.1CE913856273@sourceware.org>

builder@sourceware.org writes:

> A new failure has been detected on builder binutils-fedora-x86_64 while building binutils-gdb.
>
> Full details are available at:
>     https://builder.sourceware.org/buildbot/#builders/77/builds/173
>
> Build state: failed compile (failure)
> Revision: d21691eaa7e851a7600ce1f616c5289b7c69055b
> Worker: bb3
> Build Reason: (unknown)
> Blamelist: Andrew Burgess <aburgess@redhat.com>, GDB Administrator <gdbadmin@sourceware.org>, Tom Tromey <tom@tromey.com>
>
> Steps:
>
> - 0: worker_preparation ( success )
>
> - 1: git checkout ( success )
>     Logs:
>         - stdio: https://builder.sourceware.org/buildbot/#builders/77/builds/173/steps/1/logs/stdio
>
> - 2: rm -rf binutils-build ( success )
>     Logs:
>         - stdio: https://builder.sourceware.org/buildbot/#builders/77/builds/173/steps/2/logs/stdio
>
> - 3: configure ( success )
>     Logs:
>         - stdio: https://builder.sourceware.org/buildbot/#builders/77/builds/173/steps/3/logs/stdio
>
> - 4: make ( failure )
>     Logs:
>         - stdio: https://builder.sourceware.org/buildbot/#builders/77/builds/173/steps/4/logs/stdio
>         - warnings (8): https://builder.sourceware.org/buildbot/#builders/77/builds/173/steps/4/logs/warnings__8_

I took a look through the build log and the only obvious error I could
see was this one:

  /home/builder/shared/fedora-latest/worker/binutils-fedora-x86_64/binutils-gdb/missing: line 81: makeinfo: command not found
  WARNING: 'makeinfo' is missing on your system.
           You should only need it if you modified a '.texi' file, or
           any other file indirectly affecting the aspect of the manual.
           You might want to install the Texinfo package:
           <http://www.gnu.org/software/texinfo/>
           The spurious makeinfo call might also be the consequence of
           using a buggy 'make' (AIX, DU, IRIX), in which case you might
           want to install GNU make:
           <http://www.gnu.org/software/make/>
  make[2]: *** [Makefile:1778: doc/bfd.info] Error 127
  make[2]: Leaving directory '/home/builder/shared/fedora-latest/worker/binutils-fedora-x86_64/binutils-build/bfd'
  make[1]: *** [Makefile:1938: info-recursive] Error 1
  make[1]: Leaving directory '/home/builder/shared/fedora-latest/worker/binutils-fedora-x86_64/binutils-build/bfd'
  make: *** [Makefile:3060: all-bfd] Error 2
  make: *** Waiting for unfinished jobs....

It appears that this builder doesn't have makeinfo installed.

Thanks,
Andrew



  reply	other threads:[~2022-06-09  9:32 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-09  0:20 builder
2022-06-09  9:32 ` Andrew Burgess [this message]
2022-06-09 10:00   ` Mark Wielaard
2022-06-09  0:26 builder
2022-10-19  0:24 builder
2022-12-05  0:18 builder
2023-01-13 22:26 builder
2023-01-15 23:45 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=87v8tafahk.fsf@redhat.com \
    --to=aburgess@redhat.com \
    --cc=builder@sourceware.org \
    --cc=gdbadmin@sourceware.org \
    --cc=tom@tromey.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).