Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] linux: kconfig needs the toolchain
Date: Wed, 1 Aug 2018 17:48:32 +0200	[thread overview]
Message-ID: <20180801154832.GB2294@scaer> (raw)
In-Reply-To: <20180801083541.653e1abc@windsurf>

Thomas, All,

On 2018-08-01 08:35 +0200, Thomas Petazzoni spake thusly:
> 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.

We need the toolchain to generate the .config file, even in a nromal
build, i.e. not just for the menuconfig et al.

I.e. running 'make clean; make' should also build the toolchain before
the linux configuration, which is part of the kconfig infra.

Agreed that it would not happen in practice, but for theoretical
correctness, it is also needed in this case.

> 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.

Well, I also thought about that, but decided against, because we don't
want to generalise a behaviour based on a single case.

As for the configurability, I would have gone with:

    FOO_KCONFIG_NEEDS_CC = YES

because that is actually what it wants currently.

But in the future, it might also want to call 'dtc' to check whether it
supports overlays, or call 'openssl' to check if a cypher is available.
So we'd have to expand this to:

    FOO_KCONFIG_DEPENDENCIES = toolchain host-dtc host-openssl

Or whatev'...

So I'd prefer waiting, and hard-coding that one peculiarity within the
only user so far, the linux kernel.

Regards,
Yann E. MORIN.

-- 
.-----------------.--------------------.------------------.--------------------.
|  Yann E. MORIN  | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software  Designer | \ / CAMPAIGN     |  ___               |
| +33 223 225 172 `------------.-------:  X  AGAINST      |  \e/  There is no  |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL    |   v   conspiracy.  |
'------------------------------^-------^------------------^--------------------'

  reply	other threads:[~2018-08-01 15:48 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
2018-08-01 15:48     ` Yann E. MORIN [this message]
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=20180801154832.GB2294@scaer \
    --to=yann.morin.1998@free.fr \
    --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