From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [autobuild.buildroot.net] Build results for 2016-05-13
Date: Sun, 15 May 2016 21:47:53 +0200 [thread overview]
Message-ID: <20160515214753.67974bf6@free-electrons.com> (raw)
In-Reply-To: <20160514145905.GA3877@free.fr>
Hello,
On Sat, 14 May 2016 16:59:05 +0200, Yann E. MORIN wrote:
> I'm not sure my machine is the only one to have the issue. There are
> very similar issues building host-python3:
Gaah, indeed :-/
Python is a big and widely used package, it's a bit annoying to disable
parallel build for it. But I guess it's the best we can do right now,
unless you have an idea to fix the problem (but parallel build issues
are often complex to understand, especially in a convoluted build
system like the one of Python...).
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2016-05-15 19:47 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-14 6:30 [Buildroot] [autobuild.buildroot.net] Build results for 2016-05-13 Thomas Petazzoni
2016-05-14 13:46 ` Thomas Petazzoni
2016-05-14 14:11 ` Peter Korsgaard
2016-05-14 14:19 ` Thomas Petazzoni
2016-05-14 14:59 ` Yann E. MORIN
2016-05-14 16:02 ` Yann E. MORIN
2016-05-15 19:55 ` Thomas Petazzoni
2016-05-15 20:03 ` Yann E. MORIN
2016-05-15 19:47 ` Thomas Petazzoni [this message]
2016-05-14 15:02 ` Gustavo Zacarias
2016-05-15 19:53 ` Thomas Petazzoni
2016-05-16 4:29 ` Baruch Siach
2016-05-15 18:21 ` Jörg Krause
2016-05-15 21:43 ` Matthew Weber
2016-05-16 6:47 ` Thomas Petazzoni
2016-05-16 10:19 ` Martin Bark
2016-05-16 11:15 ` Thomas Petazzoni
2016-05-16 12:23 ` Martin Bark
2016-05-16 12:50 ` Thomas Petazzoni
2016-05-16 14:34 ` Martin Bark
2016-05-16 14:43 ` Thomas Petazzoni
2016-05-16 15:01 ` Martin Bark
2016-05-23 20:19 ` Romain Naour
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=20160515214753.67974bf6@free-electrons.com \
--to=thomas.petazzoni@free-electrons.com \
--cc=buildroot@busybox.net \
/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 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.