From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] tar: add Config.in.host
Date: Sat, 16 Feb 2019 14:32:07 +0100 [thread overview]
Message-ID: <20190216143207.65930f15@windsurf.home> (raw)
In-Reply-To: <20190215232006.4990-1-mmayer@broadcom.com>
Hello Markus,
On Fri, 15 Feb 2019 15:20:06 -0800
Markus Mayer <mmayer@broadcom.com> wrote:
> Add a config option to build tar for the host, so the user can choose
> to build it, even if Buildroot wouldn't do so ordinarily.
>
> Signed-off-by: Markus Mayer <mmayer@broadcom.com>
> ---
>
> Since Buildroot can only work with three tar version (1.27-1.29), the
> likelihood that system tar is too old or too new is quite high -- and
> increasing. Ubuntu 16.04 and 18.04 ship with an acceptabe version of
> tar. As of Ubuntu 18.10, system tar is already too recent.
>
> Our main build machines are Ubuntu 16.04, but we need to support other
> platforms. We need build machines of different flavours to be able to
> build buildroot without requiring an Internet connection, using only
> pre-downloaded package tar-balls (downloaded during the master build).
>
> We can't rely that the tar sources have been downloaded automatically
> based on what was detected on the master build machine, because it may
> not require host-tar while a different build machine might.
>
> A manual config option will give us the choice to build and bundle
> host-tar regardless of what Buildroot finds on the master.
This use case is already solved by the option BR2_FORCE_HOST_BUILD,
introduced recently in commit 3f1b965bc36c64f83c962e373f7b5fe1245e3355,
with the exception that BR2_FORCE_HOST_BUILD solves the issue for all
host packages, not just for host-tar.
Best regards,
Thomas Petazzoni
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
prev parent reply other threads:[~2019-02-16 13:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-15 23:20 [Buildroot] [PATCH] tar: add Config.in.host Markus Mayer
2019-02-16 13:32 ` 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=20190216143207.65930f15@windsurf.home \
--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