|Strange problem trying to use LDT on second machine [message #1072350]
||Mon, 22 July 2013 15:19
| Burt Bicksler
Registered: July 2013
I'm new to Lua, and LDT. What I've seen with LDT is great but I'm having some challenges, the the current frustration is trying to duplicate the configuration for a project on my notebook that I finally got running on my desktop machine.
Both machines are running Ubuntu 12.04 LTS. I'm working with a project that uses lgi, and because I couldn't get the internal interpreters to work and play well with lgi I followed a suggestion to use the Lua version that is installed on my system.
I set up both Lua 5.2 and Lua 5.1 which I have on my desktop.
Note that from the command line I was able to build and test some simple GUI LUA programs with no problems. And after much fiddling I was able to get things set up with the external interpreters so that I could build using Lua 5.2 and run the application with no problem from LDT.
Of course I couldn't debug since I don't have a luasocket module for 5.2 yet, but I could run the applications in LDT.
So next I wanted to set up the same thing on the notebook where I'm doing most of the actual devlopment work.
As far as I can see I've duplicated the configuration the same as on the desktop but I'm hitting some issues on the notebook:
When I attempt to run a program that previously worked in LDT (non-Gui, just hello world) If I use internal Lua 5.1 it works, including debugging as before. But if I use the internal Lua 5.1 I get the following error:
Exception in thread "main" java.lang.UnsatisfiedLinkError: /home/bbick/.eclipse/org.eclipse.platform_3.7.0_155965261/configuration/org.eclipse.osgi/bundles/202/1/.cp/lib/libjnlua52.so: liblua52.so: cannot open shared object file: No such file or directory
at java.lang.ClassLoader$NativeLibrary.load(Native Method)
I've searched and liblua52.so is found here:
Note that this particular problem happens on both the desktop and the notebook. If I use the Ubuntu Lua 5.2 it runs fine in LDT.
Also there is no issue using the Ubuntu Lua 5.2 from the command line. How do I go about tracking down the source of this particular problem?
The other problem is that the lgi test GUI application.
I can now get that to run fine in LDT on the desktop and notebook using the external Ubuntu Lua 5.2.
But with the LDT internal Lua 5.2 I get the same error as above, and possible others if that is fixed. Is there a chance that with the build path set that I could get lgi working with the internal Lua 5.2 to get debugging working, or is it not worth exploring?
Thanks for any suggestions. (I had done a search for anything related to liblua52.so in the forum and on Goole but haven't found anything useful).
Powered by FUDForum
. Page generated in 0.09759 seconds