From: Sergio Durigan Junior <sergiodj@redhat.com>
To: Pedro Alves <palves@redhat.com>
Cc: Simon Marchi <simon.marchi@ericsson.com>,
gdb-patches@sourceware.org,
Brendan Kirby <brendan.kirby@imgtec.com>
Subject: Re: [PATCH obv/pushed] MIPS ptrace build fixes
Date: Wed, 29 Jul 2015 22:32:00 -0000 [thread overview]
Message-ID: <871tfqegsx.fsf@redhat.com> (raw)
In-Reply-To: <55B94CD3.5080705@redhat.com> (Pedro Alves's message of "Wed, 29 Jul 2015 22:59:47 +0100")
On Wednesday, July 29 2015, Pedro Alves wrote:
> On 07/29/2015 10:26 PM, Simon Marchi wrote:
>> On 15-07-29 05:19 PM, Simon Marchi wrote:
>>> FYI, I am pushing this as obvious.
>>>
>>> Since Pedro's ptrace cleanups, the MIPS buildbot compilation fails.
>
> In my defense, I did get a build fail email report, but it points at:
>
> http://gdb-build.sergiodj.net/builders/Debian-MIPS-m64/builds/77
>
> and looking at:
>
> http://gdb-build.sergiodj.net/builders/Debian-MIPS-m64/builds/77/steps/compile%20gdb/logs/stdio
>
> it shows the build had failed for an unrelated issue:
>
> tdep.Tpo ../../binutils-gdb/gdb/i386obsd-tdep.c
> In file included from ../../binutils-gdb/gdb/common/common-defs.h:32:0,
> from ../../binutils-gdb/gdb/defs.h:28,
> from ../../binutils-gdb/gdb/i386obsd-tdep.c:20:
> build-gnulib/import/stdlib.h:41:20: fatal error: /usr/lib/gcc/mips-linux-gnu/4.9/include/ctddef.h: No such file or directory
> #include <stddef.h>
> ^
> compilation terminated.
> The bug is not reproducible, so it is likely a hardware or OS problem.
> make[2]: *** [i386obsd-tdep.o] Error 1
> Makefile:1133: recipe for target 'i386obsd-tdep.o' failed
>
> So I just ignored it. Guess I was "lucky".
FWIW, I've been noticing random errors in the MIPS buildslave. I even
spotted an ICE once (I think Alan Modra reported it to me). Not sure if
it is because of the load or something else.
Thanks,
--
Sergio
GPG key ID: 237A 54B1 0287 28BF 00EF 31F4 D0EB 7628 65FC 5E36
Please send encrypted e-mail if possible
http://sergiodj.net/
next prev parent reply other threads:[~2015-07-29 22:32 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-29 21:19 Simon Marchi
2015-07-29 21:26 ` Simon Marchi
2015-07-29 21:59 ` Pedro Alves
2015-07-29 22:32 ` Sergio Durigan Junior [this message]
2015-07-30 9:14 ` Peter Schauer
2015-08-24 14:48 ` Pedro Alves
2015-08-24 14:59 ` Peter Schauer
2015-08-24 15:03 ` Pedro Alves
2015-08-24 17:52 ` Brendan Kirby
2015-08-24 18:04 ` Pedro Alves
2015-08-24 18:10 ` Sergio Durigan Junior
2015-08-24 18:17 ` Pedro Alves
2015-08-24 18:20 ` Sergio Durigan Junior
2015-08-24 18:24 ` Sergio Durigan Junior
2015-08-24 18:30 ` Brendan Kirby
2015-08-24 18:05 ` Sergio Durigan Junior
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=871tfqegsx.fsf@redhat.com \
--to=sergiodj@redhat.com \
--cc=brendan.kirby@imgtec.com \
--cc=gdb-patches@sourceware.org \
--cc=palves@redhat.com \
--cc=simon.marchi@ericsson.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