All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] lzlib: fix Lua dependency
Date: Thu, 10 Mar 2016 23:52:32 +0100	[thread overview]
Message-ID: <20160310235232.4367c8dd@free-electrons.com> (raw)
In-Reply-To: <1457561898-2054-1-git-send-email-joerg.krause@embedded.rocks>

Dear J?rg Krause,

On Wed,  9 Mar 2016 23:18:18 +0100, J?rg Krause wrote:
> lzlib cannot be build with LuaJIT and requires Lua 5.x.
> 
> Fixes:
> http://autobuild.buildroot.net/results/d71/d71209c3e5235f507afee38b618d5740ef91fdcb/
> http://autobuild.buildroot.net/results/ef8/ef80136ec17ad9b0a5e3121c4b6091b15c3da0d4/
> http://autobuild.buildroot.net/results/5e9/5e9d77e415e8cafb842b84d3d6d91280ae5491e3/
> 
> Signed-off-by: J?rg Krause <joerg.krause@embedded.rocks>
> ---
>  package/lzlib/Config.in | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/package/lzlib/Config.in b/package/lzlib/Config.in
> index f7fae15..32328c5 100644
> --- a/package/lzlib/Config.in
> +++ b/package/lzlib/Config.in
> @@ -1,7 +1,7 @@
>  config BR2_PACKAGE_LZLIB
>  	bool "lzlib"
>  	select BR2_PACKAGE_ZLIB
> -	depends on BR2_PACKAGE_HAS_LUAINTERPRETER
> +	depends on BR2_PACKAGE_LUA

It is somewhat surprising that a *new* version removes support for
LuaJIT.

But OK, applied. If anybody cares about lzlib in a LuaJIT context, they
can fix this up.

Thanks!

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

      reply	other threads:[~2016-03-10 22:52 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-09 22:18 [Buildroot] [PATCH] lzlib: fix Lua dependency Jörg Krause
2016-03-10 22:52 ` Thomas Petazzoni [this message]

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=20160310235232.4367c8dd@free-electrons.com \
    --to=thomas.petazzoni@free-electrons.com \
    --cc=buildroot@busybox.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.