From: "Wiederhake, Tim" <tim.wiederhake@intel.com>
To: Sergio Durigan Junior <sergiodj@redhat.com>,
Pedro Alves <palves@redhat.com>
Cc: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: RE: Breakage on builder Fedora-x86_64-w64-mingw32, revision 49b000dc5686e016f05b717f18d2c8f865eb3617 [gdb-8.12-branch]
Date: Fri, 13 Jul 2018 10:55:00 -0000 [thread overview]
Message-ID: <9676A094AF46E14E8265E7A3F4CCE9AF7493FD29@irsmsx111.ger.corp.intel.com> (raw)
In-Reply-To: <874lh4pf8k.fsf@redhat.com>
Hi all,
> -----Original Message-----
> From: gdb-patches-owner@sourceware.org [mailto:gdb-patches-
> owner@sourceware.org] On Behalf Of Sergio Durigan Junior
> Sent: Thursday, July 12, 2018 6:54 PM
> To: Pedro Alves <palves@redhat.com>
> Cc: gdb-patches@sourceware.org
> Subject: Re: Breakage on builder Fedora-x86_64-w64-mingw32, revision
> 49b000dc5686e016f05b717f18d2c8f865eb3617 [gdb-8.12-branch]
>
> On Thursday, July 12 2018, Pedro Alves wrote:
>
> > On 07/12/2018 08:59 AM, gdb-buildbot@sergiodj.net wrote:
> >> yes
> >> checking for memcmp... In file included from ../../binutils-
> gdb/intl/plural.y:35:0:
> >> ../../binutils-gdb/intl/plural-exp.h:102:23: error: conflicting types
> for 'libintl_gettextparse'
> >> # define PLURAL_PARSE libintl_gettextparse
> >> ^
For what it's worth, we're seeing this, too, every now and then.
Up to now I believed this was just a problem with our setup, as I couldn't find any difference in the source or build directories of failing and working builds.
Additionally, cross-compiling gdb seems to increase the frequency of failures, as does having the source or build directory on a network share.
Tim
Intel Deutschland GmbH
Registered Address: Am Campeon 10-12, 85579 Neubiberg, Germany
Tel: +49 89 99 8853-0, www.intel.de
Managing Directors: Christin Eisenschmid, Christian Lamprechter
Chairperson of the Supervisory Board: Nicole Lau
Registered Office: Munich
Commercial Register: Amtsgericht Muenchen HRB 186928
next prev parent reply other threads:[~2018-07-13 10:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-12 7:59 Oh dear. I regret to inform you that commit 49b000dc5686e016f05b717f18d2c8f865eb3617 might be unfortunate [gdb-8.12-branch] gdb-buildbot
2018-07-12 7:59 ` Breakage on builder Fedora-x86_64-w64-mingw32, revision 49b000dc5686e016f05b717f18d2c8f865eb3617 [gdb-8.12-branch] gdb-buildbot
2018-07-12 16:21 ` Pedro Alves
2018-07-12 16:53 ` Sergio Durigan Junior
2018-07-13 10:55 ` Wiederhake, Tim [this message]
2018-07-13 11:16 ` Pedro Alves
2018-07-13 11:21 ` Pedro Alves
2018-07-20 20:40 ` Joseph Myers
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=9676A094AF46E14E8265E7A3F4CCE9AF7493FD29@irsmsx111.ger.corp.intel.com \
--to=tim.wiederhake@intel.com \
--cc=gdb-patches@sourceware.org \
--cc=palves@redhat.com \
--cc=sergiodj@redhat.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