From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] Trouble with offline build
Date: Wed, 28 Feb 2018 09:29:40 +0100 [thread overview]
Message-ID: <87a7vtldor.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20180228075533.564a23b7@windsurf.home> (Thomas Petazzoni's message of "Wed, 28 Feb 2018 07:55:33 +0100")
>>>>> "Thomas" == Thomas Petazzoni <thomas.petazzoni@bootlin.com> writes:
Hi,
> To be honest, I don't really see how to solve that problem. the
> host-{cmake,lzip,xzcat,tar} issue could probably be solved by
> downloading all of them even if some of them won't be needed (we may
> have a "make all-source" that differs from "make source" to avoid "make
> source" from downloading useless stuff). However, for the host
> architecture difference, I'm not sure how to proceed, and I'm not sure
> there is a reasonable solution.
> Bottom line: should we document/make it clear that doing a "make
> source" on machine A and then do a build on machine B is not
> guaranteeing a fully offline build ? It's a bit of a pity, because I
> know there are some environment where only a given machine has Internet
> access, and the developer machines don't, but I don't see a good way of
> solving this in Buildroot.
Me neither. Historically, make source was meant to ensure that
everything is downloaded now so you could go offline and continue
building _ON_THE_SAME_MACHINE_. This potentially does indeed break down
if you try to reuse the download directory on another machine, but I
don't quite see how we can solve this for all situations.
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2018-02-28 8:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-27 23:34 [Buildroot] Trouble with offline build A
2018-02-28 4:53 ` Baruch Siach
2018-02-28 6:55 ` Thomas Petazzoni
2018-02-28 8:29 ` Peter Korsgaard [this message]
2018-03-01 19:30 ` Yann E. MORIN
2018-02-28 4:57 ` Bernd Kuhls
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=87a7vtldor.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.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