From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] core: add rule to dump packages' build order
Date: Fri, 7 Apr 2017 12:43:14 +0200 [thread overview]
Message-ID: <20170407124314.660c3edc@free-electrons.com> (raw)
In-Reply-To: <fd9c07fd-2e86-ed73-2fd1-bfcf27522664@mind.be>
Hello,
On Fri, 7 Apr 2017 12:30:46 +0200, Arnout Vandecappelle wrote:
> > Well, I've been tracking build-order issues for a while last WE, and
> > believe me, I was very happy to be able to see the build order before
> > I attempted a build, yes.
>
> That's my biggest problem with this feature: I have no idea how to use it.
> Could you add some explanation somewhere?
Yann was tracking down the dc3dd failure. With some configurations it
was building, with others not. So he was trying to figure which package
that gets built before dc3dd causes the problem. For this, it was
really nice to be able to load a configuration, and immediately see in
which order packages would be built, and therefore which packages would
be built before dc3dd, without having to do the build itself.
Does that explain better the use case for this?
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2017-04-07 10:43 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-02 13:03 [Buildroot] [PATCH] core: add rule to dump packages' build order Yann E. MORIN
2017-04-03 10:10 ` Arnout Vandecappelle
2017-04-04 18:59 ` Yann E. MORIN
2017-04-07 10:30 ` Arnout Vandecappelle
2017-04-07 10:43 ` Thomas Petazzoni [this message]
2017-04-07 11:11 ` Arnout Vandecappelle
2017-04-07 19:24 ` Yann E. MORIN
2017-04-07 19:44 ` Yann E. MORIN
2017-04-10 9:28 ` Arnout Vandecappelle
2017-04-10 11:44 ` Thomas Petazzoni
2017-04-13 22:18 ` Alexandre Belloni
2017-04-07 10:31 ` Arnout Vandecappelle
2017-04-11 9:23 ` Arnout Vandecappelle
2017-04-13 21:09 ` Thomas Petazzoni
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=20170407124314.660c3edc@free-electrons.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox