Products > Test Equipment

Open source lxi-tools and liblxi v1.0 released for GNU/Linux

<< < (55/67) > >>

lundmar:

--- Quote from: N0NB on March 18, 2018, 11:28:49 am ---Arghh!

I'm getting tripped up by Lua in updating my SlackBuild script for lxi-tools 1.19.  The configure script halts as Lua5.2 is not found and the SlackBuilds.org site has version 5.1.5 available.  I presume this version is too old for various and sundry reasons?

I've never used Lua knowingly, but I found when writing a SlackBuild script for Hamlib (someone else contributed Swig Lua bindings).  The impression I got is that Lua seems to be rather incompatible between minor versions.  I hope I am wrong about that.

I suppose I can try installing Lua 5.1.5 and see if lxi-tools will build and run against it.

--- End quote ---

There is an overview of Lua 5.x version changes here: https://www.lua.org/versions.html

For now I think it will work to require minimum 5.1. Sure there are some nice features added in 5.2 and 5.3 but I think most can do without them. In case a script needs e.g. Lua 5.3 it can add a check and opt out in case it is not available.

N0NB:

--- Quote from: lundmar on March 18, 2018, 02:04:53 pm ---Perfectly fine patch  :-+

I simply had it fixed at Lua 5.2 but I assume it will work fine with all 5.x. If you feel like it I invite you to create a github pull request to push your change upstream. Or I can apply the patch on your behalf.
--- End quote ---

Go ahead and apply it, Martin.


--- Quote from: lundmar on March 18, 2018, 02:04:53 pm ---
--- Quote from: N0NB on March 18, 2018, 12:29:11 pm ---and run autoreconf --force -v --install to rebuild configure.

--- End quote ---

FYI - for convenience, same as running ./autogen.sh

--- End quote ---

As I'm working from your release tarballs, that script is not included, but it's no more complicated to simply call autoreconf from the SlackBuild script.   :)



--- Quote from: lundmar on March 18, 2018, 02:04:53 pm ---Those are warnings that are yet to be fixed. You can ignore them for now. To test you could start by running the basic Lua test script:


--- Code: ---lxi run test/basic-tests.lua

--- End code ---

--- End quote ---

I see that is in the Git repository but not in the 1.19 release tarball.  It would be useful to include the test script in the 1.20 release tarball.   :-+

Edit:

The basic-test.lua script ran without error using Lua 5.1.5, so it will likely work just fine.

lundmar:

--- Quote from: N0NB on March 18, 2018, 05:05:08 pm ---
--- Quote from: lundmar on March 18, 2018, 02:04:53 pm ---Perfectly fine patch  :-+

I simply had it fixed at Lua 5.2 but I assume it will work fine with all 5.x. If you feel like it I invite you to create a github pull request to push your change upstream. Or I can apply the patch on your behalf.
--- End quote ---

Go ahead and apply it, Martin.

--- End quote ---

I tested the change on Ubuntu/Debian and unfortunately it fails so a bit more rework is required. Debian/Ubuntu supports parallel lua installations which introduces separate named pkgconfig lookup names, not "lua" but "lua5.2", "lua5.3" etc. basically invalidating any possibility for a single version check.

EDIT: Fixed in https://github.com/lxi-tools/lxi-tools/commit/beddd9316a3e0cc46ad9023013a31ae94b3c4f33


--- Quote from: N0NB on March 18, 2018, 05:05:08 pm ---I see that is in the Git repository but not in the 1.19 release tarball.  It would be useful to include the test script in the 1.20 release tarball.   :-+

--- End quote ---

Oh, I've forgot to include them.

EDIT: Fixed


--- Quote from: N0NB on March 18, 2018, 05:05:08 pm ---Edit:

The basic-test.lua script ran without error using Lua 5.1.5, so it will likely work just fine.

--- End quote ---

Great - lets assume it works.

N0NB:
An interesting issue I am seeing has to do with my main Slackware 14.2 desktop which is running the avahi daemon cannot discover the 'scope.  However, in a Slackware 14.2 VM where I have avahi installed for building lxi-tools, but not running, I can access the 'scope just fine.   :-//

I know that avahi is working as I am using it to play audio over to my MythTV box using PulseAudio.  Also the avahi browser utility shows a bunch of mDNS stuff from the network.

I have to admit that I am far from knowledgeable regarding mDNS and even less so in beginning to troubleshoot it.

lundmar:

--- Quote from: N0NB on March 20, 2018, 12:26:44 pm ---An interesting issue I am seeing has to do with my main Slackware 14.2 desktop which is running the avahi daemon cannot discover the 'scope.  However, in a Slackware 14.2 VM where I have avahi installed for building lxi-tools, but not running, I can access the 'scope just fine.   :-//

I know that avahi is working as I am using it to play audio over to my MythTV box using PulseAudio.  Also the avahi browser utility shows a bunch of mDNS stuff from the network.

I have to admit that I am far from knowledgeable regarding mDNS and even less so in beginning to troubleshoot it.

--- End quote ---

I assume your have built lxi-tools on each machine in which case you have to make sure that libavahi-core-dev libavahi-common-dev libavahi-client-dev or similar is installed so that the configure script enables the mDNS feature.

For some unknown reason I decided to make mDNS an optional feature. I think I will likely change it to a mandatory feature in the future.

Navigation

[0] Message Index

[#] Next page

[*] Previous page

There was an error while thanking
Thanking...
Go to full version
Powered by SMFPacks Advanced Attachments Uploader Mod