From: Eric Le Bihan <eric.le.bihan.dev@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [autobuild.buildroot.net] Build results for 2018-08-20
Date: Tue, 21 Aug 2018 22:45:50 +0200 [thread overview]
Message-ID: <20180821204549.GA26988@ned> (raw)
In-Reply-To: <20180821060020.69804207B3@mail.bootlin.com>
Hi!
On 18-08-21 08:00:20, Thomas Petazzoni wrote:
>
> arm | host-meson-0.47.1 | NOK | http://autobuild.buildroot.net/results/636da0febe02f991095965d52cc4a8b2da644777 |
> powerpc | host-meson-0.47.1 | NOK | http://autobuild.buildroot.net/results/e6aa3d98203d3ac1788671bda3041b2563e5a411 |
> arm | host-meson-0.47.1 | NOK | http://autobuild.buildroot.net/results/af709ccc027b0a9bea0228001572084c19d4c710 |
> arm | host-meson-0.47.1 | NOK | http://autobuild.buildroot.net/results/12af6e626c1ad4b5c9f4c612b64027213923c4d7 |
> nios2 | host-meson-0.47.1 | NOK | http://autobuild.buildroot.net/results/9b837f60cbd15e2a3c11e3453e543ca27ec28498 |
> arc | host-meson-0.47.1 | NOK | http://autobuild.buildroot.net/results/78f4ec7d8bbb94aa5ea1bcc91a56aad664ab8835 |
> i686 | host-meson-0.47.1 | NOK | http://autobuild.buildroot.net/results/ded8c3a72e97c6e7481062ff601f1f03adab6976 |
This looks like an issue with setuptools and Python 3.7, as reported
here [1].
From [2], setuptools v38.4.0 is used, the latest is v40.2.0, but v38.4.1
should do the trick [3,4].
[1] https://github.com/pypa/setuptools/issues/1257
[2] http://autobuild.buildroot.net/results/636da0febe02f991095965d52cc4a8b2da644777/build-end.log
[3] https://github.com/pypa/setuptools/pull/1263
[4] https://github.com/pypa/setuptools/compare/v38.4.0...v38.4.1
Regards,
--
ELB
next prev parent reply other threads:[~2018-08-21 20:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-21 6:00 [Buildroot] [autobuild.buildroot.net] Build results for 2018-08-20 Thomas Petazzoni
2018-08-21 20:45 ` Eric Le Bihan [this message]
2018-08-21 20:48 ` Thomas Petazzoni
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=20180821204549.GA26988@ned \
--to=eric.le.bihan.dev@free.fr \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox