autoconf-archive-maintainers
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: SOLVED Re: Prefix bug in ax_lua?


From: Tim Perkins
Subject: Re: SOLVED Re: Prefix bug in ax_lua?
Date: Mon, 09 Apr 2018 13:42:17 +0000

Hi Nate, 

Glad you got things working. Sounds like you did a pretty thorough analysis! The macro actually uses a little Lua script to deal with the prefix, and that seemed like a likely place things could be going wrong. A good guess, I guess. Anyway, I didn't realize you work on Hamlib. Never used it myself, but it seems pretty neat.

Glad I could help!


On Mon, Apr 9, 2018, 8:12 AM Nate Bargmann <address@hidden> wrote:
* On 2018 08 Apr 22:50 -0500, Tim Perkins wrote:

Thanks for your help, Tim.

To answer your other email, I am running Slackware 14.2 with Lua 5.2/5.3
built from the scripts provided at Slackbuilds.org and I am trying to
build bindings for my own SlackBuild script for Hamlib which now has Lua
language bindings available.

These are not distribution provided build scripts, but are submitted by
volunteers like myself.  I did find a bug in the respective
package-config files provided for each so those have been corrected.

The macro Hamlib is using is serial 39 which appears to differ only in
that URLs are http rather than https.

> Could you also try printing "package.path" from inside the Lua
> interpreter?

> print(package.path)
/usrshare/lua/5.2/?.lua;/usrshare/lua/5.2/?/init.lua;/usrlib64/lua/5.2/?.lua;/usrlib64/lua/5.2/?/init.lua;./?.lua

> print(package.path)
/usrshare/lua/5.3/?.lua;/usrshare/lua/5.3/?/init.lua;/usrlib64/lua/5.3/?.lua;/usrlib64/lua/5.3/?/init.lua;./?.lua;./?/init.lua

It looks like the bug is sitting right there!

> And maybe check if the LUA_PATH environment variable is being set
> somewhere?

No it's not, at least that I could find.

I dug into the build scripts for Lua and found that the path was being
modified in src/luaconfig.h and a trailing '/' was omitted in the sed
command.  I've corrected it locally and will be submitting a patch to
the script maintainers to correct this.  I have tested my local build of
Hamlib and the binding is now working correctly with the correct paths:

> print(package.path)
/usr/share/lua/5.2/?.lua;/usr/share/lua/5.2/?/init.lua;/usr/lib64/lua/5.2/?.lua;/usr/lib64/lua/5.2/?/init.lua;./?.lua

> print(package.path)
/usr/share/lua/5.3/?.lua;/usr/share/lua/5.3/?/init.lua;/usr/lib64/lua/5.3/?.lua;/usr/lib64/lua/5.3/?/init.lua;./?.lua;./?/init.lua

Which looks much better!

Thanks for your help in pointing me toward the right direction, which I
likely should have done first.

- Nate

--

"The optimist proclaims that we live in the best of all
possible worlds.  The pessimist fears this is true."

Web: http://www.n0nb.us  GPG key: D55A8819  GitHub: N0NB

reply via email to

[Prev in Thread] Current Thread [Next in Thread]