All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arnout Vandecappelle <arnout@mind.be>
To: Jesse Millwood <jesse_dev@fastmail.com>, buildroot@buildroot.org
Subject: Re: [Buildroot] Overriding Kconfig Values from external br2
Date: Thu, 6 Jan 2022 10:45:21 +0100	[thread overview]
Message-ID: <09340549-99c9-b79c-17db-3967b1ab6335@mind.be> (raw)
In-Reply-To: <37282adb-8559-4124-874d-c1729bd3ce01@www.fastmail.com>



On 05/01/2022 20:03, Jesse Millwood wrote:
> Hello,
> 
> I have an external C/C++ toolchain that I've put together that uses MUSL. I've 
> also built an external Rust toolchain that uses my MUSL toolchain.
> 
> My issue is that there is a Rust Kconfig variable that specifies if a specific 
> architecture supports Rust.
> 
> The Kconfig variable in question is BR2_PACKAGE_HOST_RUSTC_TARGET_ARCH_SUPPORTS 
> in package/rustc/Config.in.host.

[snip]

> You may notice that I changed the libc depends line to be or'd with 
> BR2_TOOLCHAIN_USES_MUSL. It seems that this does not get considered when I 
> choose my external musl toolchain option. In the menuconfig when I search for 
> the BR2_PACKAGE_HOST_RUSTC_TARGET_ARCH_SUPPORTS variable with the "/" key it 
> looks like it is only getting it from the original file. Does buildroot have a 
> mechanism for overwriting this kind of setting and if not, does anyone have an 
> idea of how I would accomplish what I am trying to do (make buildroot honor my 
> external rust toolchain)?

  No, there's no way to override the dependencies of an existing Config.in 
symbol in an external.

  However, this was corrected in upstream Buildroot in commit 
d69d40c029dc7d8199b745eaee759d92b66c5d17. So you can try to backport that commit 
instead, or just update Buildroot to something more recent.

  Regards,
  Arnout


> 
> Thanks,
> Jesse
> 
> _______________________________________________
> buildroot mailing list
> buildroot@buildroot.org
> https://lists.buildroot.org/mailman/listinfo/buildroot
> 
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  reply	other threads:[~2022-01-06  9:45 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-05 19:03 [Buildroot] Overriding Kconfig Values from external br2 Jesse Millwood
2022-01-06  9:45 ` Arnout Vandecappelle [this message]
2022-01-06 15:37   ` Jesse Millwood
2022-01-06 17:09     ` Arnout Vandecappelle
2022-01-08  0:07       ` Jesse Millwood

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=09340549-99c9-b79c-17db-3967b1ab6335@mind.be \
    --to=arnout@mind.be \
    --cc=buildroot@buildroot.org \
    --cc=jesse_dev@fastmail.com \
    /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.