Version mismatch between Lua and Luarocks?

[pccasto]

Hi,

Thanks for creating this decoder, and publishing this info. It may help me diagnose an issue. But before I get to actually using it :-), I thought I'd let you know about a couple of small issues with the setup instructions.

Installing this on a raspberry pi, but don't think that is the issue.
I installed the specified version of Lua (lua5.2-dev), and tried both LuaRocks 2.4.4 and 2.4.2.
When I ran ./configure, both complained about not finding headers, soI tried both with:
' --with-lua-include=/usr/include/lua5.2/'.
But in both cases the configure complained about interpreter mismatches. Seems that luarocks expects only 5.1?

So I did an apt-get install of lua5.1-dev, and the .configure and make bootstrap worked.

When I did the luarocks install, it seems that the name is lua-zlib, rather than lua_zlib.

Thanks and best regards,
~paul

[stefanLeo]

Hi

Thx for the feedback - I already fixed the luarocks zlib typo.
I will check the other stuff on my Ubuntu setup and update accordingly.

Let me know if the script worked for you ;-)

BR
Stefan

[pccasto]

Hi Stefan -

Looks like both of these are needed
sudo apt-get install lua5.2-dev
AND ;-)
sudo apt-get install lua5.2 (or apt-get update)

In my case, the system may have already had an (outdated) lua5.1, so that's why I was seeing the odd results from ./configure. the install -dev added the headers, but did not update binaries/libraries.

Once I added lua5.2, the ./configure found the 5.2 instance, and all went as expected.

Script is now being included when I run tshark - so past all the installation hurdles.

It could be, after all of this the data in the websocket I'm looking for was not deflated in the first place. Seems like I'm able to see the raw ascii from a json-rpc call with or without the lua module loaded. So this was an interesting, but possibly unneeded side journey. I'll let you know if I have any other observations, but for now, please consider this working - and with my thanks.

BR
~paul