From: iyzsong@member.fsf.org (宋文武)
To: Andreas Enge <andreas@enge.fr>
Cc: guix-devel@gnu.org
Subject: Re: Qt-5 in core-updates
Date: Mon, 25 Jan 2016 09:57:13 +0800 [thread overview]
Message-ID: <87twm2ctfq.fsf@member.fsf.org> (raw)
In-Reply-To: <20160124191925.GA4264@debian> (Andreas Enge's message of "Sun, 24 Jan 2016 20:19:25 +0100")
Andreas Enge <andreas@enge.fr> writes:
> Hello,
>
> qt-5 fails to build on both x86_64 and armhf in core-updates with the
> following error:
> Traceback (most recent call last):
> File "/tmp/nix-build-qt-5.5.1.drv-0/qt-everywhere-opensource-src-5.5.1/qtwebkit/Source/WebKit2/Scripts/generate-messages-header.py", line 28, in <module>
> import webkit2.messages
> EOFError: EOF read where object expected
> Makefile.WebKit2.DerivedSources:881: recipe for target 'generated/PluginProxyMessages.h' failed
> make[3]: *** [generated/PluginProxyMessages.h] Error 1
>
> Surprisingly, it succeeds on i686 (and its build is disabled on mips).
>
This seems like a parallel build issue after I find that,
Writing a pyc file is not atomic in python:
<https://bugs.python.org/issue13146>
It was fixed in Python 3.3+, but not in Python 2.7.x (the one for
building WebKit).
I think we can try:
- Patch our python-2.7.x like Ubuntu does.
<https://launchpad.net/ubuntu/+archive/primary/+files/python2.7_2.7.10-4ubuntu1.diff.gz>
- Patch the build phases of qt and webkitgtk to pre-generate *.pyc
files before the actually building.
Or disable parallel build completely.
- Restart the builds on hydra, hope it will pass.
next prev parent reply other threads:[~2016-01-25 1:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-24 19:19 Qt-5 in core-updates Andreas Enge
2016-01-24 23:34 ` Andreas Enge
2016-01-25 1:57 ` 宋文武 [this message]
2016-01-25 9:25 ` Ludovic Courtès
2016-01-25 18:04 ` Andreas Enge
2016-01-26 2:23 ` 宋文武
2016-01-27 10:38 ` Andreas Enge
2016-02-02 16:47 ` Andreas Enge
2016-03-17 21:47 ` Andreas Enge
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=87twm2ctfq.fsf@member.fsf.org \
--to=iyzsong@member.fsf.org \
--cc=andreas@enge.fr \
--cc=guix-devel@gnu.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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.