On Fri, Feb 23, 2018 at 2:17 AM, Ruediger Pluem <rpl...@apache.org> wrote:
> Hm, it work for me on Centos 6 and 7. What lua packages have you installed?
> I only have the 64 bit versions installed. Do you have 32 bit versions 
> installed as well?
>
> On 02/22/2018 10:54 PM, William A Rowe Jr wrote:
>> This wasn't pretty; candidate 2.4.30 build on current fedora...
>>
>> /path/build/libtool --silent --mode=link gcc  -g -O2 -pthread
>> -L/path/lib      -o mod_lua.la -rpath /path/modules -module
>> -avoid-version  lua_apr.lo lua_config.lo mod_lua.lo lua_request.lo
>> lua_vmprep.lo lua_dbd.lo lua_passwd.lo -L/usr/lib -llua -lm -lcrypt
>> /usr/bin/ld: skipping incompatible /usr/lib/libm.so when searching for -lm
>> /usr/bin/ld: skipping incompatible /usr/lib/libcrypt.so when searching
>> for -lcrypt
>> /usr/bin/ld: skipping incompatible /usr/lib/libpthread.so when
>> searching for -lpthread
>> /usr/bin/ld: skipping incompatible /usr/lib/libc.so when searching for -lc
>>
>> -L/usr/lib ? That's F'ed up.
>>
>> LUA_CFLAGS='-I/usr/include'
>> LUA_LIBS='-L/usr/lib -llua -lm'
>> MOD_LUA_LDADD='-L/usr/lib -llua -lm -lcrypt '
>>
>> are our mistakes. Not sure this is a regression, but it is nonsense.
>>
>
> Hm, it works for me on Centos 6 and 7. What lua packages do you have 
> installed?
> I only have the 64 bit versions installed. Do you have 32 bit versions 
> installed as well?

Here's my deployment;

[wrowe@hub bld-candidate]$ ls /usr/lib/liblua*
ls: cannot access '/usr/lib/liblua*': No such file or directory
[wrowe@hub bld-candidate]$ ls /usr/lib/pkgconfig/lua*
ls: cannot access '/usr/lib/pkgconfig/lua*': No such file or directory
[wrowe@hub bld-candidate]$ ls /usr/lib64/liblua*
/usr/lib64/liblua-5.1.so       /usr/lib64/libluajit-5.1.so.2.1.0
/usr/lib64/liblua-5.3.so       /usr/lib64/liblua.so
/usr/lib64/libluajit-5.1.so.2
[wrowe@hub bld-candidate]$ ls /usr/lib64/pkgconfig/lua*
/usr/lib64/pkgconfig/lua-5.1.pc  /usr/lib64/pkgconfig/lua.pc
[wrowe@hub bld-candidate]$ ls /usr/include/lua*
/usr/include/luaconf.h         /usr/include/lua.h    /usr/include/lualib.h
/usr/include/luaconf-x86_64.h  /usr/include/lua.hpp
/usr/include/lua-5.1:
lauxlib.h  luaconf.h  lua.h  lua.hpp  lualib.h

> But having a quick look over modules/lua/config.m4 seems to confirm the 
> nonsense you state
> and it seems to be luck that it works for me.

Do you end up with an -L/usr/lib for the module in your CentOS example?
Did it happen to pick up the lib64 path? Or no lib path at all?

> But it does not seem to be a regression.

Glad for the confirmation.

Reply via email to