From: Sergio Durigan Junior <sergiodj@redhat.com>
To: Alan Hayward <Alan.Hayward@arm.com>
Cc: "gdb-patches\@sourceware.org" <gdb-patches@sourceware.org>,
nd <nd@arm.com>
Subject: Re: Oh dear. I regret to inform you that commit b5884fa7101cc528f07fd57c3de445a3680964a6 might be unfortunate
Date: Tue, 25 Sep 2018 13:07:00 -0000 [thread overview]
Message-ID: <87lg7pohcw.fsf@redhat.com> (raw)
In-Reply-To: <96501099-B076-4F95-96D9-1514701DD0B4@arm.com> (Alan Hayward's message of "Mon, 19 Feb 2018 11:43:44 +0000")
On Monday, February 19 2018, Alan Hayward wrote:
>> On 19 Feb 2018, at 10:07, 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:
>>
>> Add common/ dir in build directories
>> b5884fa7101cc528f07fd57c3de445a3680964a6
>>
>> 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.
>
> Sadly, when I try the builds with the exact same configure line, my build works!
>
> make[4]: *** No rule to make target `../../../binutils-gdb/gdb/gdbserver/common/btrace-common.c'. Stop.
>
> Looks like make is picking up the wrong rule for the common dir - it’s trying to compile from inside gdbserver.
> I think this is an issue with different versions of make working differently. Sigh. I’ll force my make version and debug.
This is probably because of a whitespace issue in the configure flags.
This has now been fixed in the BuildBot. Sorry about the noise.
--
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:[~2018-09-25 13:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-19 10:07 gdb-buildbot
2018-02-19 10:28 ` Breakage on builder Ubuntu-AArch32-native-gdbserver-m32, revision b5884fa7101cc528f07fd57c3de445a3680964a6 gdb-buildbot
2018-02-19 10:59 ` Breakage on builder Ubuntu-AArch32-m32, " gdb-buildbot
2018-02-19 11:43 ` Oh dear. I regret to inform you that commit b5884fa7101cc528f07fd57c3de445a3680964a6 might be unfortunate Alan Hayward
2018-09-25 13:07 ` Sergio Durigan Junior [this message]
2018-03-02 0:34 ` Breakage on builder Ubuntu-AArch64-native-gdbserver-m64, revision b5884fa7101cc528f07fd57c3de445a3680964a6 gdb-buildbot
2018-03-02 10:10 ` Alan Hayward
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=87lg7pohcw.fsf@redhat.com \
--to=sergiodj@redhat.com \
--cc=Alan.Hayward@arm.com \
--cc=gdb-patches@sourceware.org \
--cc=nd@arm.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