From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] linux: kconfig needs the toolchain
Date: Wed, 1 Aug 2018 08:35:41 +0200 [thread overview]
Message-ID: <20180801083541.653e1abc@windsurf> (raw)
In-Reply-To: <d703b5fb-a3e9-6398-c5e8-bf63c25ba106@mind.be>
Hello,
On Wed, 1 Aug 2018 00:21:18 +0200, Arnout Vandecappelle wrote:
> > Like is done in the kconfig-package infra for the dependency on
> > $(1)-patch, we use an order-only prerequisites on the toolchain,
> > to guarantee the compiler is available before we can display the
> > kconfig of the kernel.
> You actually want to say here why an order-only dependency and not a normal
> dependency: "Since 'toolchain' is a phony target and therefore always out of
> date, a normal dependency would cause the .config target to be rebuilt on each
> invocation of make."
When looking at the patch, my initial reaction was: why is the
dependency on the .config file, rather than on the
-menuconfig/-xconfig/-nconfig/... targets. Those are phony targets, so
a normal dependency would work.
This could even be pushed one level up to the pkg-kconfig
infrastructure, as we're pretty likely to see other packages go down
this route in the future maybe ? Of course, it should be optional.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Bootlin (formerly Free Electrons)
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2018-08-01 6:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-31 20:16 [Buildroot] [PATCH] linux: kconfig needs the toolchain Yann E. MORIN
2018-07-31 22:21 ` Arnout Vandecappelle
2018-08-01 6:35 ` Thomas Petazzoni [this message]
2018-08-01 15:48 ` Yann E. MORIN
2018-08-01 21:12 ` Yann E. MORIN
2018-08-01 15:39 ` 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=20180801083541.653e1abc@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