Re: PicoLisp on windows

[Guido Stepken]

Sure. But tell me: What is faster? A tiny Picolisp interpreter binary, that
entirely fits into 1st/2nd/3rd level cache, accesses memory without
waitstaites - or a huge, multi gigabyte JIT engine, that, in itself, is a
pure memory monster?

My measurements show, that small, tiny interpreters - especially for lambda
microservices - are much faster than any Microsoft/Oracle/Apple (LLVM is
heavily sponsored by Apple!) technology.

And then you will also notice, that your "cloud memory footprint" (tens of
thousands of micoservices running at the same time with different customer
data, each) will tremendously go down, when you simply don't use any
"Wintel Alliance" technology: "We make slower software for you make faster
hardware!" (where Apple and Oracle certainly belong to!)

It saves you plenty of money, when you simply don't use U.S. technology
(neither Closed Source nor Open Source), using a sledgehammer to crack a
nut.

Tiny interpreters, like Picolisp, here have tremendous advantages. Also
don't forget to activate KSM (Kernel Same-page Merging) in Linux. Same
binaries (4K memory pages) get consolidated, only use one, single binary
instance in DRAM.

Remember: *Picolisp is a genius-strike!*

Most people simply don't understand why, because they simply got victim of
long-term U.S. advertising strategies selling more and more hardware to
host bigger and bigger software packages. That nonsense has kept up going
Silicon Valley for two decades now, pulling billions from our pockets.

Have fun!

Guido Stepken


Am Donnerstag, 26. März 2020 schrieb :

> Does anyone realize that there's an LLVM-based port of picolisp being
> worked on by Alex? :)
>
> --
> UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe
>

Re: PicoLisp on windows

[r cs]

Gosh, no!

On Wed, Mar 25, 2020 at 9:02 PM  wrote:

> Does anyone realize that there's an LLVM-based port of picolisp being
> worked on by Alex? :)
>
> --
> UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe
>


-- 
*Níl aon tinteán mar do thinteán féin. *[Irish Gaelic]
(There is no fireside like your own fireside.)

Re: PicoLisp on windows

[C K Kashyap]

Indeed Rick - it was listed in my original email as one of the options :)

On Wed, Mar 25, 2020 at 6:02 PM  wrote:

> Does anyone realize that there's an LLVM-based port of picolisp being
> worked on by Alex? :)
>
> --
> UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe
>

Re: PicoLisp on windows

[rick]

Does anyone realize that there's an LLVM-based port of picolisp being worked on 
by Alex? :)

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

Re: PicoLisp on windows

[Guido Stepken]

Hi to all!

Before s.b. is reinventing wheels, like porting Picolisp onto .net, please
consider Femtolisp, which is the base underlying Julia programming language
JIT compiler. It's LLVM based and ultra fast, tiny and quite useful as PoC
for implementing Picolisp on your own.

https://github.com/JeffBezanson/femtolisp/blob/master/README.md

Picolisp on Windows and .NET ... i could never have imagined that s.b.
could want that ... is Windows still in use anywhere? I mean: After Emotet,
newest Zero Day Exploits, ? Still no antidote against, after one year
now!

Sorry, that i must say that, but whole Microsoft infrastructure has
collapsed under its own weight, cross site complexity!

"End of lifetime" for Microsoft, i would say!

Have fun!

Am Dienstag, 24. März 2020 schrieb C K Kashyap :

> Hi All,
> I've been using PicoLisp under docker on my windows machine but a
> challenge that I face is in my ability to share the scripts with my
> colleagues. It would be awesome to run picolisp on Windows.
>
> minipicolisp is easy to build on Windows (with mingw). However, it does
> not really have networking and bignum among other things.
>
> I was wondering if it would be easier/better -
>
> 1. Try to figure out how to use networking in minipicolisp - perhaps using
> libuv (the io library that's used by nodejs)
> 2. Figure out how to patch the Posix calls needed by Picolisp
> 3. Use PicoLisp LLVM as the base
> 4. Any other idea :)
>
> Regards,
> Kashyap
>

Re: PicoLisp on windows

[George-Phillip Orais]

Ah ok got it, thanks for the clarification.

Hmm maybe you can also try the Emu of Pil64, its in C also.


BR,
Geo

On Wed, Mar 25, 2020 at 2:23 PM C K Kashyap  wrote:

