luaposix: fix runtime by selecting "bit32" instead of "bitop"
authorArnout Vandecappelle <arnout@mind.be>
Thu, 23 Feb 2017 17:00:37 +0000 (18:00 +0100)
committerThomas Petazzoni <thomas.petazzoni@free-electrons.com>
Thu, 2 Mar 2017 21:57:11 +0000 (22:57 +0100)
commit8bd2e2f3194b5e73680dc16555a7a77b73e2c3ff
treee82653347d763f7a444cd6c93647a1d492c182f2
parent276f4fd56208fc496f5c5739d347fbd05bba7108
luaposix: fix runtime by selecting "bit32" instead of "bitop"

Since the bump of luaposix to 33.4.0, it doesn't work anymore at
runtime with LuaJIT or Lua 5.1. This can be tested with the following
defconfig:

BR2_x86_64=y
BR2_TOOLCHAIN_EXTERNAL=y
BR2_PACKAGE_LUA=y
BR2_PACKAGE_LUA_5_1=y
BR2_PACKAGE_LUAPOSIX=y

/usr/bin/lua: /usr/share/lua/5.1/posix/init.lua:17: module 'bit32' not found:
...

In older luaposix versions, it would try to load the 'bit' instead of
'bit32' module if LUAVER == 5.1. However, this feature was removed in
33.4.0.

So instead of adding a runtime dependency on luabitop, depend on
lua-bit32.

Signed-off-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be>
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
package/luaposix/Config.in