Re: Success at last!

Hi David, I did attach in a later post, but as a courtesy, here it is :-) /Arie 2018-04-17 17:52 GMT+02:00 Loyall, David : > FYI, Arie, I didn't receive any attachment with your email. > > > From: Arie van Wingerden > > Sent: Tuesday, April 17, 2018 10:02 AM > >

Re: PicoLisp on Windows WSL first tryout fails ...

Hi Arie, > After that picolisp installed just fine. So far, so good! > > I notice that the package name is picolisp17.12+20180218-1, which seems to > be version 17.12 (looking at that name), > but "pil -version" says 18.2.17. How about that? That's OK, an intermediate version release :) ♪♫

RE: Success at last!

FYI, Arie, I didn't receive any attachment with your email. > From: Arie van Wingerden > Sent: Tuesday, April 17, 2018 10:02 AM > Subject: Success at last! > [...] > Attached a document with what I did. > [...] PԔ � )mX�����zV�u�.n7�

Re: PicoLisp on Windows WSL first tryout fails ...

Hi Alexander, just posted my success story :-) I just downloaded the latest PicoLisp deb package and tried to install with dpkg. It failed, because it missed libssl1.1. After quite a bit of searching I thought I had to upgrade Linux (apt-get upgrade). So, I did that, because it wouldn't hurt

Now WITH attachment

Install PicoLisp on Windows 10 NOTE: - PSA = PowerShell as Administrator (right-click Windows | PowerShell (admin) - BSH = bash shell (Windows+r | bash | OK) Install and enable WSL: 1. PSA: Enable-WindowsOptionalFeature -Online -FeatureName Microsoft-Windows-Subsystem-Linux 2. reboot 3.

Success at last!

Hi all, after quite a lot of arm wrestling with Linux I got PicoLisp version 18.2.17 to work! Attached a document with what I did. Hope that might help others as well! Thx! /Arie

Re: PicoLisp on Windows WSL first tryout fails ...

Hi Arie, > So, I tried it another way by just installing the Debian package PicoLisp: >sudo apt-get install picolisp > and indeed, now starting pil just works. However, it is an older version ( > *15.11.0*). Yes, it is Debian "stable". > On this page: >

Re: PicoLisp on Windows WSL first tryout fails ...

​Hi Joe, going the Vagrant way will be difficult. On this (older HP) PC I've tried many times to get Linux to run in e.g. VirtualBox and also VMWare. To date I can't get it to work. In the past I ran Linux quite a few times under VirtualBox and VMWare on other computers. Maybe it has to do with

Re: PicoLisp on Windows WSL first tryout fails ...

Arie, For WSL, you need to build picoLisp on a linux machine and then transfer it down. You can follow the download/install instructions, but here is generally what I did ON LINUX 1. wget https://software-lab.de/picoLisp.tgz 2. tar -zxvf picoLisp.tgz 3. cd picoLisp/src 4. make 5 cd ../src64 6.

Re: PicoLisp on Windows WSL first tryout fails ...

Hi Philipp, Arie, > pil is just a wrapper around picolisp, it loads a few libraries etc as Yes, but > standard, but it relies on the intepreter being at /usr/bin/picolisp, This is not completely correct. Note that there are two 'pil's in the distribution: One in bin/ #!/usr/bin/picolisp

Re: PicoLisp on Windows WSL first tryout fails ...

Hi Philip, just copied all stuff from bin to /usr/bin/picolisp and then tried to run pil. But same error shows up. So I guess I'll have to wait a bit for the PicoLisp guru's ;-) Thx anyway. Apperciate it! /Arie 2018-04-17 13:01 GMT+02:00 Philipp Geyer : > Hi Arie, > > pil

Re: Follow-up last email

Ahh, so my suggestion won't work then. Does WSL have 'file'? Could you try running file ./picolisp and seeing what it spits out? Phil -- UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe

Last mail in this row :-)

Hi, my Windows system specs are: Windows 10 Pro 64 bit Version 1709 Build 16299.371 CPU Intel Core-I5 2500 I need some advice for what the best PicoLisp version I should compile and the steps required. I guess now that the "bad executable" has something to do with the way I compiled ...? Bad

Re: PicoLisp on Windows WSL first tryout fails ...

Hi Arie, pil is just a wrapper around picolisp, it loads a few libraries etc as standard, but it relies on the intepreter being at /usr/bin/picolisp, which it is not in your case. You can either try changing the shebang at the top of pil from #!/usr/bin/picolisp /usr/lib/picolisp/lib.l to

Follow-up last email

Also: arie@HP-Arie:/mnt/e/_utils_/src/picolisp/picolisp_install/picoLisp/bin$ /picolisp -bash: ./picolisp: cannot execute binary file: Exec format error

PicoLisp on Windows WSL first tryout fails ...

Hi, I did 2 things: 1) installed WSL and PicoLisp succesful 2) created doceumentation of how to do that Building went OK; no errors. However, I cannot run pil itself; see terminal output here: arie@HP-Arie:/mnt/e/_utils_/src/picolisp/picolisp_install/picoLisp/bin$ ls -al total 292 drwxrwxrwx 0

Re: PicoLisp on Windows

After installing WSL I'm going to install/make PicoLisp. I guess I now should use the default installation steps here: https://picolisp.com/wiki/?home > ​Otherwise, grab the latest version - [picoLisp.tgz] - unpack it, > follow the instructions from the INSTALL file, and then check out the >

Re: signify

* Henrik Sarvell [180416 22:12]: > Hi Mike, > > I get the impression this is a way to check if a file has not been tampered > with as opposed to actually encrypting and decrypting a file or? Yes, this is a variant of OpenBSD's signify(1): https://man.openbsd.org/signify A