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 this BIOS which does not support virtualization.
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*). On this page: https://packages.debian.org/sid/lisp/picolisp I see that there is a version: *17.12+20180218-1* available. Q: *Why isn't that latest package installed?* (Be gentle, my knowledge of Linux is very limited :-) Thx! /Arie 2018-04-17 13:57 GMT+02:00 Joe Bogner <joebog...@gmail.com>: > 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 > <https://software-lab.de/picoLisptgz> > 2. tar -zxvf picoLisp.tgz > 3. cd picoLisp/src > 4. make > 5 cd ../src64 > 6. make > > > ON WINDOWS BASH > 1. wget https://software-lab.de/picoLisp.tgz > 2. tar -zvxf picoLisp.tgz > 3. cd picoLisp > 4. scp user@domain:/path/to/bin/picoLisp bin/picoLisp > > You should be able to then run ./pil > > The key here is to build on linux and then transfer down to your windows > bash install. I used SCP to do the transfer > > Hope this helps. If you do not have access to a linux machine, you may > want to try out vagrant on windows. I can help with that if you'd like > > Also, several of us are active on #picoLisp -- if you are unfamiliar with > irc you can try here: https://webchat.freenode.net/ > > NOTE: WSL has an issue with file locking with the picoLisp DB. I will look > into that next > > Joe > > On Tue, Apr 17, 2018 at 7:25 AM, Alexander Burger <a...@software-lab.de> > wrote: > >> 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 /usr/lib/picolisp/lib.l >> (load "@lib/misc.l" "@lib/btree.l" "@lib/db.l" "@lib/pilog.l") >> >> which indeed calls #!/usr/bin/picolisp, but this is not meant to be >> called here. >> It is intended to be copied to - or linked from - /usr/bin. >> >> >> The other 'pil' looks different: >> >> exec ${0%/*}/bin/picolisp ${0%/*}/lib.l @ext.l "$@" >> >> and it is the main workhorse. It can be called locally >> >> $ ./pil + >> >> or with a relative or absolute path from anywhere >> >> $ /foo/bar/pil + >> >> and will always load everything from its local environment. >> >> ♪♫ Alex >> >> -- >> UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe >> > >
