Lua 5.2 support

[devurandom]

lsyncd-2.0.7 fails to compile with Lua 5.2, see for example the Gentoo bug on the matter [1].

The error is:
x86_64-pc-linux-gnu-gcc -DHAVE_CONFIG_H -I. -pipe -O2 -march=athlon64-sse3 -Wall -c inotify.c
inotify.c:132:1: error: unknown type name ‘luaL_reg’
[…]

A complete build.log is available at abovementioned report.

[1] https://bugs.gentoo.org/show_bug.cgi?id=434238

[axkibe]

Thank you. I'll cater for this in upcoming Lsyncd 2.1

[devurandom]

I created a patch and submitted it as pull #147.

[axkibe]

Thank you, will look through it at the weekend.
Don't you think it would be possible to write it in a way it works with 5.1
and 5.2?
Kind regards, Axel

On Tue, Sep 18, 2012 at 3:25 PM, Dennis Schridde
notifications@github.comwrote:

I created a patch and submitted it as pull #147#147
.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/146#issuecomment-8654563.

[axkibe]

If I remember correctly from the mailinglist, there is some backward
compatibility flag in Lua 5.2 to turn on before including the header file,
this time they turned it off by default. It will create backward
compatilibity with Lua 5.1, but not what has been been deprecated in 5.1
already. However, in 5.1 they had the compatibility flag for 5.0 turned on
by default, so maybe Lsyncd uses 5.0 stuff. If thats the case it should be
changed to 5.1 native code, that works with 5.2 compatibility flag turned
on. I don't expect a 5.3 or 6.0 in any near or middle future, see:
http://lua-users.org/lists/lua-l/2011-12/msg00579.html

Thank you, for your effort! Its great work.

Kind regards, Axel
.

On Tue, Sep 18, 2012 at 3:39 PM, Axel Kittenberger axkibe@gmail.com wrote:

Thank you, will look through it at the weekend.
Don't you think it would be possible to write it in a way it works with
5.1 and 5.2?
Kind regards, Axel

On Tue, Sep 18, 2012 at 3:25 PM, Dennis Schridde <notifications@github.com

wrote:

I created a patch and submitted it as pull #147#147
.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/146#issuecomment-8654563.