> By runtime I meant something beyond just the OS - in the case of .net ,
> you need the CLR (like the jvm in case of java). It's just that windows
> machines come with CLR so it is not apparent.
> Regards,
> Kashyap
>
> On Tue, Mar 24, 2020 at 10:08 PM George-Phillip Orais <
> orais.georgephil...@gmail.com> wrote:
>
>> Hi Kashyap,
>>
>> That's also one of my plan so it will work on Linux and Mac, but will see
>> coz it will be redundant especially for Linux.
>>
>> miniPicoLisp is indeed pure PicoLisp and ideally for embedded systems,
>> but I'm not sure what you mean "not needing any runtime".
>>
>>
>> BR,
>> Geo
>>
>> On Wed, Mar 25, 2020 at 1:43 PM C K Kashyap  wrote:
>>
>>> Thanks all,
>>>
>>> Hey Geo - perhaps you should use .Net core :) - I look forward to your
>>> implementation.
>>>
>>> I'd still like to figure the possibility of adding to miniPicoLisp - I
>>> like the idea not needing any runtime :)
>>>
>>> Regards,
>>> Kashyap
>>>
>>>
>>> On Tue, Mar 24, 2020 at 8:43 PM r cs >> > wrote:
>>>
>>>> Ersatz is much more functional than minipicolisp and includes basic TCP
>>>> networking.
>>>>
>>>> Regards,
>>>> rcs
>>>>
>>>> On Tue, Mar 24, 2020 at 10:51 PM C K Kashyap >>> > wrote:
>>>>
>>>>> Thanks rcs,
>>>>> I just checked - at the very least Ersataz has "call" implemented!!!
>>>>> ...makes it more useful that miniPicoLIsp.
>>>>> Regards,
>>>>> Kashyap
>>>>>
>>>>> On Tue, Mar 24, 2020 at 7:27 PM C K Kashyap 
>>>>> wrote:
>>>>>
>>>>>> Hi rcs,
>>>>>> I had not considered Erstaz since I assumed that it is equivalent in
>>>>>> capability to miniPicoLisp and has the added requirement of JVM. While I 
>>>>>> am
>>>>>> sure about the JVM part, I am not so sure about the capabilityis that
>>>>>> not so?
>>>>>> Regards,
>>>>>> Kashyap
>>>>>>
>>>>>> On Tue, Mar 24, 2020 at 7:03 PM r cs  wrote:
>>>>>>
>>>>>>> Kashyap:
>>>>>>>
>>>>>>> Have you considered Ersatz on Windows?
>>>>>>>
>>>>>>> Regards,
>>>>>>> rcs
>>>>>>>
>>>>>>> On Tue, Mar 24, 2020 at 6:55 PM C K Kashyap 
>>>>>>> wrote:
>>>>>>>
>>>>>>>> Hi All,
>>>>>>>> I've been using PicoLisp under docker on my windows machine but a
>>>>>>>> challenge that I face is in my ability to share the scripts with my
>>>>>>>> colleagues. It would be awesome to run picolisp on Windows.
>>>>>>>>
>>>>>>>> minipicolisp is easy to build on Windows (with mingw). However, it
>>>>>>>> does not really have networking and bignum among other things.
>>>>>>>>
>>>>>>>> I was wondering if it would be easier/better -
>>>>>>>>
>>>>>>>> 1. Try to figure out how to use networking in minipicolisp -
>>>>>>>> perhaps using libuv (the io library that's used by nodejs)
>>>>>>>> 2 Figure out how to patch the Posix calls needed by Picolisp
>>>>>>>> 3. Use PicoLisp LLVM as the base
>>>>>>>> 4. Any other idea :)
>>>>>>>>
>>>>>>>> Regards,
>>>>>>>> Kashyap
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>> *Níl aon tinteán mar do thinteán féin. *[Irish Gaelic]
>>>>>>> (There is no fireside like your own fireside.)
>>>>>>>
>>>>>>>
>>>>>>>
>>>>
>>>> --
>>>> *Níl aon tinteán mar do thinteán féin. *[Irish Gaelic]
>>>> (There is no fireside like your own fireside.)
>>>>
>>>>
>>>>

Re: PicoLisp on windows

[C K Kashyap]

By runtime I meant something beyond just the OS - in the case of .net , you
need the CLR (like the jvm in case of java). It's just that windows
machines come with CLR so it is not apparent.
Regards,
Kashyap

On Tue, Mar 24, 2020 at 10:08 PM George-Phillip Orais <
orais.georgephil...@gmail.com> wrote:

> Hi Kashyap,
>
> That's also one of my plan so it will work on Linux and Mac, but will see
> coz it will be redundant especially for Linux.
>
> miniPicoLisp is indeed pure PicoLisp and ideally for embedded systems, but
> I'm not sure what you mean "not needing any runtime".
>
>
> BR,
> Geo
>
> On Wed, Mar 25, 2020 at 1:43 PM C K Kashyap  wrote:
>
>> Thanks all,
>>
>> Hey Geo - perhaps you should use .Net core :) - I look forward to your
>> implementation.
>>
>> I'd still like to figure the possibility of adding to miniPicoLisp - I
>> like the idea not needing any runtime :)
>>
>> Regards,
>> Kashyap
>>
>>
>> On Tue, Mar 24, 2020 at 8:43 PM r cs > > wrote:
>>
>>> Ersatz is much more functional than minipicolisp and includes basic TCP
>>> networking.
>>>
>>> Regards,
>>> rcs
>>>
>>> On Tue, Mar 24, 2020 at 10:51 PM C K Kashyap >> > wrote:
>>>
>>>> Thanks rcs,
>>>> I just checked - at the very least Ersataz has "call" implemented!!!
>>>> ...makes it more useful that miniPicoLIsp.
>>>> Regards,
>>>> Kashyap
>>>>
>>>> On Tue, Mar 24, 2020 at 7:27 PM C K Kashyap 
>>>> wrote:
>>>>
>>>>> Hi rcs,
>>>>> I had not considered Erstaz since I assumed that it is equivalent in
>>>>> capability to miniPicoLisp and has the added requirement of JVM. While I 
>>>>> am
>>>>> sure about the JVM part, I am not so sure about the capabilityis that
>>>>> not so?
>>>>> Regards,
>>>>> Kashyap
>>>>>
>>>>> On Tue, Mar 24, 2020 at 7:03 PM r cs  wrote:
>>>>>
>>>>>> Kashyap:
>>>>>>
>>>>>> Have you considered Ersatz on Windows?
>>>>>>
>>>>>> Regards,
>>>>>> rcs
>>>>>>
>>>>>> On Tue, Mar 24, 2020 at 6:55 PM C K Kashyap 
>>>>>> wrote:
>>>>>>
>>>>>>> Hi All,
>>>>>>> I've been using PicoLisp under docker on my windows machine but a
>>>>>>> challenge that I face is in my ability to share the scripts with my
>>>>>>> colleagues. It would be awesome to run picolisp on Windows.
>>>>>>>
>>>>>>> minipicolisp is easy to build on Windows (with mingw). However, it
>>>>>>> does not really have networking and bignum among other things.
>>>>>>>
>>>>>>> I was wondering if it would be easier/better -
>>>>>>>
>>>>>>> 1. Try to figure out how to use networking in minipicolisp - perhaps
>>>>>>> using libuv (the io library that's used by nodejs)
>>>>>>> 2 Figure out how to patch the Posix calls needed by Picolisp
>>>>>>> 3. Use PicoLisp LLVM as the base
>>>>>>> 4. Any other idea :)
>>>>>>>
>>>>>>> Regards,
>>>>>>> Kashyap
>>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> *Níl aon tinteán mar do thinteán féin. *[Irish Gaelic]
>>>>>> (There is no fireside like your own fireside.)
>>>>>>
>>>>>>
>>>>>>
>>>
>>> --
>>> *Níl aon tinteán mar do thinteán féin. *[Irish Gaelic]
>>> (There is no fireside like your own fireside.)
>>>
>>>
>>>

