Re: Latest (better) way to install PicoLisp on Windows WSL + Question

2018-05-25 Thread Arie van Wingerden 
Hi,

pil -version -bye
18.2.17

HTH,
   Arie

2018-05-25 10:37 GMT+02:00 O.Hamann :

> Thank you for updating your recipes, Arie!
>
> Could you please have a look and tell, which version of picolisp you got
> by this procedure?
>
> I think " pil -version -bye " or similar on the commandline should do.
>
> Kind regards.
>
>
> On 20.05.2018 14:44, Arie van Wingerden wrote:
>
>> Hi all,
>>
>> as I had to fight the first time to get WSL and PicoLisp working, I
>> now just overlooked the easy way ;-)
>>
>> The steps involved in installing WSL/Ubuntu and PicoLisp can now be
>> reduced to just:
>>
>> *Start the "Microsoft Store" App:
>> 01. search for "Ubuntu"
>> 02. install latest Ubuntu version (currently 18.04)
>> Ubuntu Bash shell opens during last step:
>> 01. you are asked for your User name and Password (twice)
>> 02. update Ubuntu (packages):sudo apt-get update
>> sudo apt-get upgrade
>> sudo apt-get dist-upgrade
>> sudo apt autoremove
>> sudo apt-get update
>> 04. go into your home directory:
>> cd ~
>> 05. install PicoLisp:
>> sudo apt install PicoLisp*
>>
>>
> --
> UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe
>

Re: Latest (better) way to install PicoLisp on Windows WSL + Question

2018-05-25 Thread O.Hamann 

Thank you for updating your recipes, Arie!

Could you please have a look and tell, which version of picolisp you got 
by this procedure?


I think " pil -version -bye " or similar on the commandline should do.

Kind regards.


On 20.05.2018 14:44, Arie van Wingerden wrote:

Hi all,

as I had to fight the first time to get WSL and PicoLisp working, I
now just overlooked the easy way ;-)

The steps involved in installing WSL/Ubuntu and PicoLisp can now be
reduced to just:

*Start the "Microsoft Store" App:
01. search for "Ubuntu"
02. install latest Ubuntu version (currently 18.04)
Ubuntu Bash shell opens during last step:
01. you are asked for your User name and Password (twice)
02. update Ubuntu (packages):sudo apt-get update
sudo apt-get upgrade
sudo apt-get dist-upgrade
sudo apt autoremove
sudo apt-get update
04. go into your home directory:
cd ~
05. install PicoLisp:
sudo apt install PicoLisp*



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

Re: Latest (better) way to install PicoLisp on Windows WSL + Question

2018-05-20 Thread Alexander Burger 
Hi Arie,

> Maybe this could put on the Wiki (and replace the Flinux thing, which
> appears to be broken).
> Is Alex the maintainer, or also a community thing to do this?

Anybody can do - just click on "Log in" and then "Create account".

♪♫ Alex

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

Re: Latest (better) way to install PicoLisp on Windows WSL + Question

2018-05-20 Thread Arie van Wingerden 
Hi all,

as I had to fight the first time to get WSL and PicoLisp working, I now
just overlooked the easy way ;-)

The steps involved in installing WSL/Ubuntu and PicoLisp can now be reduced
to just:


>
>
>
>
>
>
>
>
>
>
>
>
>
> *Start the "Microsoft Store" App: 01. search for "Ubuntu" 02. install
> latest Ubuntu version (currently 18.04)Ubuntu Bash shell opens during last
> step: 01. you are asked for your User name and Password (twice) 02. update
> Ubuntu (packages): sudo apt-get update sudo apt-get upgrade sudo apt-get
> dist-upgrade sudo apt autoremove sudo apt-get update 04. go into your home
> directory: cd ~ 05. install PicoLisp: sudo apt install PicoLisp*


After that everything just works fine so far.
So, WSL/Ubuntu is well behaving at the moment.

Side notes:
- I had issues with symlinks in WSL (found a lot of issues on the web as
well); maybe not yet ready for use
- question about /usr/lib vs. /usr/local/lib remains

Maybe this could put on the Wiki (and replace the Flinux thing, which
appears to be broken).
Is Alex the maintainer, or also a community thing to do this?

TIA,
   Arie

2018-05-20 12:58 GMT+02:00 Arie van Wingerden :

