From: Pedro Alves <palves@redhat.com>
To: "Wiederhake, Tim" <tim.wiederhake@intel.com>,
Sergio Durigan Junior <sergiodj@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 11:21:00 -0000 [thread overview]
Message-ID: <c9892053-ba73-7173-c871-cd56db02b6f9@redhat.com> (raw)
In-Reply-To: <c893891b-7e4a-58c5-da17-b7baf73a2b9f@redhat.com>
On 07/13/2018 12:16 PM, Pedro Alves wrote:
> On 07/13/2018 11:55 AM, Wiederhake, Tim wrote:
>>> To: Pedro Alves <palves@redhat.com>
>>>
>>> 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.
>
> My guess is that for some reason GNU Make thinks it
> needs to rebuild plural.c from src/intl/plural.y instead of
> using the in-source-tree src/intl/plural.c, and then we run into some
> incompatibility between gettext and bison (or rather,
> the newer-bison-produced file). Network shares are prone to
> time skew, >1s differences, etc. confusing make.
>
> Oh, hmm, I've been building my mingw cross gdbs with --disable-intl.
> If I remove that, then I see that same error too.
>
> Yep, if I
> touch src/intl/plural.c
> then
> rm -f build/intl/plural.* && make -C intl
> build successfully.
>
> I kind of have the feeling I've seen this discussed before.
Found <https://sourceware.org/ml/binutils/2014-12/msg00107.html>.
Looks like there's an intl fix, but nobody ever imported it into
our copy (starting with updating gcc's copy).
Anyone want to take a stab at it?
Thanks,
Pedro Alves
next prev parent reply other threads:[~2018-07-13 11:21 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
2018-07-13 11:16 ` Pedro Alves
2018-07-13 11:21 ` Pedro Alves [this message]
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=c9892053-ba73-7173-c871-cd56db02b6f9@redhat.com \
--to=palves@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=sergiodj@redhat.com \
--cc=tim.wiederhake@intel.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