From: Simon Marchi <simark@simark.ca>
To: gdb-buildbot@sergiodj.net, Nick Alcock <nick.alcock@oracle.com>,
gdb-patches@sourceware.org
Subject: Re: Oh dear. I regret to inform you that commit 0e65dfbaf3a0299e4837216a103c28625d4b4f1d might be unfortunate
Date: Wed, 29 May 2019 02:16:00 -0000 [thread overview]
Message-ID: <f7125ecf-6285-0143-2808-14c9efe932e0@simark.ca> (raw)
In-Reply-To: <0e65dfbaf3a0299e4837216a103c28625d4b4f1d-master-breakage@gdb-build>
On 2019-05-28 8:02 p.m., gdb-buildbot@sergiodj.net wrote:
> My lords, ladies, gentlemen, members of the public.
>
> It is a matter of great regret and sadness to inform you that commit:
>
> libctf: build system
> 0e65dfbaf3a0299e4837216a103c28625d4b4f1d
>
> might have made GDB unwell. Since I am just your Butler BuildBot,
> I kindly ask that a human superior officer double-check this.
>
> Please note that if you are reading this message on gdb-patches, there might
> be other builders broken.
>
> You can find more details about the unfortunate breakage in the next messages.
>
> Cheers,
>
> Your GDB BuildBot.
>
In case you have trouble spotting the error, I believe it is
../../binutils-gdb/libctf/ctf-archive.c:24:10: fatal error: endian.h: No such file or directory
#include <endian.h>
^~~~~~~~~~
which you can find if you follow one of the "Full build" URLs in the other messages.
Simon
next prev parent reply other threads:[~2019-05-29 2:16 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-29 0:02 gdb-buildbot
2019-05-29 0:02 ` Breakage on builder Solaris11-sparcv9-m64, revision 0e65dfbaf3a0299e4837216a103c28625d4b4f1d gdb-buildbot
2019-05-29 1:34 ` Breakage on builder Solaris11-amd64-m64, " gdb-buildbot
2019-05-29 2:16 ` Simon Marchi [this message]
2019-05-29 10:21 ` Oh dear. I regret to inform you that commit 0e65dfbaf3a0299e4837216a103c28625d4b4f1d might be unfortunate Rainer Orth
2019-05-29 12:46 ` Nix
2019-05-29 13:14 ` Andreas Schwab
2019-05-29 13:38 ` Rainer Orth
2019-05-29 14:18 ` Nick Alcock
2019-05-29 16:33 ` [PATCH] Fix a number of build problems found on Solaris and NetBSD (was Re: Oh dear. I regret to inform you that commit 0e65dfbaf3a0299e4837216a103c28625d4b4f1d might be unfortunate) Nick Alcock
2019-05-29 18:22 ` Rainer Orth
2019-05-29 20:08 ` Nick Alcock
2019-05-29 20:34 ` Kamil Rytarowski
2019-05-29 21:46 ` Nick Alcock
2019-05-30 0:54 ` Sergio Durigan Junior
2019-05-30 7:14 ` Kamil Rytarowski
2019-05-30 9:35 ` Nick Alcock
2019-05-29 16:04 ` Oh dear. I regret to inform you that commit 0e65dfbaf3a0299e4837216a103c28625d4b4f1d might be unfortunate Nick Alcock
2019-05-29 4:26 ` Breakage on builder NetBSD-x86_64-m64, revision 0e65dfbaf3a0299e4837216a103c28625d4b4f1d gdb-buildbot
2019-05-29 5:51 ` Kamil Rytarowski
2019-05-29 12:51 ` Nick Alcock
2019-05-29 23:31 ` Breakage on builder Fedora-x86_64-w64-mingw32, " gdb-buildbot
2019-05-30 0:13 ` Nick Alcock
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=f7125ecf-6285-0143-2808-14c9efe932e0@simark.ca \
--to=simark@simark.ca \
--cc=gdb-buildbot@sergiodj.net \
--cc=gdb-patches@sourceware.org \
--cc=nick.alcock@oracle.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