> As a follow-up I attach the output of env command.
>
> 2018-05-20 12:42 GMT+02:00 Arie van Wingerden :
>
>> Hi,
>>
>> as I found out that (already) the way WSL (Windows Subsystem for Linux)
>> works has changed in a big way, I needed to update things a bit. This
>> applies to Windows 10 with latest April 2018 update.
>>
>> If you did the installation the old way, you should:
>> - remove the Linux subsystem (PowerShell as admin):
>>   lxrun /uninstall
>> - backup any stuff you need from within the rootfs to Windows dir
>> - remove the rootfs:
>>   Use the program "Search Everything" from VoidTools to find
>>   the name "rootfs" and delete that folder
>>
>> New installation goes via Microsoft Store.
>>
>> Find new WSL + PicoLisp installation attached.
>>
>> QUESTION 1:
>> I now can start picolisp from within the installation directory, but even
>> after creating symlinks I cannot get pil or picolisp to run from anywhere
>> else.
>>
>> Any help?
>>
>> QUESTION 2:
>>
>> I also found out that using /usr/lib is deprecated and that instead
>> /usr/local/lib should be used. This also applies for other paths as well.
>>
>> Should this be changed in installation instructions and/or make files?
>>
>> /Arie
>>
>>
>>
>>
>>
>
>

Re: Latest (better) way to install PicoLisp on Windows WSL + Question

2018-05-20 Thread Arie van Wingerden 
As a follow-up I attach the output of env command.

2018-05-20 12:42 GMT+02:00 Arie van Wingerden :

> Hi,
>
> as I found out that (already) the way WSL (Windows Subsystem for Linux)
> works has changed in a big way, I needed to update things a bit. This
> applies to Windows 10 with latest April 2018 update.
>
> If you did the installation the old way, you should:
> - remove the Linux subsystem (PowerShell as admin):
>   lxrun /uninstall
> - backup any stuff you need from within the rootfs to Windows dir
> - remove the rootfs:
>   Use the program "Search Everything" from VoidTools to find
>   the name "rootfs" and delete that folder
>
> New installation goes via Microsoft Store.
>
> Find new WSL + PicoLisp installation attached.
>
> QUESTION 1:
> I now can start picolisp from within the installation directory, but even
> after creating symlinks I cannot get pil or picolisp to run from anywhere
> else.
>
> Any help?
>
> QUESTION 2:
>
> I also found out that using /usr/lib is deprecated and that instead
> /usr/local/lib should be used. This also applies for other paths as well.
>
> Should this be changed in installation instructions and/or make files?
>
> /Arie
>
>
>
>
>
LS_COLORS=rs=0:di=01;34:ln=01;36:mh=00:pi=40;33:so=01;35:do=01;35:bd=40;33;01:cd=40;33;01:or=40;31;01:mi=00:su=37;41:sg=30;43:ca=30;41:tw=30;42:ow=34;42:st=37;44:ex=01;32:*.tar=01;31:*.tgz=01;31:*.arc=01;31:*.arj=01;31:*.taz=01;31:*.lha=01;31:*.lz4=01;31:*.lzh=01;31:*.lzma=01;31:*.tlz=01;31:*.txz=01;31:*.tzo=01;31:*.t7z=01;31:*.zip=01;31:*.z=01;31:*.Z=01;31:*.dz=01;31:*.gz=01;31:*.lrz=01;31:*.lz=01;31:*.lzo=01;31:*.xz=01;31:*.zst=01;31:*.tzst=01;31:*.bz2=01;31:*.bz=01;31:*.tbz=01;31:*.tbz2=01;31:*.tz=01;31:*.deb=01;31:*.rpm=01;31:*.jar=01;31:*.war=01;31:*.ear=01;31:*.sar=01;31:*.rar=01;31:*.alz=01;31:*.ace=01;31:*.zoo=01;31:*.cpio=01;31:*.7z=01;31:*.rz=01;31:*.cab=01;31:*.wim=01;31:*.swm=01;31:*.dwm=01;31:*.esd=01;31:*.jpg=01;35:*.jpeg=01;35:*.mjpg=01;35:*.mjpeg=01;35:*.gif=01;35:*.bmp=01;35:*.pbm=01;35:*.pgm=01;35:*.ppm=01;35:*.tga=01;35:*.xbm=01;35:*.xpm=01;35:*.tif=01;35:*.tiff=01;35:*.png=01;35:*.svg=01;35:*.svgz=01;35:*.mng=01;35:*.pcx=01;35:*.mov=01;35:*.mpg=01;35:*.mpeg=01;35:*.m2v=01;35:*.mkv=01;35:*.webm=01;35:*.ogm=01;35:*.mp4=01;35:*.m4v=01;35:*.mp4v=01;35:*.vob=01;35:*.qt=01;35:*.nuv=01;35:*.wmv=01;35:*.asf=01;35:*.rm=01;35:*.rmvb=01;35:*.flc=01;35:*.avi=01;35:*.fli=01;35:*.flv=01;35:*.gl=01;35:*.dl=01;35:*.xcf=01;35:*.xwd=01;35:*.yuv=01;35:*.cgm=01;35:*.emf=01;35:*.ogv=01;35:*.ogx=01;35:*.aac=00;36:*.au=00;36:*.flac=00;36:*.m4a=00;36:*.mid=00;36:*.midi=00;36:*.mka=00;36:*.mp3=00;36:*.mpc=00;36:*.ogg=00;36:*.ra=00;36:*.wav=00;36:*.oga=00;36:*.opus=00;36:*.spx=00;36:*.xspf=00;36:
HOSTTYPE=x86_64
LESSCLOSE=/usr/bin/lesspipe %s %s
LANG=C.UTF-8
USER=arie
PWD=/home/arie
HOME=/home/arie
NAME=HP-Arie
XDG_DATA_DIRS=/usr/local/share:/usr/share:/var/lib/snapd/desktop
SHELL=/bin/bash
TERM=xterm-256color
SHLVL=1
LOGNAME=arie
PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/mnt/c/Program
 Files (x86)/Intel/iCLS Client:/mnt/c/Program Files/Intel/iCLS 