Re: PicoLisp on windows

[George-Phillip Orais]

Hi Kashyap,

That's also one of my plan so it will work on Linux and Mac, but will see
coz it will be redundant especially for Linux.

miniPicoLisp is indeed pure PicoLisp and ideally for embedded systems, but
I'm not sure what you mean "not needing any runtime".


BR,
Geo

On Wed, Mar 25, 2020 at 1:43 PM C K Kashyap  wrote:

> Thanks all,
>
> Hey Geo - perhaps you should use .Net core :) - I look forward to your
> implementation.
>
> I'd still like to figure the possibility of adding to miniPicoLisp - I
> like the idea not needing any runtime :)
>
> Regards,
> Kashyap
>
>
> On Tue, Mar 24, 2020 at 8:43 PM r cs  > wrote:
>
>> Ersatz is much more functional than minipicolisp and includes basic TCP
>> networking.
>>
>> Regards,
>> rcs
>>
>> On Tue, Mar 24, 2020 at 10:51 PM C K Kashyap > > wrote:
>>
>>> Thanks rcs,
>>> I just checked - at the very least Ersataz has "call" implemented!!!
>>> ...makes it more useful that miniPicoLIsp.
>>> Regards,
>>> Kashyap
>>>
>>> On Tue, Mar 24, 2020 at 7:27 PM C K Kashyap  wrote:
>>>
>>>> Hi rcs,
>>>> I had not considered Erstaz since I assumed that it is equivalent in
>>>> capability to miniPicoLisp and has the added requirement of JVM. While I am
>>>> sure about the JVM part, I am not so sure about the capabilityis that
>>>> not so?
>>>> Regards,
>>>> Kashyap
>>>>
>>>> On Tue, Mar 24, 2020 at 7:03 PM r cs  wrote:
>>>>
>>>>> Kashyap:
>>>>>
>>>>> Have you considered Ersatz on Windows?
>>>>>
>>>>> Regards,
>>>>> rcs
>>>>>
>>>>> On Tue, Mar 24, 2020 at 6:55 PM C K Kashyap 
>>>>> wrote:
>>>>>
>>>>>> Hi All,
>>>>>> I've been using PicoLisp under docker on my windows machine but a
>>>>>> challenge that I face is in my ability to share the scripts with my
>>>>>> colleagues. It would be awesome to run picolisp on Windows.
>>>>>>
>>>>>> minipicolisp is easy to build on Windows (with mingw). However, it
>>>>>> does not really have networking and bignum among other things.
>>>>>>
>>>>>> I was wondering if it would be easier/better -
>>>>>>
>>>>>> 1. Try to figure out how to use networking in minipicolisp - perhaps
>>>>>> using libuv (the io library that's used by nodejs)
>>>>>> 2 Figure out how to patch the Posix calls needed by Picolisp
>>>>>> 3. Use PicoLisp LLVM as the base
>>>>>> 4. Any other idea :)
>>>>>>
>>>>>> Regards,
>>>>>> Kashyap
>>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> *Níl aon tinteán mar do thinteán féin. *[Irish Gaelic]
>>>>> (There is no fireside like your own fireside.)
>>>>>
>>>>>
>>>>>
>>
>> --
>> *Níl aon tinteán mar do thinteán féin. *[Irish Gaelic]
>> (There is no fireside like your own fireside.)
>>
>>
>>

Re: PicoLisp on windows

[C K Kashyap]

It will be great if I could have a starting point to extend miniPicoLisp -
hasn't anyone tried to add networking to miniPicoLisp :)
Regards,
Kashyap

On Tue, Mar 24, 2020 at 9:36 PM C K Kashyap  wrote:

> Thanks all,
>
> Hey Geo - perhaps you should use .Net core :) - I look forward to your
> implementation.
>
> I'd still like to figure the possibility of adding to miniPicoLisp - I
> like the idea not needing any runtime :)
>
> Regards,
> Kashyap
>
>
> On Tue, Mar 24, 2020 at 8:43 PM r cs  wrote:
>
>> Ersatz is much more functional than minipicolisp and includes basic TCP
>> networking.
>>
>> Regards,
>> rcs
>>
>> On Tue, Mar 24, 2020 at 10:51 PM C K Kashyap > > wrote:
>>
>>> Thanks rcs,
>>> I just checked - at the very least Ersataz has "call" implemented!!!
>>> ...makes it more useful that miniPicoLIsp.
>>> Regards,
>>> Kashyap
>>>
>>> On Tue, Mar 24, 2020 at 7:27 PM C K Kashyap  wrote:
>>>
>>>> Hi rcs,
>>>> I had not considered Erstaz since I assumed that it is equivalent in
>>>> capability to miniPicoLisp and has the added requirement of JVM. While I am
>>>> sure about the JVM part, I am not so sure about the capabilityis that
>>>> not so?
>>>> Regards,
>>>> Kashyap
>>>>
>>>> On Tue, Mar 24, 2020 at 7:03 PM r cs  wrote:
>>>>
>>>>> Kashyap:
>>>>>
>>>>> Have you considered Ersatz on Windows?
>>>>>
>>>>> Regards,
>>>>> rcs
>>>>>
>>>>> On Tue, Mar 24, 2020 at 6:55 PM C K Kashyap 
>>>>> wrote:
>>>>>
>>>>>> Hi All,
>>>>>> I've been using PicoLisp under docker on my windows machine but a
>>>>>> challenge that I face is in my ability to share the scripts with my
>>>>>> colleagues. It would be awesome to run picolisp on Windows.
>>>>>>
>>>>>> minipicolisp is easy to build on Windows (with mingw). However, it
>>>>>> does not really have networking and bignum among other things.
>>>>>>
>>>>>> I was wondering if it would be easier/better -
>>>>>>
>>>>>> 1. Try to figure out how to use networking in minipicolisp - perhaps
>>>>>> using libuv (the io library that's used by nodejs)
>>>>>> 2. Figure out how to patch the Posix calls needed by Picolisp
>>>>>> 3. Use PicoLisp LLVM as the base
>>>>>> 4. Any other idea :)
>>>>>>
>>>>>> Regards,
>>>>>> Kashyap
>>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> *Níl aon tinteán mar do thinteán féin. *[Irish Gaelic]
>>>>> (There is no fireside like your own fireside.)
>>>>>
>>>>>
>>>>>
>>
>> --
>> *Níl aon tinteán mar do thinteán féin. *[Irish Gaelic]
>> (There is no fireside like your own fireside.)
>>
>>
>>

