linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Josh Triplett <josh@joshtriplett.org>
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: Sat, 4 Feb 2012 10:32:59 -0800	[thread overview]
Message-ID: <20120204183259.GA28208@leaf> (raw)
In-Reply-To: <4F2C51A5.1040800@zytor.com>

On Fri, Feb 03, 2012 at 01:29:09PM -0800, H. Peter Anvin wrote:
> 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?

This seems like a *great* idea.  Unfortunately, a quick look at the
implementation of kbuild suggests that it doesn't currently implement
numeric comparisons (<, <=, >, >=), only equality (= and !=).  Most of
the time, a Kconfig file will want to write "depends GCC >=
some_version".

Looking at scripts/kconfig/expr.c, it doesn't look that hard to add,
though.

- Josh Triplett

  reply	other threads:[~2012-02-04 18:33 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 [this message]
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=20120204183259.GA28208@leaf \
    --to=josh@joshtriplett.org \
    --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;
as well as URLs for NNTP newsgroup(s).