public inbox for linux-kbuild@vger.kernel.org
 help / color / mirror / Atom feed
From: Michal Marek <mmarek@suse.cz>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: "linux-kbuild@vger.kernel.org" <linux-kbuild@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Ingo Molnar <mingo@elte.hu>
Subject: Re: Kconfig and toolchain dependencies
Date: Fri, 24 Feb 2012 23:19:10 +0100	[thread overview]
Message-ID: <4F480CDE.8010605@suse.cz> (raw)
In-Reply-To: <4F2C51A5.1040800@zytor.com>

Dne 3.2.2012 22:29, H. Peter Anvin napsal(a):
> Right now, we don't have a good way to encode toolchain dependencies in
> Kconfig.  This makes it hard to add optional features which depend on
> newer toolchain features.
> 
> If we just add them, then it breaks all*config and randconfig on
> platforms with the older toolchains unless the user manually adds
> exclusion rules.  This is bad for testing.
> 
> It seems relatively straightforward to do if we were to manifest some
> CONFIG_ variables based on the target toolchain, e.g.
> 
> CONFIG_GCC=0x040601

(sorry for the late reply)

It would be a bit tricky, because the toolchain version depends also on
CONFIG_CROSS_COMPILE. So Kconfig would need to know the semantics of
CONFIG_CROSS_COMPILE and CONFIG_GCC and the dependency of the latter on
the former.

Michal

  parent reply	other threads:[~2012-02-24 22:19 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-03 21:29 Kconfig and toolchain dependencies H. Peter Anvin
2012-02-04 18:32 ` Josh Triplett
2012-02-07 20:26   ` H. Peter Anvin
2012-02-24 22:19 ` Michal Marek [this message]
2012-02-24 22:23   ` H. Peter Anvin

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=4F480CDE.8010605@suse.cz \
    --to=mmarek@suse.cz \
    --cc=hpa@zytor.com \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    /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