Re: PicoLisp on windows

[C K Kashyap]

Thanks all,

Hey Geo - perhaps you should use .Net core :) - I look forward to your
implementation.

I'd still like to figure the possibility of adding to miniPicoLisp - I like
the idea not needing any runtime :)

Regards,
Kashyap


On Tue, Mar 24, 2020 at 8:43 PM r cs  wrote:

> Ersatz is much more functional than minipicolisp and includes basic TCP
> networking.
>
> Regards,
> rcs
>
> On Tue, Mar 24, 2020 at 10:51 PM C K Kashyap  > wrote:
>
>> Thanks rcs,
>> I just checked - at the very least Ersataz has "call" implemented!!!
>> ...makes it more useful that miniPicoLIsp.
>> Regards,
>> Kashyap
>>
>> On Tue, Mar 24, 2020 at 7:27 PM C K Kashyap  wrote:
>>
>>> Hi rcs,
>>> I had not considered Erstaz since I assumed that it is equivalent in
>>> capability to miniPicoLisp and has the added requirement of JVM. While I am
>>> sure about the JVM part, I am not so sure about the capabilityis that
>>> not so?
>>> Regards,
>>> Kashyap
>>>
>>> On Tue, Mar 24, 2020 at 7:03 PM r cs  wrote:
>>>
>>>> Kashyap:
>>>>
>>>> Have you considered Ersatz on Windows?
>>>>
>>>> Regards,
>>>> rcs
>>>>
>>>> On Tue, Mar 24, 2020 at 6:55 PM C K Kashyap 
>>>> wrote:
>>>>
>>>>> Hi All,
>>>>> I've been using PicoLisp under docker on my windows machine but a
>>>>> challenge that I face is in my ability to share the scripts with my
>>>>> colleagues. It would be awesome to run picolisp on Windows.
>>>>>
>>>>> minipicolisp is easy to build on Windows (with mingw). However, it
>>>>> does not really have networking and bignum among other things.
>>>>>
>>>>> I was wondering if it would be easier/better -
>>>>>
>>>>> 1. Try to figure out how to use networking in minipicolisp - perhaps
>>>>> using libuv (the io library that's used by nodejs)
>>>>> 2. Figure out how to patch the Posix calls needed by Picolisp
>>>>> 3. Use PicoLisp LLVM as the base
>>>>> 4. Any other idea :)
>>>>>
>>>>> Regards,
>>>>> Kashyap
>>>>>
>>>>
>>>>
>>>> --
>>>> *Níl aon tinteán mar do thinteán féin. *[Irish Gaelic]
>>>> (There is no fireside like your own fireside.)
>>>>
>>>>
>>>>
>
> --
> *Níl aon tinteán mar do thinteán féin. *[Irish Gaelic]
> (There is no fireside like your own fireside.)
>
>
>

Re: PicoLisp on windows

[r cs]

Ersatz is much more functional than minipicolisp and includes basic TCP
networking.

Regards,
rcs

On Tue, Mar 24, 2020 at 10:51 PM C K Kashyap  wrote:

> Thanks rcs,
> I just checked - at the very least Ersataz has "call" implemented!!!
> ...makes it more useful that miniPicoLIsp.
> Regards,
> Kashyap
>
> On Tue, Mar 24, 2020 at 7:27 PM C K Kashyap  wrote:
>
>> Hi rcs,
>> I had not considered Erstaz since I assumed that it is equivalent in
>> capability to miniPicoLisp and has the added requirement of JVM. While I am
>> sure about the JVM part, I am not so sure about the capabilityis that
>> not so?
>> Regards,
>> Kashyap
>>
>> On Tue, Mar 24, 2020 at 7:03 PM r cs  wrote:
>>
>>> Kashyap:
>>>
>>> Have you considered Ersatz on Windows?
>>>
>>> Regards,
>>> rcs
>>>
>>> On Tue, Mar 24, 2020 at 6:55 PM C K Kashyap  wrote:
>>>
>>>> Hi All,
>>>> I've been using PicoLisp under docker on my windows machine but a
>>>> challenge that I face is in my ability to share the scripts with my
>>>> colleagues. It would be awesome to run picolisp on Windows.
>>>>
>>>> minipicolisp is easy to build on Windows (with mingw). However, it does
>>>> not really have networking and bignum among other things.
>>>>
>>>> I was wondering if it would be easier/better -
>>>>
>>>> 1. Try to figure out how to use networking in minipicolisp - perhaps
>>>> using libuv (the io library that's used by nodejs)
>>>> 2. Figure out how to patch the Posix calls needed by Picolisp
>>>> 3. Use PicoLisp LLVM as the base
>>>> 4. Any other idea :)
>>>>
>>>> Regards,
>>>> Kashyap
>>>>
>>>
>>>
>>> --
>>> *Níl aon tinteán mar do thinteán féin. *[Irish Gaelic]
>>> (There is no fireside like your own fireside.)
>>>
>>>
>>>

