[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20130716090546.GB4402@pd.tnic>
Date: Tue, 16 Jul 2013 11:05:46 +0200
From: Borislav Petkov <bp@...en8.de>
To: Andrew Morton <akpm@...ux-foundation.org>
Cc: "Yann E. MORIN" <yann.morin.1998@...e.fr>,
"H. Peter Anvin" <hpa@...or.com>, Ingo Molnar <mingo@...nel.org>,
Kyungsik Lee <kyungsik.lee@....com>,
Michal Marek <mmarek@...e.cz>, linux-kernel@...r.kernel.org,
linux-kbuild@...r.kernel.org, x86@...nel.org,
celinux-dev@...ts.celinuxforum.org,
linux-arm-kernel@...ts.infradead.org, hyojun.im@....com,
chan.jeong@....com, raphael.andy.lee@...il.com,
Ingo Molnar <mingo@...e.hu>,
Thomas Gleixner <tglx@...utronix.de>,
Russell King <rmk@....linux.org.uk>,
Florian Fainelli <florian@...nwrt.org>,
Yann Collet <yann.collet.73@...il.com>,
Chanho Min <chanho.min@....com>
Subject: Re: [PATCH -next 2/2] kbuild: fix for updated LZ4 tool with the new
streaming format
On Tue, Jul 16, 2013 at 01:27:56AM -0700, Andrew Morton wrote:
> What I'm angling at is, rather than a single global front-end script,
> can we embed the scripts in some fashion within the various Kconfig
> files? Say,
>
> script ./some-script.sh
>
> and the config system will only evaluate that command if it is working
> on that Kconfig file. Obviously that requires a multiple-pass thing.
What's wrong with simply grepping the .config we've just created for
*enabled* symbols which require userspace support, check for the
presence of said support and bail out if none?
I.e., those steps:
1. make <whatever>config
2. make => A prereq. target runs the shell script.
--
Regards/Gruss,
Boris.
Sent from a fat crate under my desk. Formatting is fine.
--
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists