Newlisp won't run on 64bit Kubuntu? (13.04)

Started by Owen_R, October 24, 2013, 05:55:50 AM

Previous topic - Next topic

Owen_R

(This doesn't seem like quite the right place to ask this kind of question, but I didn't see any better category...?)





So I just installed Kubuntu (13.04) on both my computers...



old desktop     - 32bit processor   - 32bit OS

newer netbook   - 64bit processor   - 64bit OS



I installed newlisp on both.



(By downloading:



http://www.newlisp.org/downloads/newlisp_10.5.4-utf8_i386.deb">http://www.newlisp.org/downloads/newlis ... 8_i386.deb">http://www.newlisp.org/downloads/newlisp_10.5.4-utf8_i386.deb



and then using qapt-deb-installer on that downloaded file.



Same version for both computers, because there is only a 32bit version, of course.)





Now newlisp works on the old desktop.



But on the newer netbook, I get this problem:




~$ newlisp
bash: /usr/bin/newlisp: No such file or directory


Check it's installed...




~$ sudo apt-get install newlisp
[sudo] password for o1:
Reading package lists... Done
Building dependency tree      
Reading state information... Done
newlisp:i386 is already the newest version.
0 upgraded, 0 newly installed, 0 to remove and 1 not upgraded.


Apparently so, but it still doesn't work:




~$ newlisp
bash: /usr/bin/newlisp: No such file or directory


Is there something wrong with the executable?




~$ cd /usr/bin/

/usr/bin$ ls -l | grep newlisp
lrwxrwxrwx 1 root root          23 Sep 30 22:58 newlisp -> /usr/bin/newlisp-10.5.4*
-rwxr-xr-x 1 root root       19315 Sep 30 22:58 newlispdoc*
-rwxr-xr-x 1 root root      332832 Sep 30 22:58 newlisp-10.5.4*
-rwxr-xr-x 1 root root       50758 Sep 30 22:58 newlisp-edit*


That's exactly the same as on the old desktop where is *does* work...



Any ideas?

conan

#1
What happens if you try running it directly, not through the symbolic link:



/usr/bin/newlisp-10.5.4



What does say 'file' command about that file?



The reported error looks like a shell/file issue, but you show the file there... Strange!

Owen_R

#2
Actually, it did exactly the same thing when I ran it directly like that. (I forgot to mention I had already tried that.)



So yeah, it claimed a file that was clearly *there*, didn't exist.



Anyway, I just built it from source.



Let's see, along the way I got...



"newlisp.h:135:19: fatal error: ffi.h: No such file or directory"



So I did the



make -f makefile_linuxLP64_utf8



version instead...



And then it said:



"newlisp.c:32:31: fatal error: readline/readline.h: No such file or directory"



So I had to



sudo apt-get install libreadline-dev



first...



And then a simple:



make -f makefile_linuxLP64_utf8

sudo make install



*did* finally just work.



But while I (pretty much) understand that process in *retrospect*, I prolly woulda given up if I hadn't happened to be lucky enough to have someone around to help me...



So I hope that information might make it possible for someone to fix the simple .deb package install for less experienced users like me who just wanna play around with newlisp.



Anyway, thanks for trying to help! ^^

rickyboy

#3
Quoteit claimed a file that was clearly *there*, didn't exist.

That happens with any 32-bit binary on a 64-bit Linux.  You either had to get a 64-bit package (e.g. deb) or rebuild from sources.  So, you made a correct decision.  Glad it worked out for you eventually.
(λx. x x) (λx. x x)

Owen_R

#4
Quote from: "rickyboy"
Quoteit claimed a file that was clearly *there*, didn't exist.

That happens with any 32-bit binary on a 64-bit Linux.


Really?



Would it have worked if I had the 32bit libraries it required, then?



[EDIT: Yes, that *is* kinda a non-sequitor question; It's something someone else told me was the way it works in general with 32bit stuff on 64bit Linux...]