./configure gets version mismatch if lpeg and lua are different versions

[Nomarian]

Problem

./configure tries to guess the latest versions of lua and lpeg, but if latest lua is 5.4 and lpeg is for 5.3 you get a version mismatch with the error message and a failure in running vis itself.

for now the fix is going into config.mk and modifying the file by hand and setting equal versions

Steps to reproduce

./configure and your lpeg is not the same as your lua version.

vis version (vis -v)

0.9

Terminal name/version

No response

$TERM environment variable

No response

[mcepl]

On Sat Feb 1, 2025 at 9:30 AM CET, lan Nomar wrote: ./configure tries to guess the latest versions of lua and lpeg, but if latest lua is 5.4 and lpeg is for 5.3 you get a version mismatch with the error message and a failure in running vis itself. for now the fix is going into config.mk and modifying the file by hand and setting equal versions

Should we encourage using libraries for different versions than Lua itself? Is it supported by Lua? Matěj

…

-- http://matej.ceplovi.cz/blog/, @***@***.*** GPG Finger: 3C76 A027 CA45 AD70 98B5 BC1D 7920 5802 880B C9D8 We understand our competition isn’t with Caldera or SuSE--our competition is with Microsoft. -- Bob Young of Red Hat (August 1, 1999) http://www.linuxjournal.com/article/3553

[Nomarian]

I don't think so, the error message of "version mismatch" is not set anywhere in vis itself (rudimentary search via rg), so this might be an error message of lua/lpeg itself?

Frankly, I don't know why lpeg is even a build requirement, the lexers is entirely handled by a lua script no?

[mcepl]

Frankly, I don't know why lpeg is even a build requirement, the lexers is entirely handled by a lua script no?

LPEG is not a building requirement: vis can work (in limited capacity) without it, and liblpeg is not dynamically linked to the vis binary.

We are talking about the configure option --enable-lpeg-static (build with LPeg static linking), which obviously requires lpeg to link it statically in.