Client:/mnt/c/Windows/System32:/mnt/c/Windows:/mnt/c/Windows/System32/wbem:/mnt/c/Windows/System32/WindowsPowerShell/v1.0:/mnt/c/Program
 Files/Intel/Intel(R) Management Engine Components/DAL:/mnt/c/Program Files 
(x86)/Intel/Intel(R) Management Engine Components/DAL:/mnt/c/Program 
Files/Intel/Intel(R) Management Engine Components/IPT:/mnt/c/Program Files 
(x86)/Intel/Intel(R) Management Engine 
Components/IPT:/mnt/c/Windows/System32/OpenSSH:/mnt/e/_utils_/scripts:/mnt/c/Users/HP/AppData/Local/Microsoft/WindowsApps:/mnt/c/Users/HP/AppData/Local/Microsoft/WindowsApps:/snap/bin
LESSOPEN=| /usr/bin/lesspipe %s
_=/usr/bin/env

Latest (better) way to install PicoLisp on Windows WSL + Question

2018-05-20 Thread Arie van Wingerden 
Hi,

as I found out that (already) the way WSL (Windows Subsystem for Linux)
works has changed in a big way, I needed to update things a bit. This
applies to Windows 10 with latest April 2018 update.

If you did the installation the old way, you should:
- remove the Linux subsystem (PowerShell as admin):
  lxrun /uninstall
- backup any stuff you need from within the rootfs to Windows dir
- remove the rootfs:
  Use the program "Search Everything" from VoidTools to find
  the name "rootfs" and delete that folder

New installation goes via Microsoft Store.

Find new WSL + PicoLisp installation attached.

QUESTION 1:
I now can start picolisp from within the installation directory, but even
after creating symlinks I cannot get pil or picolisp to run from anywhere
else.

Any help?

QUESTION 2:

I also found out that using /usr/lib is deprecated and that instead
/usr/local/lib should be used. This also applies for other paths as well.

Should this be changed in installation instructions and/or make files?

/Arie
Install PicoLisp on Windows 10 64 bit using WSL (Windows Subsystem for Linux)
=

Open a PowerScript shell as Admin:
01. Enable-WindowsOptionalFeature -Online -FeatureName 
Microsoft-Windows-Subsystem-Linux
(reboot if required)
02. Get-WindowsOptionalFeature -FeatureName 
Microsoft-Windows-Subsystem-Linux -Online 
(reboot if required)

Start the "Microsoft Store" App:
01. search for "Ubuntu"
02. install latest Ubuntu version (currently 18.04)

Ubuntu terminal opens during last step:
01. you are asked for your User name and Password (twice)
02. update Ubuntu (packages):   
sudo apt-get update
sudo apt-get upgrade
sudo apt-get dist-upgrade
sudo apt autoremove
sudo apt-get update
03. install a few needed packages:
sudo apt install make
sudo apt install make-guile
sudo apt install gcc
sudo apt-get install gcc-multilib g++-multilib
sudo apt-get install libssl-dev 
04. go into your home directory
cd ~
05. download and unpack PicoLisp sources:
wget https://software-lab.de/picoLisp.tgz
tar xfz picolisp.tgz
rm picolisp.tgz
06. download and unpack platform specific file for 64 bit:
cd picolisp/
wget http://software-lab.de/x86-64.linux.tgz
tar xfz x86-64.linux.tgz
rm x86-64.linux.tgz
07. install PicoLisp 64 bit:
(cd src64; make)
(cd src; make tools gate)
10. create symlinks:
sudo ln -s / /usr/lib/picolisp
sudo ln -s /usr/lib/picolisp/bin/picolisp /usr/bin
sudo ln -s /usr/lib/picolisp/bin/pil /usr/bin
sudo ln -s //man/man1/picolisp.1 
/usr/share/man/man1
sudo ln -s //man/man1/pil.1 
/usr/share/man/man1
sudo ln -s / /usr/share/picolisp
11. add library to ldconfig:
sudo ldconfig /usr/lib