-- 
*Níl aon tinteán mar do thinteán féin. *[Irish Gaelic]
(There is no fireside like your own fireside.)

Re: PicoLisp on windows

[George-Phillip Orais]

Hi Kahsyap et al,

First of all, I hope everyone here and everyone's family are doing well,
safe and far from the COVID19 danger.
Today I started to work from home because yesterday the report came that
one worker from different company but in the same building of our office is
COVID19 positive, so our company shifts to code red which means full work
from home.
I hope and pray this pandemic will end soon so that we can all go back to
our normal and safe life.

Back to original subject, I am also interested of this subject. Actually I
am working on something for this and plan to announce it once I have
something to show. But because you are asking, maybe I could share some
info here.

I am currently planning to implement PicoLisp on .Net framework with these
two approach:
1. Using DLR which is used for IronPython and IronRuby
2. Implement from scratch and use DLR as reference

Progress is a bit slow because of work, but aiming to make something happen
before or on PicoLisp Conference :)


BR,
Geo

On Wed, Mar 25, 2020 at 11:51 AM C K Kashyap  wrote:

> Thanks rcs,
> I just checked - at the very least Ersataz has "call" implemented!!!
> ...makes it more useful that miniPicoLIsp.
> Regards,
> Kashyap
>
> On Tue, Mar 24, 2020 at 7:27 PM C K Kashyap  wrote:
>
>> Hi rcs,
>> I had not considered Erstaz since I assumed that it is equivalent in
>> capability to miniPicoLisp and has the added requirement of JVM. While I am
>> sure about the JVM part, I am not so sure about the capabilityis that
>> not so?
>> Regards,
>> Kashyap
>>
>> On Tue, Mar 24, 2020 at 7:03 PM r cs  wrote:
>>
>>> Kashyap:
>>>
>>> Have you considered Ersatz on Windows?
>>>
>>> Regards,
>>> rcs
>>>
>>> On Tue, Mar 24, 2020 at 6:55 PM C K Kashyap  wrote:
>>>
>>>> Hi All,
>>>> I've been using PicoLisp under docker on my windows machine but a
>>>> challenge that I face is in my ability to share the scripts with my
>>>> colleagues. It would be awesome to run picolisp on Windows.
>>>>
>>>> minipicolisp is easy to build on Windows (with mingw). However, it does
>>>> not really have networking and bignum among other things.
>>>>
>>>> I was wondering if it would be easier/better -
>>>>
>>>> 1. Try to figure out how to use networking in minipicolisp - perhaps
>>>> using libuv (the io library that's used by nodejs)
>>>> 2. Figure out how to patch the Posix calls needed by Picolisp
>>>> 3. Use PicoLisp LLVM as the base
>>>> 4. Any other idea :)
>>>>
>>>> Regards,
>>>> Kashyap
>>>>
>>>
>>>
>>> --
>>> *Níl aon tinteán mar do thinteán féin. *[Irish Gaelic]
>>> (There is no fireside like your own fireside.)
>>>
>>>
>>>

Re: PicoLisp on windows

[C K Kashyap]

Thanks rcs,
I just checked - at the very least Ersataz has "call" implemented!!!
..makes it more useful that miniPicoLIsp.
Regards,
Kashyap

On Tue, Mar 24, 2020 at 7:27 PM C K Kashyap  wrote:

> Hi rcs,
> I had not considered Erstaz since I assumed that it is equivalent in
> capability to miniPicoLisp and has the added requirement of JVM. While I am
> sure about the JVM part, I am not so sure about the capabilityis that
> not so?
> Regards,
> Kashyap
>
> On Tue, Mar 24, 2020 at 7:03 PM r cs  wrote:
>
>> Kashyap:
>>
>> Have you considered Ersatz on Windows?
>>
>> Regards,
>> rcs
>>
>> On Tue, Mar 24, 2020 at 6:55 PM C K Kashyap  wrote:
>>
>>> Hi All,
>>> I've been using PicoLisp under docker on my windows machine but a
>>> challenge that I face is in my ability to share the scripts with my
>>> colleagues. It would be awesome to run picolisp on Windows.
>>>
>>> minipicolisp is easy to build on Windows (with mingw). However, it does
>>> not really have networking and bignum among other things.
>>>
>>> I was wondering if it would be easier/better -
>>>
>>> 1. Try to figure out how to use networking in minipicolisp - perhaps
>>> using libuv (the io library that's used by nodejs)
>>> 2. Figure out how to patch the Posix calls needed by Picolisp
>>> 3. Use PicoLisp LLVM as the base
>>> 4. Any other idea :)
>>>
>>> Regards,
>>> Kashyap
>>>
>>
>>
>> --
>> *Níl aon tinteán mar do thinteán féin. *[Irish Gaelic]
>> (There is no fireside like your own fireside.)
>>
>>
>>

Re: PicoLisp on windows

[C K Kashyap]

Hi rcs,
I had not considered Erstaz since I assumed that it is equivalent in
capability to miniPicoLisp and has the added requirement of JVM. While I am
sure about the JVM part, I am not so sure about the capabilityis that
not so?
Regards,
Kashyap

On Tue, Mar 24, 2020 at 7:03 PM r cs  wrote:

