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] boot/barebox: kconfig needs the toolchain
Date: Tue, 29 Dec 2020 23:56:16 +0100	[thread overview]
Message-ID: <20201229225616.GC1680670@scaer> (raw)
In-Reply-To: <20201208101107.32758-1-jmaselbas@kalray.eu>

Jules, All,

On 2020-12-08 11:11 +0100, Jules Maselbas via buildroot spake thusly:
> In barebox v2020.09.0, kconfig has been updated to a newer version
> based on Linux 5.9-rc2.  As in linux, kconfig can call the compiler
> to test its capabilities.
> 
> Signed-off-by: Jules Maselbas <jmaselbas@kalray.eu>

Applied to master, thanks!

I've just added a little blurb about custom versions: since we can't
know whether custom version need the toolchain or not, we just make that
unconditional.

Thanks!

Regards,
Yann E. MORIN.

> ---
>  boot/barebox/barebox.mk | 5 +++++
>  1 file changed, 5 insertions(+)
> 
> diff --git a/boot/barebox/barebox.mk b/boot/barebox/barebox.mk
> index 422f27312d..2e80954741 100644
> --- a/boot/barebox/barebox.mk
> +++ b/boot/barebox/barebox.mk
> @@ -88,6 +88,11 @@ $(1)_KCONFIG_DEPENDENCIES = \
>  	$(BR2_BISON_HOST_DEPENDENCY) \
>  	$(BR2_FLEX_HOST_DEPENDENCY)
>  
> +# Starting with barebox v2020.09.0, the kconfig used calls the
> +# cross-compiler to check its capabilities. So we need the
> +# toolchain before we can call the configurators.
> +$(1)_KCONFIG_DEPENDENCIES += toolchain
> +
>  ifeq ($$(BR2_TARGET_$(1)_BAREBOXENV),y)
>  define $(1)_BUILD_BAREBOXENV_CMDS
>  	$$(TARGET_CC) $$(TARGET_CFLAGS) $$(TARGET_LDFLAGS) -o $$(@D)/bareboxenv \
> -- 
> 2.17.1
> 
> 
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot

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

  reply	other threads:[~2020-12-29 22:56 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-08 10:11 [Buildroot] [PATCH] boot/barebox: kconfig needs the toolchain Jules Maselbas
2020-12-29 22:56 ` Yann E. MORIN [this message]
2021-01-05 15:10 ` Peter Korsgaard

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=20201229225616.GC1680670@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