[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20130715150342.35f7620ffe0835e3e2bc37d0@linux-foundation.org>
Date: Mon, 15 Jul 2013 15:03:42 -0700
From: Andrew Morton <akpm@...ux-foundation.org>
To: Ingo Molnar <mingo@...nel.org>
Cc: 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,
"H. Peter Anvin" <hpa@...or.com>, Ingo Molnar <mingo@...e.hu>,
Thomas Gleixner <tglx@...utronix.de>,
Russell King <rmk@....linux.org.uk>,
Borislav Petkov <bp@...en8.de>,
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 Fri, 12 Jul 2013 09:56:02 +0200 Ingo Molnar <mingo@...nel.org> wrote:
>
> * Kyungsik Lee <kyungsik.lee@....com> wrote:
> > quiet_cmd_lz4 = LZ4 $@
> > cmd_lz4 = (cat $(filter-out FORCE,$^) | \
> > - lz4demo -c1 stdin stdout && $(call size_append, $(filter-out FORCE,$^))) > $@ || \
> > + lz4c -l -c1 stdin stdout && $(call size_append, $(filter-out FORCE,$^))) > $@ || \
> > (rm -f $@ ; false)
>
> None of the major distros I tried has the lz4 or lz4c binary available,
> and this breaks randconfig builds:
>
> /bin/sh: lz4c: command not found
>
> If:
>
> CONFIG_HAVE_KERNEL_LZ4=y
> CONFIG_KERNEL_LZ4=y
> CONFIG_RD_LZ4=y
> CONFIG_LZ4_DECOMPRESS=y
> CONFIG_DECOMPRESS_LZ4=y
>
> If a utility is not widely available yet and if the utility is not in the
> kernel proper, could you please at least make sure that randconfig does
> not stumble over non-buildable kernels?
I don't know how to do this. Any suggestions?
It has to be done at `make config' time. We'd need to probe for the
presence of lz4c and then.... what?
Is there any precedent for this?
I don't think we can just ignore the absence of lz4c - the user has
selected a config which his system cannot build. The problem lies
within randconfig itself.
--
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