From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2 1/3] package/erlang: bump to version 22.2
Date: Wed, 5 Feb 2020 10:37:39 +0100 [thread overview]
Message-ID: <20200205103739.62be0ec6@windsurf> (raw)
In-Reply-To: <20200204100733.22106-1-frank.vanbever@essensium.com>
Hello Frank,
Thanks for the new iteration. However, one question remains. See below.
On Tue, 4 Feb 2020 11:07:31 +0100
Frank Vanbever <frank.vanbever@essensium.com> wrote:
> # Patched erts/aclocal.m4
> -ERLANG_AUTORECONF = YES
> +define ERLANG_RUN_AUTOCONF
> + cd $(@D) && PATH=$(BR_PATH) ./otp_build autoconf
> +endef
> +HOST_ERLANG_DEPENDENCIES = host-autoconf
> +ERLANG_PRE_CONFIGURE_HOOKS += ERLANG_RUN_AUTOCONF
> +
> +define ERLANG_RUN_SAVE_BOOTSTRAP
> + cd $(@D) && PATH=$(BR_PATH) ./otp_build save_bootstrap
> +endef
Why is this save_bootstrap now needed ? Looking at HOWTO/INSTALL.md in
the Erlang source code shows:
"""
#### Pre-built Source Release ####
The source release is delivered with a lot of platform independent
build results already pre-built. If you want to remove these pre-built
files, invoke `./otp_build remove_prebuilt_files` from the `$ERL_TOP`
directory. After you have done this, you can build exactly the same way
as before, but the build process will take a much longer time.
> *WARNING*: Doing `make clean` in an arbitrary directory of the source
> tree, may remove files needed for bootstrapping the build.
>
> Doing `./otp_build save_bootstrap` from the `$ERL_TOP` directory before
> doing `make clean` will ensure that it will be possible to build after
> doing `make clean`. `./otp_build save_bootstrap` will be invoked
> automatically when `make` is invoked from `$ERL_TOP` with either the
> `clean` target, or the default target. It is also automatically invoked
> if `./otp_build remove_prebuilt_files` is invoked.
>
> If you need to verify the bootstrap beam files match the provided
> source files, use `./otp_build update_primary` to create a new commit that
> contains differences, if any exist.
"""
Which doesn't really help in understanding why we need to call this
save_bootstrap action in the context of Buildroot. It definitely
warrants an explanation in the commit log and a small comment above the
code. No need to resend a new iteration of the entire patch series,
just give some more details by e-mail, I can amend the patch when
applying.
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2020-02-05 9:37 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 ` Thomas Petazzoni [this message]
2020-02-05 11:15 ` [Buildroot] [PATCH v2 1/3] package/erlang: bump to version 22.2 Frank Vanbever
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=20200205103739.62be0ec6@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox