From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] package/lua-msgpack-native: fix build with moonjit
Date: Wed, 18 Dec 2019 23:15:04 +0100 [thread overview]
Message-ID: <20191218231504.26a30aa2@windsurf> (raw)
In-Reply-To: <20191210174004.25479-1-francois.perrad@gadz.org>
On Tue, 10 Dec 2019 18:40:04 +0100
Francois Perrad <fperrad@gmail.com> wrote:
> compatibility with Lua 5.0 was removed in LuaJIT/moonjit 2.1.x
> (Lua 5.1.x and LuaJIT 2.0.x have this compatibility)
>
> see http://autobuild.buildroot.org/results/4e4/4e428df01def186cb034a1774f6c00e2e7c9468c/build-end.log
This should have been:
Fixes:
http://autobuild.buildroot.org/results/4e428df01def186cb034a1774f6c00e2e7c9468c/
>
> Signed-off-by: Francois Perrad <francois.perrad@gadz.org>
> ---
> package/lua-msgpack-native/lua-msgpack-native.mk | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/package/lua-msgpack-native/lua-msgpack-native.mk b/package/lua-msgpack-native/lua-msgpack-native.mk
> index acd3a0e1c..b3ca7aef4 100644
> --- a/package/lua-msgpack-native/lua-msgpack-native.mk
> +++ b/package/lua-msgpack-native/lua-msgpack-native.mk
> @@ -11,7 +11,7 @@ LUA_MSGPACK_NATIVE_LICENSE = Apache-2.0
> LUA_MSGPACK_NATIVE_LICENSE_FILES = LICENSE.txt
>
> define LUA_MSGPACK_NATIVE_BUILD_CMDS
> - $(TARGET_CC) $(TARGET_CFLAGS) -fPIC -shared -o $(@D)/msgpack.so $(@D)/mp.c
> + $(TARGET_CC) $(TARGET_CFLAGS) -DluaL_reg=luaL_Reg -fPIC -shared -o $(@D)/msgpack.so $(@D)/mp.c
I've added a comment in the .mk file to explain this, as it is a bit
weird, and then I've applied to master.
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
prev parent reply other threads:[~2019-12-18 22:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-10 17:40 [Buildroot] [PATCH] package/lua-msgpack-native: fix build with moonjit Francois Perrad
2019-12-18 22:15 ` 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=20191218231504.26a30aa2@windsurf \
--to=thomas.petazzoni@bootlin.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.