All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Parallel top-level make and multiple rootfs types
Date: Sat, 4 Nov 2017 23:05:58 +0100	[thread overview]
Message-ID: <20171104230558.4e785082@windsurf> (raw)
In-Reply-To: <32f8ab99-e828-f276-fc5a-61f9955db8cc@mind.be>

Hello,

On Sat, 4 Nov 2017 21:56:58 +0100, Arnout Vandecappelle wrote:

> > can I disable parallel execution of the rootfs-* build steps while still
> > building everything up to target-finalize in parallel?  
> 
>  No, that's not possible with make. I don't know if Thomas has already thought
> about this aspect of top-level parallel...

No, I haven't thought about this aspect of top-level parallel build.

>  I think the solution is to change the way we build the rootfs: instead of doing
> the fakeroot steps over and over again, do it once, save with the -s option, and
> then do the individual filesystems in a separate (readonly) fakeroot with -i to
> read the previously created fakeroot file.

I think Yann did some work in terms of parallel generation of
filesystem images, but I'm not sure exactly what he did :)

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com

  reply	other threads:[~2017-11-04 22:05 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-25 23:10 [Buildroot] Parallel top-level make and multiple rootfs types Jan Kundrát
2017-11-02 18:27 ` Jan Kundrát
2017-11-04 20:56   ` Arnout Vandecappelle
2017-11-04 22:05     ` Thomas Petazzoni [this message]
2017-11-05  8:41       ` Yann E. MORIN

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=20171104230558.4e785082@windsurf \
    --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.