> Kashyap:
>
> Have you considered Ersatz on Windows?
>
> Regards,
> rcs
>
> On Tue, Mar 24, 2020 at 6:55 PM C K Kashyap  wrote:
>
>> Hi All,
>> I've been using PicoLisp under docker on my windows machine but a
>> challenge that I face is in my ability to share the scripts with my
>> colleagues. It would be awesome to run picolisp on Windows.
>>
>> minipicolisp is easy to build on Windows (with mingw). However, it does
>> not really have networking and bignum among other things.
>>
>> I was wondering if it would be easier/better -
>>
>> 1. Try to figure out how to use networking in minipicolisp - perhaps
>> using libuv (the io library that's used by nodejs)
>> 2. Figure out how to patch the Posix calls needed by Picolisp
>> 3. Use PicoLisp LLVM as the base
>> 4. Any other idea :)
>>
>> Regards,
>> Kashyap
>>
>
>
> --
> *Níl aon tinteán mar do thinteán féin. *[Irish Gaelic]
> (There is no fireside like your own fireside.)
>
>
>

Re: PicoLisp on windows

[r cs]

Kashyap:

Have you considered Ersatz on Windows?

Regards,
rcs

On Tue, Mar 24, 2020 at 6:55 PM C K Kashyap  wrote:

> Hi All,
> I've been using PicoLisp under docker on my windows machine but a
> challenge that I face is in my ability to share the scripts with my
> colleagues. It would be awesome to run picolisp on Windows.
>
> minipicolisp is easy to build on Windows (with mingw). However, it does
> not really have networking and bignum among other things.
>
> I was wondering if it would be easier/better -
>
> 1. Try to figure out how to use networking in minipicolisp - perhaps using
> libuv (the io library that's used by nodejs)
> 2. Figure out how to patch the Posix calls needed by Picolisp
> 3. Use PicoLisp LLVM as the base
> 4. Any other idea :)
>
> Regards,
> Kashyap
>


-- 
*Níl aon tinteán mar do thinteán féin. *[Irish Gaelic]
(There is no fireside like your own fireside.)

PicoLisp on windows

[C K Kashyap]

Hi All,
I've been using PicoLisp under docker on my windows machine but a challenge
that I face is in my ability to share the scripts with my colleagues. It
would be awesome to run picolisp on Windows.

minipicolisp is easy to build on Windows (with mingw). However, it does not
really have networking and bignum among other things.

I was wondering if it would be easier/better -

1. Try to figure out how to use networking in minipicolisp - perhaps using
libuv (the io library that's used by nodejs)
2. Figure out how to patch the Posix calls needed by Picolisp
3. Use PicoLisp LLVM as the base
4. Any other idea :)

Regards,
Kashyap

Re: picolisp on windows

[C K Kashyap]

Oops, I should have looked more closely. I do see the .src files :)
Thanks!

On Tue, Feb 5, 2019 at 6:07 AM Alexander Burger  wrote:

> Hi Kashyap,
>
> > Anyway, I could not find the java sources - I could only find the
> compiled
> > jar file. Are the java sources available?
>
> They are in fact included in the PicoLisp distro, however not as *.java
> files,
> but as
>
>ersatz/sys.src
>ersatz/fun.src
>
> The script mkJar takes them, builds a single PicoLisp.java file, and
> compiles
> that with javac.
>
> The mkJar script is written in PicoLisp, so this is a chicken-egg problem

Re: picolisp on windows

[Alexander Burger]

Hi Kashyap,

> Anyway, I could not find the java sources - I could only find the compiled
> jar file. Are the java sources available?

They are in fact included in the PicoLisp distro, however not as *.java files,
but as

   ersatz/sys.src
   ersatz/fun.src

The script mkJar takes them, builds a single PicoLisp.java file, and compiles
that with javac.

The mkJar script is written in PicoLisp, so this is a chicken-egg problem. But
you can use Ersatz to (re)build itself.

☺/ A!ex

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

Re: picolisp on windows

[C K Kashyap]

Thanks for the tips rcs,
Yes indeed I was able to build minipicolisp on windows using mingw32. The
best part is that I could take the generated exe and run it on another
machine :)

My goal is to understand picolisp implementation and perhaps switch to it
as my programming environment. I cant wait to get a system working with
picolisp + libuv + SDL! I spent a lot of time trying to build a compiler
starting with the 90 minutes scheme to c compiler (I've managed to
translate it to clojure and python <https://github.com/ckkashyap/s2c>) In
my mind I had no reason to doubt some things which picolisp paper calls as
myths :) ... but after reading it, I feel like I should atleast see it in
action. I was particularly moved by the thought that compilation causes the
loss of lispiness!

Anyway, I could not find the java sources - I could only find the compiled
jar file. Are the java sources available?

Regards,
Kashyap

On Tue, Feb 5, 2019 at 4:26 AM r cs  wrote:

