Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Nick Alcock <nick.alcock@oracle.com>
To: gdb-buildbot@sergiodj.net
Cc: gdb-patches@sourceware.org, binutils@sourceware.org
Subject: Re: Breakage on builder Fedora-x86_64-w64-mingw32, revision 0e65dfbaf3a0299e4837216a103c28625d4b4f1d
Date: Thu, 30 May 2019 00:13:00 -0000	[thread overview]
Message-ID: <87v9xs3il1.fsf@esperi.org.uk> (raw)
In-Reply-To: <E1hW82c-0006W9-LS@kwanyin.sergiodj.net>	(gdb-buildbot@sergiodj.net's message of "Wed, 29 May 2019 19:31:30	-0400")

On 30 May 2019, gdb-buildbot@sergiodj.net said:

> Unfortunately it seems that there is a breakage on GDB.
>
> Commit title: 'libctf: build system'
> Revision: 0e65dfbaf3a0299e4837216a103c28625d4b4f1d
>
> You can find more details below:
>
> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>
> Buildslave:
> 	fedora-x86-64-3
>
> Full Build URL:
> 	<http://gdb-build.sergiodj.net/builders/Fedora-x86_64-w64-mingw32/builds/4453>

This is

In file included from ../../binutils-gdb/libctf/ctf-dump.c:20:
../../binutils-gdb/libctf/ctf-impl.h:24:10: fatal error: sys/errno.h: No such file or directory
 #include <sys/errno.h>
          ^~~~~~~~~~~~~
compilation terminated.
make[3]: *** [Makefile:403: ctf-dump.o] Error 1
make[3]: *** Waiting for unfinished jobs....

i.e. the same report as earlier today on Solaris.

This, along with a number of other portability problems, is fixed by the
patch I just sent to Kamil in <87d0k13pf4.fsf@esperi.org.uk>. Once Jose
is around, I'll get him to look it over and see about pushing it.

Anyone else who wants to review it in the meantime, do go ahead (but I'm
afraid there are changelog diffs in there because it's in immediately-
ready-to-push state). If someone with suitable permissions thinks it is
acceptable in its current state, they are welcome to apply it straight
off the list, as far as I'm concerned :) anything to unbreak the build!

Archive link: <https://sourceware.org/ml/binutils/2019-05/msg00435.html>.

Sorry about this!


      reply	other threads:[~2019-05-30  0:13 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-29  0:02 Oh dear. I regret to inform you that commit 0e65dfbaf3a0299e4837216a103c28625d4b4f1d might be unfortunate 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 ` Oh dear. I regret to inform you that commit 0e65dfbaf3a0299e4837216a103c28625d4b4f1d might be unfortunate Simon Marchi
2019-05-29 10:21   ` 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 [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=87v9xs3il1.fsf@esperi.org.uk \
    --to=nick.alcock@oracle.com \
    --cc=binutils@sourceware.org \
    --cc=gdb-buildbot@sergiodj.net \
    --cc=gdb-patches@sourceware.org \
    /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