On Wed, Feb 29, 2012 at 6:14 AM, Murray S. Kucherawy <msk_at_cloudmark.com> wrote:
>> OK, now installed using 5.1.4. It's weird, I have two identical boxes
>> running RH EL 5. On the first I installed lua 5.2.0 and then installed
>> opendkim-2.4.3 without a problem: I didn't have to specify --with-lua
>> for configure, and it was able to find lua all by itself under
>> /usr/local. On the other system I had to explicitly specify --with-lua
>> and then I ran into the reported problem.
> By default, the configure script looks in /usr and /usr/local for a subdirectory called include/lua51 or include/lua5.1 or include (in that order) containing lua.h. If you have it somewhere else, you have to tell it where. Does that explain what you saw?
The configure script looks for pkgconfig files (lua.pc) first, and
some rpm have it.
# SuSE seems to have it for instance
#
http://pkgs.org/opensuse-factory/opensuse-oss-x86_64/lua-5.2.0-19.2.x86_64.rpm.html#provides
I've installed lua-5.2.0 into my FreeBSD box, and tried reproduce the
error.
- The lua-5.2.0 tarball from lua.org does not have lua.pc file:
perhaps someone will contribute one as in 5.1.x.
- LIBLUA_CFLAGS and LIBLUA_LIBS env didn't work for me, though they
were mentioned in the configure script.
- modified the configure script to accept
-I/usr/local/include/lua52, -L/usr/local/lib/lua52, and -llua-5.2
then I got the same:
| cc -std=gnu99 -DHAVE_CONFIG_H -I. -I.. -I./../libopendkim
-I/usr/include -I/usr/local/include/lua52
-DCONFIG_BASE=\"/usr/local/etc\" -O2 -pipe -fno-strict-aliasing -MT
miltertest-miltertest.o -MD -MP -MF .deps/miltertest-miltertest.Tpo -c
-o miltertest-miltertest.o `test -f 'miltertest.c' || echo
'./'`miltertest.c
| miltertest.c: In function 'main':
| miltertest.c:3975: warning: implicit declaration of function 'luaL_register'
| miltertest.c:4125: error: too few arguments to function 'lua_load'
both luaL_register and lua_load are on API change section of lua manual.
http://www.lua.org/manual/5.2/manual.html#8.3
I think supporting lua-5.2.0 requires certain amount of work.
I'd suggest that putting it off towards 2.5.1 or later.
Regards,
--
Hirohisa Yamaguchi
<umq.461_at_gmail.com>
Received on Wed Feb 29 2012 - 05:16:27 PST