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

[Thorsten Jolitz]

Joe Bogner  writes:

Hey Joe,
>
> 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

maybe I don't really understand what you mean by transfer down, but in
my case (WSL with Suse) I just opened the Suse "App" and then installed
picolisp the same way I do on a standalone Linux System, and it works
just fine.

BTW isn't WSL the best thing (produced by microsoft) ever since sliced bread? 
;-)
Now I have Linux with Tmux, Emacs and PicoLisp on my average Win10
Notebook (only Tmux needs a little hack to work) - as an official
Windows App.

I really like it ...

> 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. 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
>  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
>
>

-- 
cheers,
Thorsten


-- 
UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe

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

[Alexander Burger]

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 :)

♪♫ Alex

-- 
UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe

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

[Arie van Wingerden]

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 anyway.

Retried install of PicoLisp. Same error.

Tried to install libssl1.1 using apt-get install, which didn't seem
possible.
So, I downloaded it's deb package and installed it with dpkg.

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?

Now I'll try if everything works :-)

Thx. for all the help (also the others in the community).
I'll chime in on IRC as well.

Alex: keep up the good work! PicoLisp is great!

Now I'll have to learn it, but luckily I know quite a lot about Scheme,
Racket, Lisp and Clojure already.
Having an integrated db and a gui is impressive, a fresh breeze compared to
a lot of bloatware.

Thx. again,
/Arie






2018-04-17 16:56 GMT+02:00 Alexander Burger :

> 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:
> >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?*
>
> Yeah, good question. Debian packages are usually quite outdated.
>
> If you install the "testing" version of Debian, you get
>
>$ apt-cache policy picolisp
>picolisp:
>  Installed: 17.12+20180218-1
>  Candidate: 17.12+20180218-1
>  Version table:
> *** 17.12+20180218-1 500
>500 http://ftp.de.debian.org/debian buster/main amd64 Packages
>500 http://ftp.de.debian.org/debian sid/main amd64 Packages
>100 /var/lib/dpkg/status
>
> ♪♫ Alex
>
> --
> UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe
>

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

[Alexander Burger]

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:
>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?*

Yeah, good question. Debian packages are usually quite outdated.

If you install the "testing" version of Debian, you get

   $ apt-cache policy picolisp
   picolisp:
 Installed: 17.12+20180218-1
 Candidate: 17.12+20180218-1
 Version table:
*** 17.12+20180218-1 500
   500 http://ftp.de.debian.org/debian buster/main amd64 Packages
   500 http://ftp.de.debian.org/debian sid/main amd64 Packages
   100 /var/lib/dpkg/status

♪♫ Alex

-- 
UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe

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

[Arie van Wingerden]

​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 :

> 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. 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 
> 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
>>
>
>

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

[Joe Bogner]

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. 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 
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
>

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

[Alexander Burger]

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

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

[Arie van Wingerden]

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 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
> #!/mnt/e/_utils/src/picolisp/picolisp_install/picolisp/bin/picolisp
> /mnt/e/_utils/src/picolisp/picolisp_install/picolisp/lib/lib.l
> or, you can just try running picolisp and loading lib.l and the other
> libraries which pil loads afer that manually
>
> Phil
>
> --
> UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe
>

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

[Philipp Geyer]

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
#!/mnt/e/_utils/src/picolisp/picolisp_install/picolisp/bin/picolisp 
/mnt/e/_utils/src/picolisp/picolisp_install/picolisp/lib/lib.l
or, you can just try running picolisp and loading lib.l and the other
libraries which pil loads afer that manually

Phil

-- 
UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe

PicoLisp on Windows WSL first tryout fails ...

[Arie van Wingerden]

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 root root   4096 Apr 17 12:26 .
drwxrwxrwx 0 root root   4096 Apr 17 12:05 ..
-rwxrwxrwx 1 root root 284540 Apr 17 12:26 picolisp
-rwxrwxrwx 1 root root107 Apr 17 12:05 pil
-rwxrwxrwx 1 root root907 Apr 17 12:05 pilIndent
-rwxrwxrwx 1 root root266 Apr 17 12:05 pilPretty
-rwxrwxrwx 1 root root362 Apr 17 12:05 psh
-rwxrwxrwx 1 root root   1307 Apr 17 12:05 replica
-rwxrwxrwx 1 root root696 Apr 17 12:05 vip
-rwxrwxrwx 1 root root   2362 Apr 17 12:05 watchdog
arie@HP-Arie:/mnt/e/_utils_/src/picolisp/picolisp_install/picoLisp/bin$
/pil
-bash: ./pil: /usr/bin/picolisp: bad interpreter: No such file or directory
arie@HP-Arie:/mnt/e/_utils_/src/picolisp/picolisp_install/picoLisp/bin$

Please help :-)

TIA
/Arie