public inbox for gdbadmin@sourceware.org
help / color / mirror / Atom feed
From: Mark Wielaard <mark@klomp.org>
To: Andrew Burgess <aburgess@redhat.com>
Cc: GDB Administrator <gdbadmin@sourceware.org>, Tom Tromey <tom@tromey.com>
Subject: Re: ☠ Buildbot (GNU Toolchain): binutils-gdb - failed compile (failure) (master)
Date: Thu, 9 Jun 2022 12:00:34 +0200	[thread overview]
Message-ID: <YqHEwuGXmQy824AY@wildebeest.org> (raw)
In-Reply-To: <87v8tafahk.fsf@redhat.com>

Hi Andrew,

On Thu, Jun 09, 2022 at 10:32:23AM +0100, Andrew Burgess wrote:
>   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.

Yes, appologies, that has now been corrected:
https://sourceware.org/pipermail/buildbot/2022q2/000026.html

Cheers,

Mark


  reply	other threads:[~2022-06-09 10:00 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
2022-06-09 10:00   ` Mark Wielaard [this message]
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=YqHEwuGXmQy824AY@wildebeest.org \
    --to=mark@klomp.org \
    --cc=aburgess@redhat.com \
    --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).