> Kashyap:
>
> Under MinGW32 miniPicoLisp fails to build without two tweaks to the
> Makefile:
>
> 1. Remove the -lc switch in this line:
>
> *$(CC) -o $(bin)/picolisp $(picoFiles:.c=.o) -lc -lm*
>
>
> 2. After doing the above an executable will be produced, but the *strip*
> command in the line after that will also fail because under MinGW the
> output file is given an ".exe" filename extension.  You can either add it
> to the Makefile or just run *strip picolisp.exe* manually (which takes
> the resulting file down to 170K from 331K, so it is worth it).
>
> As an alternative to miniPicoLisp on Windows you may want to consider
> using *ersatz*, the Java-based PicoLisp variant (thanks Alex!).  The
> provided jar file works fine under Windows, and it can be rebuilt from
> source there too.  The "non-Unix" command to run it in the README works on
> Windows (using semicolon delimiters), but when you run ersatz from Linux
> you have to use colons instead:
>
> java -DPID=42 -cp .;tmp;picolisp.jar PicoLisp lib.l *(Windows)*
>
> java -DPID=42 -cp .:tmp:picolisp.jar PicoLisp lib.l *(Linux)*
>
> On Windows the Oracle JRE/JDK works fine.  On Linux for openjdk 8 these
> packages are needed: *openjdk-8-jdk, openjdk-8-jdk-headerless,
> openjdk-8-jre, openjdk-8-jre-headerless*.
>
> Regards,
> rcs
>
> On Mon, Feb 4, 2019 at 10:24 AM C K Kashyap  > wrote:
>
>> Hi Alex,
>> I wonder if libuv can substitute for POSIX?
>> Has there been any work in that direction?
>> Regards,
>> Kashyap
>>
>> On Sun, Feb 3, 2019 at 11:47 PM Alexander Burger 
>> wrote:
>>
>>> On Sun, Feb 03, 2019 at 10:25:13PM -0500, r cs wrote:
>>> > I've personally built PicoLisp under MinGW-32 on Windows 7, copied the
>>> EXE
>>> > from where I built it in msys under
>>> /MinGW/msys/1.0/home/myUser/picoLisp/src
>>> > to some place else on the system, and then just run it from a command
>>> > prompt.  Using *make* is also a lot less work than dealing with an
>>> IDE.  I
>>> > only use '32 because it is easy to install and I've been using it for
>>> > years, but the newer '64 should work the same way.
>>>
>>> You mean miniPicoLisp, right? Because neither pil32 nor pil64 can run
>>> under
>>> native Windows. They depend on POSIX.
>>>
>>> ☺/ A!ex
>>>
>>> --
>>> UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe
>>>
>>
>
> --
> *Níl aon tinteán mar do thinteán féin. *[Irish Gaelic]
> (There is no fireside like your own fireside.)
>
>
>

Re: picolisp on windows

[r cs]

Kashyap:

Under MinGW32 miniPicoLisp fails to build without two tweaks to the
Makefile:

1. Remove the -lc switch in this line:

*$(CC) -o $(bin)/picolisp $(picoFiles:.c=.o) -lc -lm*


2. After doing the above an executable will be produced, but the *strip*
command in the line after that will also fail because under MinGW the
output file is given an ".exe" filename extension.  You can either add it
to the Makefile or just run *strip picolisp.exe* manually (which takes the
resulting file down to 170K from 331K, so it is worth it).

As an alternative to miniPicoLisp on Windows you may want to consider using
*ersatz*, the Java-based PicoLisp variant (thanks Alex!).  The provided jar
file works fine under Windows, and it can be rebuilt from source there
too.  The "non-Unix" command to run it in the README works on Windows
(using semicolon delimiters), but when you run ersatz from Linux you have
to use colons instead:

java -DPID=42 -cp .;tmp;picolisp.jar PicoLisp lib.l *(Windows)*

java -DPID=42 -cp .:tmp:picolisp.jar PicoLisp lib.l *(Linux)*

On Windows the Oracle JRE/JDK works fine.  On Linux for openjdk 8 these
packages are needed: *openjdk-8-jdk, openjdk-8-jdk-headerless,
openjdk-8-jre, openjdk-8-jre-headerless*.

Regards,
rcs

On Mon, Feb 4, 2019 at 10:24 AM C K Kashyap  wrote:

> Hi Alex,
> I wonder if libuv can substitute for POSIX?
> Has there been any work in that direction?
> Regards,
> Kashyap
>
> On Sun, Feb 3, 2019 at 11:47 PM Alexander Burger 
> wrote:
>
>> On Sun, Feb 03, 2019 at 10:25:13PM -0500, r cs wrote:
>> > I've personally built PicoLisp under MinGW-32 on Windows 7, copied the
>> EXE
>> > from where I built it in msys under
>> /MinGW/msys/1.0/home/myUser/picoLisp/src
>> > to some place else on the system, and then just run it from a command
>> > prompt.  Using *make* is also a lot less work than dealing with an
>> IDE.  I
>> > only use '32 because it is easy to install and I've been using it for
>> > years, but the newer '64 should work the same way.
>>
>> You mean miniPicoLisp, right? Because neither pil32 nor pil64 can run
>> under
>> native Windows. They depend on POSIX.
>>
>> ☺/ A!ex
>>
>> --
>> UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe
>>
>

-- 
*Níl aon tinteán mar do thinteán féin. *[Irish Gaelic]
(There is no fireside like your own fireside.)

Re: picolisp on windows

[r cs]

Yes -- good catch Alex, thanks.

On Mon, Feb 4, 2019 at 2:47 AM Alexander Burger  wrote:

> On Sun, Feb 03, 2019 at 10:25:13PM -0500, r cs wrote:
> > I've personally built PicoLisp under MinGW-32 on Windows 7, copied the
> EXE
> > from where I built it in msys under
> /MinGW/msys/1.0/home/myUser/picoLisp/src
> > to some place else on the system, and then just run it from a command
> > prompt.  Using *make* is also a lot less work than dealing with an IDE.
> I
> > only use '32 because it is easy to install and I've been using it for
> > years, but the newer '64 should work the same way.
>
> You mean miniPicoLisp, right? Because neither pil32 nor pil64 can run under
> native Windows. They depend on POSIX.
>
> ☺/ A!ex
>
> --
> UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe
>


-- 
*Níl aon tinteán mar do thinteán féin. *[Irish Gaelic]
(There is no fireside like your own fireside.)

Re: picolisp on windows

[C K Kashyap]

Hi Alex,
I wonder if libuv can substitute for POSIX?
Has there been any work in that direction?
Regards,
Kashyap

On Sun, Feb 3, 2019 at 11:47 PM Alexander Burger 
wrote:

