From: "H. Peter Anvin" <hpa@zytor.com>
To: "linux-kbuild@vger.kernel.org" <linux-kbuild@vger.kernel.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Ingo Molnar <mingo@elte.hu>
Subject: Kconfig and toolchain dependencies
Date: Fri, 03 Feb 2012 13:29:09 -0800 [thread overview]
Message-ID: <4F2C51A5.1040800@zytor.com> (raw)
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
... and perhaps do other tests. I suspect we would run the tests less
frequently than what we do right now with the tests embedded in the
Makefile.
Does anyone have a feel for if this would be a good addition, and if so
where it best fits into the chain?
-hpa
--
H. Peter Anvin, Intel Open Source Technology Center
I work for Intel. I don't speak on their behalf.
next reply other threads:[~2012-02-03 21:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-03 21:29 H. Peter Anvin [this message]
2012-02-04 18:32 ` Kconfig and toolchain dependencies Josh Triplett
2012-02-07 20:26 ` H. Peter Anvin
2012-02-24 22:19 ` Michal Marek
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=4F2C51A5.1040800@zytor.com \
--to=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