linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: sam@ravnborg.org (Sam Ravnborg)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH -next 2/2] kbuild: fix for updated LZ4 tool with the new streaming format
Date: Tue, 16 Jul 2013 20:04:08 +0200	[thread overview]
Message-ID: <20130716180408.GA19863@merkur.ravnborg.org> (raw)
In-Reply-To: <201307161008.07643.yann.morin.1998@free.fr>

On Tue, Jul 16, 2013 at 10:08:07AM +0200, Yann E. MORIN wrote:
> Andrew, All,
> 
> On Tuesday 16 July 2013 09:56:11 Andrew Morton wrote:
> > On Tue, 16 Jul 2013 00:47:27 -0700 Andrew Morton <akpm@linux-foundation.org> wrote:
> > > On Mon, 15 Jul 2013 15:08:20 -0700 "H. Peter Anvin" <hpa@zytor.com> wrote:
> > > > On 07/15/2013 03:03 PM, Andrew Morton wrote:
> [--SNIP--]
> > > > We keep running over the need to be able to have kconfig run tests on
> > > > the build system (for toolchain support or for optional tools needed);
> > > > running them in the Makefiles (i.e. at Kbuild time) is simply too late.
> > > > 
> > > 
> > > Would it make sense to extend Kconfig's `depends'?
> > > 
> > > 	depends on $(shell-command)
> > > 
> > > I don't know how practical that would be to implement...
> 
> I'm afraid this will get rather ugly and not trivial.
> 
> Can we mix 'depends on SYMBOL' and 'depends on $(command)' ?
> Can we mix both in a boolean expression such as 'depends on SYMBOL
> && $(command)' ?
> 
> What would be the condition for evaluating the dependency rule? Evaluation
> at Kconfig read-time might not be enough, given this construct:
> 
>     config FOO
>         depends on $(foo)
>     comment "'foo' is missing, please install it"
>         depends on !$(foo)
> 
> Also, I believe Kconfig should stay a config-only language, without
> much esoteric features.

We could extend the symbol option part to retreive values from a binary.
Something like this:

config FOOBAR
        bool
        option exec="true"

FOOBAR would assume the value "y" if the command true has exit code == 0, otherwise "n".
And similar conversions for other types.

This only extendt Kconfig slightly - using an already present method to import
external values.

The drawback I see with this approach is that we may execute a lot of small programs
where the value is never used.
Implementing lazy evaluation of a symbol value will not be easy I think.

	Sam

  parent reply	other threads:[~2013-07-16 18:04 UTC|newest]

Thread overview: 45+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-06  8:42 [PATCH -next 1/2] arm: Remove enforced Os flag for LZ4 decompressor Kyungsik Lee
2013-05-06  8:42 ` [PATCH -next 2/2] kbuild: fix for updated LZ4 tool with the new streaming format Kyungsik Lee
2013-05-06  9:51   ` Borislav Petkov
2013-07-10  8:12     ` Geert Uytterhoeven
2013-07-10  9:36       ` Borislav Petkov
2013-07-10 18:28         ` Markus Trippelsdorf
2013-07-10 20:01           ` Borislav Petkov
2013-07-11  4:34           ` Kyungsik Lee
2013-07-11  9:46             ` [PATCH] .gitignore: ignore *.lz4 files Markus Trippelsdorf
2013-07-12  7:56   ` [PATCH -next 2/2] kbuild: fix for updated LZ4 tool with the new streaming format Ingo Molnar
2013-07-12  8:01     ` Borislav Petkov
2013-07-12 10:13       ` Ingo Molnar
2013-07-12 10:23         ` Borislav Petkov
2013-07-12 11:18           ` Andrew Morton
2013-07-12 12:06             ` Ingo Molnar
2013-07-12 12:13             ` Borislav Petkov
2013-07-12 12:34               ` Florian Fainelli
2013-07-12 12:46                 ` Borislav Petkov
2013-07-15 22:03     ` Andrew Morton
2013-07-15 22:08       ` H. Peter Anvin
2013-07-16  7:47         ` Andrew Morton
2013-07-16  7:56           ` Andrew Morton
2013-07-16  8:08             ` Yann E. MORIN
2013-07-16  8:27               ` Andrew Morton
2013-07-16  9:05                 ` Borislav Petkov
2013-07-16  9:12                   ` Yann E. MORIN
2013-07-16  9:22                     ` Borislav Petkov
2013-07-16  9:32                       ` Yann E. MORIN
2013-07-16  9:38                         ` Borislav Petkov
2013-07-16  9:45                           ` Yann E. MORIN
2013-07-16  9:59                             ` Borislav Petkov
2013-07-16 10:04                               ` Florian Fainelli
2013-07-16 18:04               ` Sam Ravnborg [this message]
2013-07-17 21:16                 ` Sam Ravnborg
2013-07-17 21:44                   ` Borislav Petkov
2013-07-17 22:30                   ` Yann E. MORIN
2013-07-17 23:22                     ` H. Peter Anvin
2013-07-18  8:02                       ` Geert Uytterhoeven
2013-07-18  7:22                     ` Geert Uytterhoeven
2013-07-18  7:34                       ` Andrew Morton
2013-07-18  7:47                         ` Yann E. MORIN
2013-07-18  7:52                           ` Andrew Morton
2013-07-18 20:47                     ` Sam Ravnborg
2013-07-16  9:13             ` Florian Fainelli
2013-07-16  9:25               ` Yann E. MORIN

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=20130716180408.GA19863@merkur.ravnborg.org \
    --to=sam@ravnborg.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    /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).