From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [autobuild.buildroot.net] Build results for 2018-08-20
Date: Tue, 21 Aug 2018 22:48:56 +0200 [thread overview]
Message-ID: <20180821224856.2bcb02a4@windsurf> (raw)
In-Reply-To: <20180821204549.GA26988@ned>
Hello,
On Tue, 21 Aug 2018 22:45:50 +0200, Eric Le Bihan wrote:
> 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].
This issue is already fixed:
https://git.buildroot.org/buildroot/commit/?h=next&id=eb9d0e38101d3f62096550e0a39dbd18932ccc87
Thanks,
Thomas
--
Thomas Petazzoni, CTO, Bootlin (formerly Free Electrons)
Embedded Linux and Kernel engineering
https://bootlin.com
prev parent reply other threads:[~2018-08-21 20:48 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
2018-08-21 20:48 ` Thomas Petazzoni [this message]
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=20180821224856.2bcb02a4@windsurf \
--to=thomas.petazzoni@bootlin.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.