Hi Paul,

thanks for caring about my "contrib" package! :)

Quoting Paul Gevers (2022-09-18 11:44:07)
> vcmi build depends on libluajit-5.1-dev but that got removed on
> ppc64el because it doesn't work correcty on that architecture and
> noone volunteers to fix *and maintain* it on that architecture. See
> bug #1014853.
> 
> Please investigate if you can just use liblua or if your package needs
> to be removed on ppc64el.

I thought according to the recent threat on d-devel [1] packages that FTBFS on
some arches should rather just let it FTBFS instead of maintaining a list of
architectures the package can be built on?

[1] https://lists.debian.org/20220911150857.xedt2an2vye3qrc7@begin

Do you know more about Lua? I do not. If I change from libluajit-5.1-dev to
liblua5.1-dev I get:

/<<PKGBUILDDIR>>/scripting/lua/LuaScriptingContext.cpp:47:18: error: 
‘LUA_BITLIBNAME’ was not declared in this scope; did you mean ‘LUA_IOLIBNAME’?
   47 |                 {LUA_BITLIBNAME, luaopen_bit}
      |                  ^~~~~~~~~~~~~~
      |                  LUA_IOLIBNAME
/<<PKGBUILDDIR>>/scripting/lua/LuaScriptingContext.cpp:47:34: error: 
‘luaopen_bit’ was not declared in this scope; did you mean ‘luaopen_io’?
   47 |                 {LUA_BITLIBNAME, luaopen_bit}
      |                                  ^~~~~~~~~~~
      |                                  luaopen_io
/<<PKGBUILDDIR>>/scripting/lua/LuaScriptingContext.cpp:48:9: error: could not 
convert ‘{{"", luaopen_base}, {"table", luaopen_table}, {"string", 
luaopen_string}, {"math", luaopen_math}, {<expression error>, <expression 
error>}}’ from ‘<brace-enclosed initializer list>’ to ‘const 
std::vector<luaL_Reg>’
   48 |         };
      |         ^
      |         |
      |         <brace-enclosed initializer list>

Thanks!

cheers, josch

Attachment: signature.asc
Description: signature

Reply via email to