From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] erlang: bump to version 20.0
Date: Fri, 1 Dec 2017 09:20:28 +0100 [thread overview]
Message-ID: <20171201092028.6ebf91b6@windsurf.lan> (raw)
In-Reply-To: <CA+-urNSgFcRjQz1pce9iG-7dxw0_BLC5M1Jt6cvLamqfarstGw@mail.gmail.com>
Hello,
On Thu, 30 Nov 2017 11:31:53 -0500, Frank Hunleth wrote:
> On Thu, Nov 30, 2017 at 10:42 AM, Johan Oudinet <johan.oudinet@gmail.com> 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
>
> Thanks for doing this. I had been holding on to a nearly identical
> patch, but it breaks several erlang packages currently in Buildroot.
What are those packages ?
> It didn't look easy to fix, and then I got busy. As I'm sure that
> you're aware, ejabberd builds fine. I don't think there are many of us
> Erlang/Buildroot users, so if this still breaks erlang packages that
> you don't use, I'm fine with removing them.
We definitely need to at least identify those packages. Is this a build
time breakage ? Run-time breakage ?
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2017-12-01 8:20 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 [this message]
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
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=20171201092028.6ebf91b6@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 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.