Re: Success at last!

[Arie van Wingerden]

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
> > Subject: Success at last!
> > [...]
> > Attached a document with what I did.
> > [...]
>
>
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. PSA: Get-WindowsOptionalFeature -FeatureName 
Microsoft-Windows-Subsystem-Linux -Online 
4. reboot
5. PSA: lxrun /install /y

Upgrade Linux to latest version:
1. BSH: sudo apt-get update
2. BSH: sudo apt-get upgrade
3. BSH: sudo apt-get dist-upgrade
4. BSH: sudo apt-get update

Then install PicoLisp:
1. download latest PicoLisp package here:
   https://packages.debian.org/sid/lisp/picolisp
   into a folder in WSL file system
2. download libssl1.1 from here:
   https://packages.debian.org/stretch/amd64/libssl1.1/download   
   into a folder in WSL file system
3. BSH: sudo dpkg -i libssl
4. BSH: sudo dpkg -i picolisp

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: Success at last!

[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
> Subject: Success at last!
> [...]
> Attached a document with what I did.
> [...]

PԔ � )mX�����zV�u�.n7�

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
>

Now WITH attachment

[Arie van Wingerden]

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. PSA: Get-WindowsOptionalFeature -FeatureName 
Microsoft-Windows-Subsystem-Linux -Online 
4. reboot
5. PSA: lxrun /install /y

Upgrade Linux to latest version:
1. BSH: sudo apt-get update
2. BSH: sudo apt-get upgrade
3. BSH: sudo apt-get dist-upgrade
4. BSH: sudo apt-get update

Then install PicoLisp:
1. download latest PicoLisp package here:
   https://packages.debian.org/sid/lisp/picolisp
   into a folder in WSL file system
2. download libssl1.1 from here:
   https://packages.debian.org/stretch/amd64/libssl1.1/download   
   into a folder in WSL file system
3. BSH: sudo dpkg -i libssl
4. BSH: sudo dpkg -i picolisp

Success at last!

[Arie van Wingerden]

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

[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: Follow-up last email

[Philipp Geyer]

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

[Arie van Wingerden]

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 architecture?

Sorry, I am not good at Linux :-)

TIA,
/Arie

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

Follow-up last email

[Arie van Wingerden]

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

[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

Re: PicoLisp on Windows

[Arie van Wingerden]

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

But on this page: http://www.picolisp.com/wiki/?flinuxpicolisp it says:

>
>- patch the Makefile
>
>
>- patch tab.c
>
>
>- (optional) patch net.c​
>
> Do I need those patches even when using WSL???

/Arie



2018-04-16 18:33 GMT+02:00 Arie van Wingerden :

> Hi Joe,
>
> ok. I'll try WSL then.
> Will let know about my findings.
> Maybe others can profit as well (Philip?)
>
> Thx
> /Arie
>
> Op ma 16 apr. 2018 18:10 schreef Joe Bogner :
>
>> Hi Arie,
>>
>> I would like to send a more detailed reply later. I'm the author of the
>> flinux writeup. It's been a few years and things don't work as nicely as
>> they did back then.
>>
>> I retested some the writeup today. I was unable to get the flinux static
>> option working. I was able to get flinux dynamic working, but the archlinux
>> distro is out of date and I wouldn't recommend going down that path any
>> more.
>>
>> After the flinux experiment, I did do some work with a precusor to WSL,
>> midipix[1], which seems to still work.
>>
>> The last time I tried WSL it had issues with database locking. I need to
>> do some more experiments on WSL now that I have a Win-10 machine
>>
>> I have another option that I've used over the years, midipix, but it's
>> out of date as well.
>>
>> Your best bet is probably to go with WSL or cygwin/msys for now.
>>
>> When I first put all this together, there was little interest. It sounds
>> like there is more interest now so I'll see if I can dust it off and bring
>> it up to date
>>
>> Thanks,
>> Joe
>>
>>
>> On Mon, Apr 16, 2018 at 11:06 AM, Philipp Geyer 
>> wrote:
>>
>>> Based on the instructions on the site, it looks like the next steps are
>>> to build pil on Linux, and then run the linux binary on Windows through
>>> flinux.
>>>
>>> I have not tried pil in WSL yet (my only Windows text machine is Win7),
>>> and I don't think that's a solution for my specific problem (to have a
>>> simple environment for an end user with no technical experience) but I
>>> have had some luck building pil with mingw/msys which provide a POSIX
>>> compatibility layer on top of Windows. I have not (yet) managed to get
>>> anything 100% working, but I'm optimistic. Currently if I build with
>>> msys2, I can get an executable which I believe passed the tests, but
>>> requires msys2.dll to be in the library path (which includes the
>>> executable directory of course) but I believe that if you build with
>>> mingw without msys, it builds against msvcrt directly, and links in the
>>> compatibility layer. This is what I haven't managed yet.
>>>
>>> As I said though, I'm optimistic, and it's something I need for my
>>> project.
>>>
>>> Philipp Geyer/Nistur
>>>
>>> --
>>> UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe
>>>
>>
>>

Re: signify

[Christian Kellermann]

* 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 tool to sign and verify files. That's what they use to sign the
packages and the installer.

-- 
May you be peaceful, may you live in safety, may you be free from
suffering, and may you live with ease.

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