> On Sun, Feb 03, 2019 at 10:25:13PM -0500, r cs wrote:
> > I've personally built PicoLisp under MinGW-32 on Windows 7, copied the
> EXE
> > from where I built it in msys under
> /MinGW/msys/1.0/home/myUser/picoLisp/src
> > to some place else on the system, and then just run it from a command
> > prompt.  Using *make* is also a lot less work than dealing with an IDE.
> I
> > only use '32 because it is easy to install and I've been using it for
> > years, but the newer '64 should work the same way.
>
> You mean miniPicoLisp, right? Because neither pil32 nor pil64 can run under
> native Windows. They depend on POSIX.
>
> ☺/ A!ex
>
> --
> UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe
>

Re: picolisp on windows

[Alexander Burger]

On Sun, Feb 03, 2019 at 10:25:13PM -0500, r cs wrote:
> I've personally built PicoLisp under MinGW-32 on Windows 7, copied the EXE
> from where I built it in msys under /MinGW/msys/1.0/home/myUser/picoLisp/src
> to some place else on the system, and then just run it from a command
> prompt.  Using *make* is also a lot less work than dealing with an IDE.  I
> only use '32 because it is easy to install and I've been using it for
> years, but the newer '64 should work the same way.

You mean miniPicoLisp, right? Because neither pil32 nor pil64 can run under
native Windows. They depend on POSIX.

☺/ A!ex

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

Re: picolisp on windows

[C K Kashyap]

Thanks rcs,
I'll go ahead and start using picolisp built with mingw-32 for now and
familiarize myself with it.
Thanks for the confirmation - it's good to know that it works :)
Regards,
Kashyap

On Sun, Feb 3, 2019 at 7:31 PM r cs  wrote:

> Kashyap:
>
> In case you didn't know this, MinGW produces MSVC executables compatible
> with normal Windows, so you just can grab the EXE out of the msys
> environment and run it on any computer where the MSVC redistributable from
> Microsoft has already been installed.
>
> I've personally built PicoLisp under MinGW-32 on Windows 7, copied the EXE
> from where I built it in msys under
> /MinGW/msys/1.0/home/myUser/picoLisp/src to some place else on the
> system, and then just run it from a command prompt.  Using *make* is also
> a lot less work than dealing with an IDE.  I only use '32 because it is
> easy to install and I've been using it for years, but the newer '64 should
> work the same way.
>
> Cheers,
> rcs
>
> On Sun, Feb 3, 2019 at 9:55 PM C K Kashyap  wrote:
>
>> Hi,
>>
>> I'd like to use picolisp built on MSVC. I am planning to start trying to
>> compile miniPicoLisp (it should really be nano :) ) using MSVC.
>>
>> I was wondering if anyone has already done this.
>>
>> MinGW does not quit work for me (I don't have strong technical reasons
>> for this). WSL does not work for me because I intend to use existing DLLs
>> which I don't suppose would be straightforward to use from WSL.
>>
>> Regards,
>> Kashyap
>>
>
>
> --
> *Níl aon tinteán mar do thinteán féin. *[Irish Gaelic]
> (There is no fireside like your own fireside.)
>
>
>

Re: picolisp on windows

[r cs]

Kashyap:

In case you didn't know this, MinGW produces MSVC executables compatible
with normal Windows, so you just can grab the EXE out of the msys
environment and run it on any computer where the MSVC redistributable from
Microsoft has already been installed.

I've personally built PicoLisp under MinGW-32 on Windows 7, copied the EXE
from where I built it in msys under /MinGW/msys/1.0/home/myUser/picoLisp/src
to some place else on the system, and then just run it from a command
prompt.  Using *make* is also a lot less work than dealing with an IDE.  I
only use '32 because it is easy to install and I've been using it for
years, but the newer '64 should work the same way.

Cheers,
rcs

On Sun, Feb 3, 2019 at 9:55 PM C K Kashyap  wrote:

> Hi,
>
> I'd like to use picolisp built on MSVC. I am planning to start trying to
> compile miniPicoLisp (it should really be nano :) ) using MSVC.
>
> I was wondering if anyone has already done this.
>
> MinGW does not quit work for me (I don't have strong technical reasons for
> this). WSL does not work for me because I intend to use existing DLLs which
> I don't suppose would be straightforward to use from WSL.
>
> Regards,
> Kashyap
>


-- 
*Níl aon tinteán mar do thinteán féin. *[Irish Gaelic]
(There is no fireside like your own fireside.)

picolisp on windows

[C K Kashyap]

Hi,

I'd like to use picolisp built on MSVC. I am planning to start trying to
compile miniPicoLisp (it should really be nano :) ) using MSVC.

I was wondering if anyone has already done this.

MinGW does not quit work for me (I don't have strong technical reasons for
this). WSL does not work for me because I intend to use existing DLLs which
I don't suppose would be straightforward to use from WSL.

Regards,
Kashyap

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

[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

[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

[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

[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

[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

[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

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

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: PicoLisp on Windows

[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: PicoLisp on Windows

[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: PicoLisp on Windows

[Philipp Geyer]

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

PicoLisp on Windows

[Arie van Wingerden]

Hi all,

for quite a while I'd like to get into PicoLisp.
I dabbled in newLisp, but PicoLisp seems to offer quite a few advantages:
database, GUI (independent of Java).

Being on Windows appears to be not an advantage :(

 Scenario 1: Windows 10 Linux sub system

Q1:
Would it be possible to use the new Windows 10 Linux subsystem as described
here: https://docs.microsoft.com/en-us/windows/wsl/install-win10 to run
PicoLisp?

Q2:
If answer is YES, would everything work as in Linux, without exceptions?

 Scenario 1: run static PIL using FLinux

If the scenario above does not work, could you please help me to use
FLinux, because I do not fully grasp the instructions here:
http://www.picolisp.com/wiki/?flinuxpicolisp

Afaict the steps mentioned for teh STATIC option are:
1. Download http://software-lab.de/picoLisp.tgz and uncompress
2. Download flinux binary

Q3:
But what are the next steps to get PIL running??

TIA,
/Arie