From: Frank Vanbever <frank.vanbever@essensium.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2 1/3] package/erlang: bump to version 22.2
Date: Wed, 05 Feb 2020 12:15:19 +0100 [thread overview]
Message-ID: <2231542.ug6IuTeUKT@wintermute> (raw)
In-Reply-To: <20200205103739.62be0ec6@windsurf>
Hello Thomas,
On Wednesday, 5 February 2020 10:37:39 CET Thomas Petazzoni wrote:
> Why is this save_bootstrap now needed ?
During development I encountered build failures due to the following file not
being present:
otp_src_22.2/bootstrap/lib/kernel/include/logger.hrl
The save_bootstrap command creates this file.
I attempted to reproduce this build failure today and I am unable to do so.
Likely the behaviour I saw was an artifact of some manipulation I did to fix
the build rather than inherent to Erlang itself.
AFAICT all lines related to ERLANG_RUN_SAVE_BOOTSTRAP can be removed as they
serve no purpose. This is as you mention also supported by the Erlang
documentation.
Given that it's removing code is this still something you can amend during the
merge or do you want me to resubmit the patches?
Br,
Frank
next prev parent reply other threads:[~2020-02-05 11:15 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-29 17:26 [Buildroot] [PATCH 1/3] package/erlang: bump to version 22.2 Frank Vanbever
2020-01-29 17:26 ` [Buildroot] [PATCH 2/3] package/elixir: new package Frank Vanbever
2020-02-01 22:02 ` Thomas Petazzoni
2020-01-29 17:26 ` [Buildroot] [PATCH 3/3] package/rabbitmq-server: bump version to 3.8.2 Frank Vanbever
2020-02-01 21:59 ` Thomas Petazzoni
2020-02-01 21:57 ` [Buildroot] [PATCH 1/3] package/erlang: bump to version 22.2 Thomas Petazzoni
2020-02-04 10:07 ` [Buildroot] [PATCH v2 " Frank Vanbever
2020-02-04 10:07 ` [Buildroot] [PATCH v2 2/3] package/elixir: new package Frank Vanbever
2020-02-05 14:42 ` Thomas Petazzoni
2020-02-04 10:07 ` [Buildroot] [PATCH v2 3/3] package/rabbitmq-server: bump version to 3.8.2 Frank Vanbever
2020-02-05 14:47 ` Thomas Petazzoni
2020-02-13 15:14 ` [Buildroot] [PATCH v3 1/2] package/rabbitmq-server: clean up license list Frank Vanbever
2020-02-13 15:14 ` [Buildroot] [PATCH v3 2/2] package/rabbitmq-server: bump version to 3.8.2 Frank Vanbever
2020-04-12 19:33 ` Thomas Petazzoni
2020-04-12 19:33 ` [Buildroot] [PATCH v3 1/2] package/rabbitmq-server: clean up license list Thomas Petazzoni
2020-02-05 9:37 ` [Buildroot] [PATCH v2 1/3] package/erlang: bump to version 22.2 Thomas Petazzoni
2020-02-05 11:15 ` Frank Vanbever [this message]
2020-02-05 14:42 ` Thomas Petazzoni
2020-02-10 13:28 ` Johan Oudinet
2020-02-10 13:30 ` Thomas Petazzoni
2020-02-10 15:20 ` Johan Oudinet
2020-02-10 15:27 ` Johan Oudinet
2020-02-10 15:51 ` Johan Oudinet
2020-02-10 15:57 ` Thomas Petazzoni
2020-02-10 16:07 ` Johan Oudinet
2020-02-10 16:48 ` 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=2231542.ug6IuTeUKT@wintermute \
--to=frank.vanbever@essensium.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.