-
-
Notifications
You must be signed in to change notification settings - Fork 28
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Suggestion for asterisk: use lua package version from system #11
Comments
Thanks for the report. Unfortunately I'm not sure there is anything we can realistically do on the packaging end. The upstream Asterisk build system seems to detect the lowest available version of Lua rather than the highest. While it does sort of work if you build on a system with only a newer Lua, I've seen reports of example configs not working with newer Lua because many of them have 5.1 specific syntax. Note that the AUR package doesn't actually depend on Lua at all, it is an optional depend because it can function without. For that case you are free to provide whatever Lua you want to try. I assume this report is largely about the pre-built package I provide in the I'll keep this open to look into building on a 5.4 only system, but I have an idea that's going to break some people's configs, possible even the supplied example ones. |
Thank you for your valuable input. On my system the order of lua detection looks correct, and with lua52 and lua51 installed it built pbx_lua.so with lua52 dependency.
then I ran ./bootstrap.sh to regenerate the ./configure script as described in https://wiki.asterisk.org/wiki/display/AST/Build+System+Architecture . In my opinion the best solution would be to provide two packages - one built for lua51 and the second one for lua. |
Hello,
would it be feasible to configure the build for asterisk to use the lua package version provided by Arch Linux? Currently it uses lua 5.1, but when I build from AUR with only lua (currently: 5.4) package installed it uses exactly this version.
Many thanks for your work!
The text was updated successfully, but these errors were encountered: