From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] erlang: bump to version 20.0
Date: Sun, 3 Dec 2017 10:59:05 +0100 [thread overview]
Message-ID: <20171203105905.3bdd1dc9@windsurf.lan> (raw)
In-Reply-To: <20171130154202.437-1-johan.oudinet@gmail.com>
Hello,
On Thu, 30 Nov 2017 16:42:02 +0100, Johan Oudinet wrote:
> This change bumps the Erlang version from 19.3 to 20.0. As a new major
> release, there are a few incompatibilities. Details are here:
> http://www.erlang.org/news/114
>
> This should fix builds on ppc64le host machines:
> http://autobuild.buildroot.net/results/407af9800313d4540643d7625e85acc0c2366892
> http://autobuild.buildroot.net/results/2aca54ad48ecfd72242d97499e21a46c1b384b10
>
> Signed-off-by: Johan Oudinet <johan.oudinet@gmail.com>
> ---
> package/erlang/erlang.hash | 4 ++--
> package/erlang/erlang.mk | 4 ++--
> 2 files changed, 4 insertions(+), 4 deletions(-)
This causes a bunch of build failures:
http://autobuild.buildroot.net/?reason=host-erlang-20.0
Seems like host-zlib is needed.
Could you have a look ?
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2017-12-03 9:59 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-30 15:42 [Buildroot] [PATCH 1/1] erlang: bump to version 20.0 Johan Oudinet
2017-11-30 16:31 ` Frank Hunleth
2017-12-01 8:20 ` Thomas Petazzoni
2017-12-01 15:16 ` Johan Oudinet
2017-12-01 15:43 ` Frank Hunleth
2017-12-01 21:46 ` Thomas Petazzoni
2017-12-03 9:59 ` Thomas Petazzoni [this message]
2017-12-04 16:32 ` Johan Oudinet
2017-12-05 19:34 ` Bernd Kuhls
2017-12-06 11:11 ` Johan Oudinet
2017-12-06 14:23 ` Thomas Petazzoni
2017-12-04 17:49 ` Bernd Kuhls
2017-12-05 16:52 ` Johan Oudinet
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=20171203105905.3bdd1dc9@windsurf.lan \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox