Re: Do free Open Source Foundation's Software Stacks fall under US Export Law?

[David Bloom]

FWIW I have been enjoying a fantastic feature of e-mail, FILTERS!

Thanks Alex and community for your work, your examples, your help when
someone posts to the list, and most of all for being sane voices in a less
than sane world.

On Thu, May 7, 2020 at 3:52 PM  wrote:

> On Wed, 06 May 2020 17:02 -04:00, Brian Cleary wrote:
> > It's the end of an error.
>
> This was my favorite.  hehe.
>
> --
> UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe
>

Re: PilCon 2020

[David Bloom]

+1 lurker interested in an online conference. While it is disappointing to
not be able to meet people in person it seems that attendance will be
dramatically increased.  Happy to help with testing online tools if needed.

On Wed, Apr 22, 2020, 1:35 AM Jean-Christophe Helary <
jean.christophe.hel...@traduction-libre.org> wrote:

>
>
> > On Apr 22, 2020, at 14:00, Alexander Burger  wrote:
> >
> > Would it make sense to plan an online conference instead? We are playing
> around
> > with Jitsi Meet currently. Any thoughts?
>
> You must be aware that the FSF's LibrePlanet was moved from IRL to Jisti
> (and others) in just a few days of time. In my personal business, I've
> moved all my IRL interactions to Jisti. I find it very practical.
>
> Last night I just had a QA/live support session for a piece of free
> software that I'm involved with. There were setting issues that probably
> were personal technical issues but otherwise the meeting went very smoothly.
>
> The ability to stream Youtube for already registered presentations is
> something that could definitely be of use in a conference, leaving the live
> part for the Q
>
> Also, as a "lurker" and very amateur programer, I would never think of
> joining PilCon in Germany, but I'd love to attend if it were online. I am
> sure a lot of people interested in other dialects of Lisp would find it
> easier to join too.
>
>
> Jean-Christophe Helary
> ---
> http://mac4translators.blogspot.com @brandelune
>
>
>
> --
> UNSUBSCRIBE: mailto:picolisp@software-lab.de?subjectUnsubscribe
>

Re: Small Docker container builds the latest pil in Alpine image

[David Bloom]

SmartOS provides good multi-tenant isolation but it won't run on a Rock64
or Raspi.  That said I do have a rock64, love it, and wish I had a need for
something so that I could buy a clusterboard.  A 28-core, 14GB RAM cluster
on a mini-ITX board for ~275 euros could get some nice work done.

Too bad that WebASM is bunk from a security perspective and I share your
love for hardware isolation.  Wherever it is running I am grateful for the
language and the community.

Cheers,
David B.

On Thu, Mar 26, 2020 at 9:43 AM  wrote:

> Thanks for your informative email.
>
> I mostly agree with your points, except for WebAssembly on the client.
> Though you differentiate between WebASM on client and on server - didn't
> know about WebASM on server, might be a very good thing!
>
> But WebASM on the client is a epic conceptual mistake - it is the new
> Adobe Flash.
> Already now it is mostly used for malware obfuscation:
> https://www.sec.cs.tu-bs.de/pubs/2019a-dimva.pdf
>
> Web scripting languages should not be turing complete, same holds true for
> everything with untrusted scripting input.
> Impossible to validate, unless you execute it. Yes, containment using
> sandboxing turns out to be a better strategy than we thought years ago, but
> still it gives a strong incentive to not work properly.
>
> Of course, that battle is already lost :(
>
> Security-wise, the whole cloud business should be dead, only full hardware
> isolation gives full security.
> Servers could be many small devices (e.g. rock64's, raspis, ..) instead of
> shared resources with many layers and much (energy) overhead.
>
> No, I don't fully practice this, not viable currently.
> Yes, I enjoy living in my radical purity niche.
>
> Have fun ;-)
> - beneroth
> On 26.03.20 13:35, Guido Stepken wrote:
>
> Though - for some folks - it might make things simpler, i am no friend of
> Docker.
>
> What the Docker founder is saying about Docker now:
>
> Solomon Hykes
> @solomonstre
> <https://mobile.twitter.com/solomonstre>
> ·
> 27. März 2019
> <https://mobile.twitter.com/solomonstre/status/004913222324225>
> If WASM+WASI existed in 2008, we wouldn't have needed to created Docker.
> That's how important it is. Webassembly on the server is the future of
> computing. A standardized system interface was the missing link. Let's hope
> WASI is up to the task!
>
> Source: https://twitter.com/solomonstre/status/004913222324225
>
> Picolisp compiles perfectly fine with emcc Emscripten C/C++ compiler and
> runs perfectly in (server side) Webassembly containers. It's completely
> replacing any Docker/Hyper-V/VMware/Amazon AWS Lambda solution.
>
> https://developer.mozilla.org/en-US/docs/WebAssembly/C_to_wasm
>
> And when you look deeper into Webassembly, you will notice, that - in
> itself - it's a Lisp, very much like Picolisp.
>
>
> https://developer.mozilla.org/en-US/docs/WebAssembly/Understanding_the_text_format
>
> Lisp now rules the world. And Linux has won! ;-)
>
> Have fun!
>
> Guido Stepken
>
> Am Mittwoch, 25. März 2020 schrieb David Bloom :
>
>> For work reasons I have strayed from the beloved PicoLisp into Erlang for
>> some time.  While I have much love for using Erlang/OTP to build robust,
>> distributed systems, it handles a different job than PicoLisp in my
>> opinion.  Even though work kept me in the Erlang world for a while I still
>> followed the mailing list and one day saw instructions on how to build pil
>> with musl.  After a single attempt in a fresh Alpine container it worked so
>> I felt compelled to share with the group.  BEHOLD!
>>
>> https://hub.docker.com/r/progit/pil-alpine-minimal
>>
>> Big, big thanks again to Alex and this entire community.  Happy hacking!
>>
>

Re: Small Docker container builds the latest pil in Alpine image

[David Bloom]

On Thu, Mar 26, 2020 at 8:43 AM Guido Stepken  wrote:

> Though - for some folks - it might make things simpler, i am no friend of
> Docker.
>
> What the Docker founder is saying about Docker now:
>
> Solomon Hykes
> @solomonstre
> 
> ·
> 27. März 2019
> 
> If WASM+WASI existed in 2008, we wouldn't have needed to created Docker.
> That's how important it is. Webassembly on the server is the future of
> computing. A standardized system interface was the missing link. Let's hope
> WASI is up to the task!
>
> Source: https://twitter.com/solomonstre/status/004913222324225
>
>
I had no idea.  That's what I get for being out of the loop for a few years

Small Docker container builds the latest pil in Alpine image

[David Bloom]

For work reasons I have strayed from the beloved PicoLisp into Erlang for
some time.  While I have much love for using Erlang/OTP to build robust,
distributed systems, it handles a different job than PicoLisp in my
opinion.  Even though work kept me in the Erlang world for a while I still
followed the mailing list and one day saw instructions on how to build pil
with musl.  After a single attempt in a fresh Alpine container it worked so
I felt compelled to share with the group.  BEHOLD!

https://hub.docker.com/r/progit/pil-alpine-minimal

Big, big thanks again to Alex and this entire community.  Happy hacking!

Re: Wiki - asking for last calls on fonts etc.

[David Bloom]

Looks clean to me.

On Mon, Jun 18, 2018, 5:20 AM Arie van Wingerden  wrote:

> Hi all,
>
> since I really want to push forward with the Wiki, I'd like to ask
> everybody to have a look at this page:
> https://picolisp.com/wiki/?Documentation
>
> Question:
> - are the headers OK?
> - is the top text OK (under header "Introduction"?
>
> Note that we wish to recognize visually impaired people!
>
> Please react before friday 22th of june 2018.
>
> After that we'll change the defaults.
>
> Best,
>Arie
>

Re: PilBox IOException "No such file"

[David Bloom]

Thanks for the reply Alex and I hope that the community solves this one.

On Wed, Apr 18, 2018, 12:32 PM Alexander Burger <a...@software-lab.de> wrote:

> On Wed, Apr 18, 2018 at 03:54:56PM +0000, David Bloom wrote:
> > I'm not certain that is relevant but I did run into issues with pil in
> > termux that was corrected with the page below.  There's a newer fix on
> the
> > page linked below but I've been using termux-fix-shebang successfully for
> > about a year now.  I hope that this can help.
> >
> > https://wiki.termux.com/wiki/Termux-fix-shebang
>
> This is another issue. As I said, there is no /bin/ in Android,
> so Termux comes with /data/data/com.termux/files/usr/bin/bash
> and scripts must call this instead of #!/bin/bash.
>
> But here we are concerned about PilBox which has nothing to do
> with Termux.
>
> ♪♫ Alex
>
> --
> UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe
>

Re: PilBox IOException "No such file"

[David Bloom]

I'm not certain that is relevant but I did run into issues with pil in
termux that was corrected with the page below.  There's a newer fix on the
page linked below but I've been using termux-fix-shebang successfully for
about a year now.  I hope that this can help.

https://wiki.termux.com/wiki/Termux-fix-shebang


Best,
David Bloom

On Wed, Apr 18, 2018, 11:39 AM Arie van Wingerden <xapw...@gmail.com> wrote:

> It might have to do with a change in Android 7:
>
> https://developer.android.com/about/versions/nougat/android-70-changes.html
> <https://developer.android.com/about/versions/nougat/android-7.0-changes.html>
> read paragraph:
>File system permission changes
>
> 2018-04-18 17:20 GMT+02:00 Alexander Burger <a...@software-lab.de>:
>
>> On Wed, Apr 18, 2018 at 05:07:35PM +0200, Richard Z wrote:
>> > maybe the binary has the name or link to the dynamic linker hardcoded
>> and
>> > it has a different name on this system?
>>
>> This could perhaps be. The glibc library.
>>
>> But from what I tested I think we would see a different error message.
>> ♪♫ Alex
>>
>> --
>> UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe
>>
>
>

Re: Vip is now a library

[David Bloom]

Wow, very cool!  Thanks for another quality piece of software for all to
use/learn from.

On Oct 18, 2017 2:16 AM, "Alexander Burger"  wrote:

> Hi all,
>
> I've added Vip ("VI PicoLisp" or "VI personalized") to the PicoLisp distro:
>
>@lib/vip.l
>@bin/vip
>
> I use it as my primary editor since several months, and extended and
> improved it
> since announcement it in the Wiki (https://picolisp.com/wiki/?vip).
>
> If you want to use it in a local installation, change the "#!" line, or -
> what I
> do - put a glue script into a local "bin/" directory which contains the
> single
> line
>
>(load "@bin/vip")
>
> Also, I've put a symbolic link 'vi -> vip' into that local "bin/"
> directory.
>
> If you want it to replace the 'vi' function in the REPL, just include
> "@lib/vip.l" in your startup command.
>
> ♪♫ Alex
>
> --
> UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe
>

Re: 17.6 back in a Tinycore container

[David Bloom]

Hello Tamas,

Thank you for the helpful suggestions, I'm definitely going to do more
markdown via Github (not because of particular love of Github but rather
needed an account to build the Docker container with).

notion.so looks appealing for a fast track to a webpage or PDF.  I'm not
running Debian so no typora for me.  :(  retext is a Python-based
single/dual-pane markdown editor (easy keyboard shortcut to turn live
preview on/off) in my package manager and seems ok.

Definitely making a better effort to keep work documented as I go but
perhaps I got too excited and released it before going back to make the
docs  nicer.  I'm still learning how to release software correctly.

On Tue, Aug 1, 2017 at 1:43 AM, Tamas Herman  wrote:

> Hello David,
>
> There is an upcoming feature in Docker which allows building containers
> the way you described.
> It's called multi-stage builds:
> https://docs.docker.com/engine/userguide/eng-image/multistage-build/
>
> It's available in beta versions only for now.
>
> Btw, I'm using https://www.notion.so/ for taking notes while I'm
> researching or developing something.
> It's like a wiki but real-time collaborative and allows publicly sharing
> your results.
>
> I highly recommend you copy paste your commands into such a tool OR
> at least into a text file as you are developing something, then it's a lot
> easier later
> to turn it into an actual article / blog post / wikipage.
>
> As a middle ground between Notion and a plain text file is creating a
> markdown file
> which you can store on Dropbox, Google Drive, GitLab, GitHub for later
> sharing.
>
> The secret to create a Markdown file effortlessly is to use the
> cross-platform
> https://typora.io/ editor, because it is NOT a dual-pane editor.
>
> It actually shows you the content you typed in a nicely rendered format,
> EXCEPT around your cursor, where it reveals the underlying markdown
> characters
> and allows direct, plain text interaction with them.
>
> I know these sound nuances, but such details can really affect our psyche
> and
> make the difference between creating and liberating knowledge or
> indefinitely
> procrastinating over it.
>
> --
>   tom
>

17.6 back in a Tinycore container

[David Bloom]

Hello PicoLispers,

I've updated the Docker container to the latest source.  It turns out that
compiling the source in a Tinycore container, copying back to host, finally
copying precompiled source back into a fresh container is the path to the
smallest image.  Back down to 14MB including vim so that you can (edit
'mycoolvar) right in the image!  Once I get a little time I'll write up an
article for the wiki explaining the process.

More detailed instructions at:

 https://hub.docker.com/r/progit/docker-tinycore-picolisp/

Enjoy.

David

Re: PicoLisp as first language

[David Bloom]

Nice start and great idea Nehal!  It would be nice to see the result of
each call.  Later you can use that to demonstrate how and why the languages
return the values that they do.

David


On Jul 31, 2017 10:37 AM, "Joh-Tob Schäg"  wrote:

Hello

I would update
Definitions, assignment and bindings
Let is only used for local assignments. setq compares to best to the
examples of the other languages.

Sincerely,



Am 31. Juli 2017 16:07:38 MESZ schrieb Nehal :

> Dear PicoLisp programmers,
>
> Hi! I am Nehal, a new PicoLisp learner and programmer from India.
>
> I am currently working on making simple, easy to begin with PicoLisp
> Documentation for school students. Usually children are taught Java, C++
> but my objective is to have them started with PicoLisp so that they learn
> programming as well as other core subjects such as Math, Physics with the
> aid of PicoLisp.  Through this experience they not only will have knack on
> several subjects with practical learning but will also hone skills in
> PicoLisp, a virtual machine and language they can befriend for life.
>
> In this light, I recently published an article on picolisp.com. Kindly
> see: https
> 
> ://
> 
> picolisp.com
> 
> /wiki/?
> 
> picolispforpythonandchickenschemeprogrammers
> 
> .
>
> This document is currently having less examples. I would like to have
> something more appended to it.
>
> I will be grateful if you can visit the link and give me feedback.
> Suggestions, extensions are requested and welcome.
>
> Thank you so much.
>
> Regards,
> Nehal
>
> सा विद्या या विमुक्तये
>

Re: anyone tried cygwin or mingw recently?

[David Bloom]

Hello Richard,

It sounds like containers may be exactly what you want.  The same
development environment isolated from your host OS of choice.  Docker
containers run great on Linux and my understanding is that Windows is
gaining/already has better support than the past.  There's not much more
work to get persistent storage working, all the directions are in the links
I posted.  I hope that it can be useful to you.

-David

On Mon, Jul 17, 2017 at 6:21 AM, Richard Z <r...@linux-m68k.org> wrote:

> On Sun, Jul 16, 2017 at 12:21:39PM -0400, David Bloom wrote:
>
> Hi,
>
> > Hi Richard.  If you want to get PicoLisp running on windows compilation
> can
> > be difficult but you mention wine.  What are you trying to run PicoLisp
> on,
> > Linux, BSD?  If you are willing to try using Docker containers I've made
> > some slim images of 64-bit PicoLisp.
>
> running on Linux is no problem, what I tried to do is have a binary that
> would run reliably on Windows and inside Wine/Linux.
> It appears the tools are not good enough yet to make that easy.
>
> Richard
>
> --
> Name and OpenPGP keys available from pgp key servers
>
>
> --
> UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe
>

Re: anyone tried cygwin or mingw recently?

[David Bloom]

On Jul 16, 2017 10:33 AM, "Richard Z"  wrote:

On Sun, Jul 09, 2017 at 02:06:05PM -0400, r...@tamos.net wrote:

Hi,

> Curious, if you gave Msys2 a try, as Mike was asking about here:

unfortunatley, msys2 (like cygwin) doesn't work with my wine installation
so I am out of luck for this project.
Also, it seems the float support of picolisp would make my project too
troublesome.

Richard


Hi Richard.  If you want to get PicoLisp running on windows compilation can
be difficult but you mention wine.  What are you trying to run PicoLisp on,
Linux, BSD?  If you are willing to try using Docker containers I've made
some slim images of 64-bit PicoLisp.

See: https://hub.docker.com/r/progit/pil-minimal/

And

https://hub.docker.com/r/progit/pil-enhanced/

I hope this helps ease you into running PicoLisp.

-David

Re: Learning Lisp

[David Bloom]

Hi Jimmie,

You may find yourself having the same realization I often have, that the
PicoLisp community has likely written something quite useful on whatever I
was considering and all one needs to do is look it up.  Additionally
depending on your timezone the IRC channel is quite helpful as well as the
mailing list here.

A great beginning in exploring PicoLisp would be the "Start here" section
of: https://picolisp.com/wiki/?Documentation as there are many articles and
tutorials with new ones being posted often.  Be sure to download the two
books which can teach you everything you need to know about PicoLisp:
- https://github.com/tj64/picolisp-works/blob/master/editor.pdf?raw=true
- https://github.com/tj64/picolisp-by-example/blob/master/book.pdf?raw=true

Getting vip running can be cumbersome for beginners.  For that and other
reasons I've made a small PicoLisp Docker container including vip found
here:
https://hub.docker.com/r/progit/pil-enhanced/

Enjoy PicoLisp and the community surrounding it, I'm a big fan.

Best,
David Bloom

On Wed, May 24, 2017 at 11:43 AM, Jimmie Houchin <jlhouc...@gmail.com>
wrote:

> Hello,
>
> I am new to PicoLisp and Lisp in general.
>
> I know that PicoLisp is not Common Lisp and is much closer to the original
> Lisp. However it seems most books are Common Lisp oriented. While browsing
> Amazon I was wondering if any of these books might be good to get a good
> understanding of Lisp.
> LISP 1.5 Programmer's Manual 2nd Edition
> <https://smile.amazon.com/LISP-Programmers-Manual-Michael-Levin/dp/0262130114>
> by Michael I. Levin (Author), John McCarthy (Contributor)
>
> Interpreting Lisp: Programming and Data Structures 2nd ed. Edition
> <https://smile.amazon.com/Interpreting-Lisp-Programming-Data-Structures/dp/1484227069>
> by Gary D. Knott
>
> The Little LISPer:
> by Matthias Felleisen, Daniel P. Friedman
>
> Build Your Own Lisp <http://buildyourownlisp.com/>
> Learn C and build your own programming language in 1000 lines of code!
> by Daniel Holden
>
> I think that Build Your Own Lisp sounds interesting. It seems like a good
> way to learn some C and get an understanding of Lisp at the same time. But
> it would be nice to have an opinion if available from people who are
> already familiar with PicoLisp.
>
>
> I do not mind buying old and used books to learn. However, I do believe it
> would be of great value for growing the community if there were current
> available resources. I have looked at the mailing list archives and
> website. I am working my way through PicoLisp Works.
>
> What about SICP? Does it bring value to a beginning PicoLisper?
>
> Please feel free to suggest books or other resources which may not be
> mentioned here. I look forward to hearing the wisdom of the community.
>
> Thanks.
>
> Shalom.
>
> Jimmie
>
>
>

Re: picoLisp in custom Buildroot container now enhanced with vip!

[David Bloom]

Thanks, and +1 for the Xzibit inspired line in there.  :)


Everyone is most welcome, I'm pleased that others can find it
useful/educational as well.  Many lolz regarding the dated but still funny
because of context Xzibit reference.  Thank you for getting that.

-David

picoLisp in custom Buildroot container now enhanced with vip!

[David Bloom]

I humbly submit to you an enhanced version of my small picoLisp container.
This comes from a desire to include Alex's vip into the small picoLisp
container for others to use and learn from as I intend to.  The idea behind
a small picoLisp container is to 1) Take advantage of containers to create
a homogeneous development environment across OSes and 2) be able to use the
language with a large, distributed system such as Triton container
infrastructure by Joyent (no affiliation).

Simply run:

docker pull progit/pil-enhanced

Various ways to use the container are listed at:
https://hub.docker.com/r/progit/pil-enhanced/

Enjoy and please feel free to request other enhancements which you think
would enrich the image.

-David Bloom

Re: native calling

[David Bloom]

Wow, don't know how I missed that one.  Thanks AW!  More code to learn
from.  Good luck with lib choice Mike, I'll be watching and learning from
that as well.

-David

On Mar 3, 2017 1:35 AM, "Mike" <mike.pech...@gmail.com> wrote:



On Mar 3, 2017, at 01:24, David Bloom <ipro...@gmail.com> wrote:

Either of these two single header C libraries is where I'm considering
beginning my journey with native calls:

nanomsg - a spiritual successor to ZeroMQ
http://nanomsg.org/index.html


https://github.com/aw/picolisp-nanomsg
nano already done

Re: native calling

[David Bloom]

Either of these two single header C libraries is where I'm considering
beginning my journey with native calls:

nanomsg - a spiritual successor to ZeroMQ
http://nanomsg.org/index.html

Or

nuklear - a slick looking, small ANSI-C GUI
https://github.com/vurtun/nuklear


I'm happy to pitch in code as well but still have much to explore in
PicoLisp and so may provide noobish codezezez.

On Mar 2, 2017 12:15 PM, "Mike Pechkin"  wrote:

> hi,
>
> I need more experience in (native) usage.
> If somebody need library bindings to something you can request here or
> directly.
>
> (mike)
>
>
>

Update: 64-Bit PicoLisp in a Docker container

[David Bloom]

Hello List!

A user pointed out to me that (edit 'sym) didn't work in the TinyCore based
container.  vi was installed but getting it to work proved to be painful so
I set out to build a small, custom container using buildroot.  After much
doc reading I managed to build a 64-bit container with PicoLisp, vim, and
zsh installed all weighing in at only 30MB.

(edit 'sym) now works!  This is notably larger than the 14MB TinyCore image
and perhaps if I were to remove zsh it would get smaller but why not have
more tools in a still tiny image?  The real fun about having vi installed
in the container is that (edit ...) can be used for browsing databases too.

Please download, comment, and enjoy.  Thank you.

-David

Re: Vip Editor

[David Bloom]

Hi Alex and thanks for the speedy reply.

>
> Yes, this is the common problem. I tried to explain it in the article,
> perhaps
> it got a bit too short:
>
> Oops, I was trying to avoid the common problem.  Not your directions so
much as my misunderstanding of C perhaps, see below.  Following your
directions I backed up the existing libncurses.so and made the 6.0 version
appropriate files installed by pacman and it worked on the first try.
Thank you for the help and for all of the code.


>It seems that other Linux distributions need similar actions. Good luck!
>
> So it is important that you set the symbolic link!
>
> (For some reasons, the default "libncurses.so" is NOT a shared object
> library
> which can be called from C programs, but a text file with some kind of
> pointer
> or link in it)
>
> ♪♫ Alex
> --
> UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe
>

Wow...it's situations like this that make me feel I'll never understand C.
Why use an extension of shared object for not a file whose contents are not
that of a shared object?

That's for another day, I've got some new picolisp code to explore and
learn from.  Hopefully I can produce something useful and give back to the
community one day.  Cheers.

-David

Re: Vip Editor

[David Bloom]

Thank you Alex for another exciting utility as well as more example code to
learn from.  I'm having some difficulty installing vip and I hope someone
can help me out.  Using a 64-bit Netrunner (based off of Manjaro based off
Arch) install, a fresh 16-12 picolisp installation, and ncurses installed I
get:

$ sudo pacman -Ss curses|grep installed
core/ncurses 6.0+20161203-1 [installed]
multilib/lib32-ncurses 6.0-2 [installed]

$ vip testo.l
[/usr/local/bin/vip:10] !? (265391 $10060141011 $10060141013
$10060141015)
[DLL] /usr/lib/libncurses.so: file too short
? ^
-> (265391 $10060141011 $10060141013 $10060141015)
?

What does it mean that mean the file is too short?  Thanks and happy new
year!

Kind regards,
David

On Mon, Jan 2, 2017 at 2:29 AM, Alexander Burger 
wrote:

> Hi all,
>
> here is an article about Vip, the Vi-Style Editor in PicoLisp:
>
>http://picolisp.com/wiki/?vip
>
> It consists of only 990 lines of code.
>
> Not that the world needs yet another editor! But it may serve as a useful
> collection of PicoLisp coding examples :)
>
> - Alex
> --
> UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe
>

Re: Compiling for containers

[David Bloom]

This is also my fault. That error message "java: not found" is really
stupid.
I've changed it to some better diagnostics.

- Alex


Don't be so hard on yourself.  I'd truly rather deal with a rare instance
of ambiguous error messages (but with help from the community) than all of
the other issues involved with our languages.  We're all grateful for your
work on and free license of picoLisp.

-David

Re: Compiling for containers

[David Bloom]

Thank you both Mr. Williams and Mr. Burger!  How noobish of me to miss the
bootstrap in the INSTALL...RTFM FTW.  Tinycore 64-bit picoLisp container
updated to 16.6 available with a simple:

docker pull docker-tinycore-picolisp

More directions available at:
https://hub.docker.com/r/progit/docker-tinycore-picolisp/

  I really love this community and language, thanks again for your help and
your patience.

All The Best,
David

Re: Compiling for containers

[David Bloom]

Hi Alexander and thanks for getting back to me so quickly.  In a 64-bit
Tinycore container  "tatsushid/tinycore 7.2-x86_64"
 I edited the Makefile line and tried without success.  Even after trying a
fresh download of the source and adding the "-nopie" to the appropriate
line (#71) I get:

/tmp $ cd picoLisp/src64/
/tmp/picoLisp/src64 $ vi Makefile
/tmp/picoLisp/src64 $ make
/mkAsm x86-64 ".linux" .s Linux base "" ../lib/map  version.l glob.l
main.l gc.l apply.l flo
w.l sym.l subr.l big.l io.l db.l net.l err.l sys/x86-64.linux.code.l
./ersatz/pil: exec: line 5: java: not found
Makefile:159: recipe for target 'x86-64.linux.base.s' failed
make: *** [x86-64.linux.base.s] Error 2

What do you make of this?

On Mon, Dec 12, 2016 at 6:35 AM, Alexander Williams <a...@unscramble.co.jp>
wrote:

> Hi David,
>
> For the stubs-32.h thing.. typically on Debian you would need libc6-i386,
> but that isn't available for 64-bit TinyCore.
>
> For Alpine Linux, you should know that it uses musl not libc, so the
> PicoLisp binary will NOT run on TinyCore if you build it on Alpine (unless
> you have musl.so on Debian..ugh?). To compile/link on Alpine with musl,
> similarly to TinyCore, you'll need to use the 64-bit OS (it exists) for the
> 64-bit binary, and the 32-bit OS for the 32-bit binary.
>
> Anyways for musl (Alpine Linux), just add '-nopie' option to the build
> options in src64/Makefile, ex:
>
> LD-MAIN = -Wl,--no-as-needed -rdynamic -lc -lm -ldl -nopie
>
> That's literally all I changed to compile picoLisp 64-bit on Alpine Linux
> 64-bit. Probably the same option for 32-bit.. let me know ;)
>
> Good luck!
>
>
> AW
> *https://aw.github.io/picolisp <https://aw.github.io/picolisp>*
>
>
> On Sun, Dec 11, 2016 at 5:41 PM, David Bloom <ipro...@gmail.com> wrote:
>
>> Hello list.  I should have come here sooner looking for someone with more
>> C compiling experience than I have.  I used to compile picoLisp in a
>> Tinycore linux container with ease following these steps:
>>
>> - tce-load compiletc  (this adds gcc, make, etc. so we can compile)
>> - copy picolisp source tarball into container
>> - compile PicoLisp
>> - remove build files
>> - tce-audit builddb
>> - tce-audit delete compiletc
>>
>> A Dockerfile would then copy in the pre-compiled picolisp, add
>> appropriate links for global installation resulting in a tidy, small image.
>>
>> For some time now, following the same process I get this:
>>
>> /tmp/picoLisp/src $ cd ../src64/
>> /tmp/picoLisp/src64 $ make
>> ./mkAsm x86-64 ".linux" .s Linux base "" ../lib/map  version.l glob.l
>> main.l gc.l apply.l flow.l sym.l subr.l big.l io.l db.l net.l err.l
>> sys/x86-64.linux.code.l
>> ../ersatz/pil: exec: line 5: java: not found
>> Makefile:159: recipe for target 'x86-64.linux.base.s' failed
>> make: *** [x86-64.linux.base.s] Error 2
>>
>> And this
>>
>> /tmp $ cd picoLisp/src
>> /tmp/picoLisp/src $ make
>> gcc -c -O2 -pipe -falign-functions=32 -fomit-frame-pointer
>> -fno-strict-aliasing -W -Wimplicit -Wreturn-type -Wunused -Wformat
>> -Wuninitialized -Wstrict-prototypes -D_GNU_SOURCE  -D_FILE_OFFS
>> ET_BITS=64 -m32 -D_OS='"Linux"' main.c
>> In file included from /usr/include/features.h:389:0,
>> from /usr/include/stdio.h:27,
>> from pico.h:5,
>> from main.c:5:
>> /usr/include/gnu/stubs.h:7:27: fatal error: gnu/stubs-32.h: No such file
>> or directory
>> compilation terminated.
>> Makefile:129: recipe for target 'main.o' failed
>> make: *** [main.o] Error 1
>> /tmp/picoLisp/src $
>>
>> A cursory search led to missing 32-bit libraries in the 64-bit Tinycore
>> image.  No big deal, what if I tried in a Alpine linux container (only
>> 32-bit but small and gaining popularity) similarly:
>>
>> https://jpst.it/QgPQ (Using a paste service due to verbose output)
>>
>> picolisp compiles easily on Netrunner (based on Manjaro based on Arch)
>> which I'm typing this from.  Any C gurus that can make more sense of this
>> is greatly appreciated.  Thanks for reading my short novel and any pointers.
>>
>> -David
>>
>
>

Compiling for containers

[David Bloom]

Hello list.  I should have come here sooner looking for someone with more C
compiling experience than I have.  I used to compile picoLisp in a Tinycore
linux container with ease following these steps:

- tce-load compiletc  (this adds gcc, make, etc. so we can compile)
- copy picolisp source tarball into container
- compile PicoLisp
- remove build files
- tce-audit builddb
- tce-audit delete compiletc

A Dockerfile would then copy in the pre-compiled picolisp, add appropriate
links for global installation resulting in a tidy, small image.

For some time now, following the same process I get this:

/tmp/picoLisp/src $ cd ../src64/
/tmp/picoLisp/src64 $ make
/mkAsm x86-64 ".linux" .s Linux base "" ../lib/map  version.l glob.l
main.l gc.l apply.l flow.l sym.l subr.l big.l io.l db.l net.l err.l
sys/x86-64.linux.code.l
./ersatz/pil: exec: line 5: java: not found
Makefile:159: recipe for target 'x86-64.linux.base.s' failed
make: *** [x86-64.linux.base.s] Error 2

And this

/tmp $ cd picoLisp/src
/tmp/picoLisp/src $ make
gcc -c -O2 -pipe -falign-functions=32 -fomit-frame-pointer
-fno-strict-aliasing -W -Wimplicit -Wreturn-type -Wunused -Wformat
-Wuninitialized -Wstrict-prototypes -D_GNU_SOURCE  -D_FILE_OFFS
ET_BITS=64 -m32 -D_OS='"Linux"' main.c
In file included from /usr/include/features.h:389:0,
from /usr/include/stdio.h:27,
from pico.h:5,
from main.c:5:
/usr/include/gnu/stubs.h:7:27: fatal error: gnu/stubs-32.h: No such file or
directory
compilation terminated.
Makefile:129: recipe for target 'main.o' failed
make: *** [main.o] Error 1
/tmp/picoLisp/src $

A cursory search led to missing 32-bit libraries in the 64-bit Tinycore
image.  No big deal, what if I tried in a Alpine linux container (only
32-bit but small and gaining popularity) similarly:

https://jpst.it/QgPQ (Using a paste service due to verbose output)

picolisp compiles easily on Netrunner (based on Manjaro based on Arch)
which I'm typing this from.  Any C gurus that can make more sense of this
is greatly appreciated.  Thanks for reading my short novel and any pointers.

-David

Unsubscribe

[David Bloom]

It's OK...I'm still subscribed with another address.

On Nov 26, 2016 9:13 PM, "Bruno Franco" 
wrote:

> I was trying out the diff function and I noticed something:
>
> : (diff '(1 2 3 4) '(3 4))
> -> (1 2)
>
> but
>
> : (diff '(3 4) '(1 2 3 4))
> -> NIL
>
> I think this means that there is an order to the arguments of diff, where
> the second argument must be the shortest.
> I wanted to ask if this was correct,  and also why was it chosen to be
> this way.
>
> I also tried this:
>
> : (diff (1 2 3 4) 2)
> -> (1 3 4)
>
> So, why does diff work even if the second argument isn't a list?
>
> I ran (doc 'diff), and though it explained how diff worked, it didn't
> answer either of my questions. I'd be grateful for any answers you can give
> me, as well as pointers to any document or reference on the internet that
> explains these issues.
>
> Thank you very much.
>

Re: Can't compile picoLisp-16.6 on OSX

[David Bloom]

Updated to 16.6.  I really need to write a small script to e-mail me when
new versions come out.

Alex and others, how do you manage to keep everything so up to date so well
and still maintain a life?

Congrats on the docker image Rafik.  It's nice to know that OSX users can
now go forth and hack the good hack on picoLisp.

Cheers!

On Sun, Oct 9, 2016 at 11:27 AM, Jon Kleiser  wrote:

> Hi Rafik,
>
> I have an old Mac (OS X 10.8.5) that I use mainly for compiling 32-bit
> PicoLisp. The compiled binaries I can copy to newer Macs, where they run
> fine. If you want, I can make the binaries available.
>
> It is possible to install old/standard build tools on a new Mac. I have
> done it once, but I prefer having the original Mac tools, and not having to
> switch back and forth.
>
> If you prefer 64-bit PicoLisp, Docker is a fine solution. If you use this
> one, https://hub.docker.com/r/progit/docker-tinycore-picolisp/, then you
> (probably) get version 16.5.30. Here’s how I start it:
>
> docker run -v /Users/jkleiser/script:/opt/script -it
> progit/docker-tinycore-picolisp
>
> I can then do things like (dir "/opt/script") or (in "/opt/script/foo.sh"
> (echo)) from inside PicoLisp.
>
> /Jon
>
> On 9. okt. 2016, at 08.16, Alexander Burger  wrote:
>
> Hi Rafik,
>
> As it turns out, as mac OSx defaults to clang, We get an error preventing
> the package to compile:
>
> flow.c:786:37: error: fields must have a constant size: 'variable length
> array in structure' extension will never be supported
> struct {any sym; any val;} bnd[length(y)];
>
>
> Yes, this is a known problem. PicoLisp 32-bit depends on dynamically
> sized arrays in several places, and clang doesn't support those :(
>
> ♪♫ Alex
> --
>
>
>

Re: Announcement: PicoLisp in a docker container

[David Bloom]

It's not nearly that cool yet.  I must have updated the version without
updating the docs a while back. While updating the docs I noticed that
there's yet a newer version out.

Isn't there already a script somewhere that pings the download page of
picolisp.com for a newer version?  I'd like to stay on top of versioning.
I'm new to maintaining an open source product and strive to one day meet
the responsiveness and helpfulness that many others have been to me in this
forum.

-David

On Aug 22, 2016 5:15 AM, "Jon Kleiser" <jon.klei...@fsat.no> wrote:

> Thanks again, David!
>
> When I run this and do “(version)”, I get 16.5.30, while your docs says
> “This is version 16.2”. I guess one gets the current stable release version
> when one does the “docker pull”. Is that right?
>
> /Jon
>
> > On 22. Aug, 2016, at 02:00, David Bloom <ipro...@gmail.com> wrote:
> >
> > Docs updated.  Sorry it took me so long.  I'll be quicker to respond in
> the future.  Added a --rm to automatically remove the container upon exit

Re: Announcement: PicoLisp in a docker container

[David Bloom]

Docs updated.  Sorry it took me so long.  I'll be quicker to respond in the
future.  Added a --rm to automatically remove the container upon exit.
That way you don't have to manually remove any cruft left over in docker ps
-a.  Optionally you can decide not to use the --rm switch and be able to
inspect the container after exit.

https://hub.docker.com/r/progit/docker-tinycore-picolisp/

Enjoy!

On Mon, Aug 15, 2016 at 9:31 AM, Jon Kleiser <jon.klei...@fsat.no> wrote:

> Thanks a lot, David!
>
> /Jon
>
> > On 15. Aug, 2016, at 13:57, David Bloom <ipro...@gmail.com> wrote:
> >
> > Pardon the delay Jon,  I've been under extreme amounts of stress but not
> > for much longer.  I'll update the docs to reflect getting a Tinycore
> prompt
> > rather than just a REPL.
> >
> > On Aug 15, 2016 6:08 AM, "Jon Kleiser" <jon.klei...@fsat.no> wrote:
> >
> >> I just want to report that my use of “docker run -v” was not correct.
> This
> >> works much better:
> >>
> >> docker run -v /Users/jkleiser/script:/opt/script -it
> >> progit/docker-tinycore-picolisp
> >>
> >> I can then do things like (dir "/opt/script") or (in
> "/opt/script/foo.sh"
> >> (echo)) from inside PicoLisp.
> >>
> >> /Jon
> >>
> >>> On 12. Aug, 2016, at 16:40, Jon Kleiser <jon.klei...@fsat.no> wrote:
> >>>
> >>> Hi David,
> >>>
> >>> I have now tried your container as described at
> >> https://hub.docker.com/r/progit/docker-tinycore-picolisp/, and I got
> >> PicoLisp version 16.5.30 running. Does your container allow me to get
> >> access to the Tinycore Linux command line?
> >>>
> >>> I need to load a PicoLisp file I have on my Mac. I have tried starting
> >> your container like this:
> >>> docker run -v /Users/jkleiser/script -it progit/docker-tinycore-
> picolisp
> >>> but when I from inside PicoLisp do (dir "/Users/jkleiser/script”), I
> >> just get NIL, so for some reason sharing the OS X file system with your
> >> container doesn’t work at the moment. Maybe the container has to be set
> up
> >> for the new ‘osxfs’ shared file system solution? I don’t know.
> >>>
> >>> If I could get at the Tinycore Linux CLI, then I could maybe get my
> >> PicoLisp file by use of wget or curl (if I put the file on the net
> first)
>
>

Re: GUI components are disabled

[David Bloom]

Thank you Mattias and Alex.  Mattias, your reminder of using +Var like in
the tutorial when there isn't necessarily a db object yet was helpful.

Alex, I still can't seem to get idForm to work even after looking at it in
form.lDo I need something like:

(get (default *ID (val *DB)) 'nm)

like in family.l?  Can you please provide a small example of how to use
idForm to create a new database object?  I feel the need to understand.
Thank you again for all the speedy help.

-David Bloom



On Tue, Jun 14, 2016 at 1:35 AM, Alexander Burger <a...@software-lab.de>
wrote:

> Hi David, Mattias,
>
> > but the +TextField's use +E/R, which connects GUI components to database
> > objects. If I am not mistaken, +E/R uses a locking mechanism to stop
> > several users from changing objects at the same time. Usually, there is
> an
> > (editButton) involved to allow a user to lock the object, make
> > modifications and release the lock once the modifications are done. You
> can
> > find examples of this in the demo app shipped with the PicoLisp
> > distribution.
> >
> > Try changing these lines:
> >
> > (gui '(+E/R +TextField) '(name : home obj) 40 "Name")
> > (gui '(+E/R +TextField) '(email : home obj) 40 "Email")
> >
> > To this:
> >
> > (gui '(+Var +TextField) '*Name 40 "Name")
> > (gui '(+Var +TextField) '*EMail 40 "Email")
> >
> > This uses a '+Var' prefix class to connect the gui components to a
> variable
> > instead. This variable is used by (newButton) to create a new object.
>
> This is correct.
>
> When, however, David wants to edit DB objects, then the +E/R prefix is
> right. But then the 'form' needs an object to be enabled.
>
> The key is to call the 'idObj' function in the form. Usually this is
> done in a header like
>
>( NIL ( (: nm)))
>
> '' internally call 'idObj' which takes care of handling the DB
> objects. Another - more standard - way is to use 'idForm'
>
>(menu ,"Title"
>   (idForm ,"Title" '(chocls) 'nr '+cls T '(may Delete) '((: nr) " -- "
> (: name))
>  ... ) )
>
> ♪♫ Alex
> --
> UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe
>

GUI components are disabled

[David Bloom]

Hello list,

I'm trying to create a registration form styled with pure.css but all the
fields are disabled for some reason.  Code snippets:

(class +Person +Entity)
(rel id (+Need +Key +Number))  # Unique ID.
(rel name (+Need +Sn +Idx +String))# Name
(rel email (+String))  # Email

[de person-reg ()
  (app)
  (action
 (html 0 "PicoLisp rules" *Css NIL
(viewport-meta-element)
( 60)
   (top-nav)
   ( "content-wrapper"
  ( 'content
 ( 'pure-g
( "l-box-lrg pure-u-3-5 pure-u-md-2-5 pure-u-sm-1"
   #(get (default *ID (val *DB)) 'name)
   (form NIL
  (gui '(+E/R +TextField) '(name : home obj) 40
"Name")
  (gui '(+E/R +TextField) '(email : home obj) 40
"Email")
  (newButton T Dst '(+Person) 'name *Name 'email
*Email) ]

### GUI ##
[de top-nav ()
  ( "header"
 ( "home-menu pure-menu pure-menu-horizontal pure-menu-fixed"
( 'a
   '((href . "!homepage") (class . "pure-menu-heading"))
   "Direct2Dr")
( "pure-menu-list"
   ( "pure-menu-item pure-menu-selected"
  ( 'a
  '((href . "!homepage") (class . "pure-menu-link"))
  "Home") )
   ( "pure-menu-item"
  ( 'a
  '((href . "#") (class . "pure-menu-link"))
  "About") )
   ( "pure-menu-item"
  ( 'a
  '((href . "#") (class . "pure-menu-link"))
  "Contact") )
   ( "pure-menu-item"
  ( 'a
  '((href . "#") (class . "pure-menu-link"))
  "Privacy & Security"]

[de footer ()
  ( "footer l-box is-center" Word to our footer!) ]


In the docs I see that gui is a front-end to new in a get request.  What if
I don't have anyone in the database yet?  How can I create a form which
will take basic info via gui and connect it to the db?  I know I'm missing
something really basic here, please point me in the right direction.  Thank
you all.

-David Bloom

Re: Announcement: PicoLisp in a docker container

[David Bloom]

Hi Alex,

There are several reasons why I've created PicoLisp in a container.

1) The image has recently been trimmed down to 14MB.  The large image was
just to get something out there and refine it shortly afterwards.
2) I didn't know that there was an existing extension.  Is it the latest
version?  All existing apt-get/tce-load solutions were off older versions.
3) PicoLisp on windows isn't very straightforward to set up but Docker
seems easier.  Perhaps it can help garner more windows attention?
4) And the main reason why is to run PicoLisp apps against a distributed
storage on Triton container infrastructure.  Ultimately because I think
people are doing it wrong, using Python mainly for data science
applications.  My friend said to show people what's the right way then.
I'd much rather use PicoLisp rather than Python for data science
applications.  Yes I understand that it lowers the barrier of entry for
non-programmers but then companies wind up hiring programmers anyway so I'm
reaching for my favorite language

I hope that explains things more.
Why download a 187MB file to "try" PicoLisp in Tinycore when you can just
type: "tce-load -il picolisp" to download/install the 88KB extension ?

I'm sorry, I don't understand the purpose of this.


Alex

On Wed, Jun 1, 2016 at 2:46 PM, David Bloom <ipro...@gmail.com> wrote:

> Thanks to your collective help I'm pleased to announce the availability of
> PicoLisp in a docker container!  Now anyone with docker installed can try
> out 64-bit PicoLisp v16.2 running on Tinycore Linux by running:
>
> docker pull progit/picolisp
>
> The image is 187MB which I hope to trim further but this is already
> hundreds of MB less than most popular images.  I'll maintain the latest
> version in the container.
>
> Please do offer up helpful suggestions if you have any and enjoy!
>
> -David Bloom
>

Re: PicoLisp Docker container

[David Bloom]

I've got Triton elastic container infrastructure in mind in particular.
All of the security of Solaris zones plus tiny PicoLisp containers
distributed over multiple servers with distributed storage = a very
intriguing platform.

I'm curious to hear about your experiences with LXC Henrik and thank you
for the amazing tutorials by the way.  I've learned a great deal of
PicoLisp from you, Alex, and the other contributors as well.

Mike, I'll work on adding it to the glot list as well.

Please note that now the image is available at:
https://hub.docker.com/r/progit/docker-tinycore-picolisp/

The name changed due to the way automated builds work with Docker Hub
linked to a Github account.  Trimmed from 170MB down to 14MB!!!  This was
done by copying a pre-compiled ./picoLisp/ into the image.  That should
help with scaling.  Enjoy.

On Tue, May 31, 2016 at 7:09 AM, Henrik Sarvell <hsarv...@gmail.com> wrote:

> I've got quite a lot of experience with LXC, can recommend highly if
> Docker doesn't cut it.
>
>
>
> On Sun, May 29, 2016 at 7:52 PM, David Bloom <ipro...@gmail.com> wrote:
>
>> Hello List,
>>
>> I'm trying to make a PicoLisp container for development and scaling of
>> PicoLisp applications.  At first I tried compiling within an Alpine Linux
>> container and got musl errors, then tried in a 64-bit Tinycore linux
>> container.
>>
>> Using latest source 16.2 I get the error below, any thoughts?  I'm not a
>> C guy so this doesn't make much sense to me even when I look at the source
>> code.  Thank you in advance for any suggestions, for the amazing language,
>> and a very supportive community.
>>
>> ~/picoLisp/src $ gcc --version
>> gcc (GCC) 5.2.0
>> Copyright (C) 2015 Free Software Foundation, Inc.
>> This is free software; see the source for copying conditions.  There is
>> NO
>> warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR
>> PURPOSE.
>>
>> ~/picoLisp/src $ make --version
>> GNU Make 4.1
>> Built for x86_64-unknown-linux-gnu
>> Copyright (C) 1988-2014 Free Software Foundation, Inc.
>> License GPLv3+: GNU GPL version 3 or later <
>> http://gnu.org/licenses/gpl.html>
>> This is free software: you are free to change and redistribute it.
>> There is NO WARRANTY, to the extent permitted by law.
>>
>> ---
>> ~/picoLisp/src $ make
>> gcc -c -O2 -pipe -falign-functions=32 -fomit-frame-pointer
>> -fno-strict-aliasing -W -Wimplicit -Wreturn-type -Wunused -Wformat
>> -Wuninitialized -Wstrict-prototypes -D_GNU_SOURCE  -D_FILE_OFFS
>> ET_BITS=64 -m32 -D_OS='"Linux"' main.c
>> In file included from /usr/include/features.h:389:0,
>> from /usr/include/stdio.h:27,
>> from pico.h:5,
>> from main.c:5:
>> /usr/include/gnu/stubs.h:7:27: fatal error: gnu/stubs-32.h: No such file
>> or directory
>> compilation terminated.
>> Makefile:129: recipe for target 'main.o' failed
>> make: *** [main.o] Error 1
>>
>> ---
>> ~ $ cd picoLisp/src64/
>> ~/picoLisp/src64 $ make
>> ./mkAsm x86-64 ".linux" .s Linux base "" ../lib/map  version.l glob.l
>> main.l gc.l apply.l flow.l sym.l subr.l big.l io.l db.l net.l err.l
>> sys/x86-64.linux.code.l
>> ../ersatz/pil: exec: line 5: java: not found
>> Makefile:142: recipe for target 'x86-64.linux.base.s' failed
>> make: *** [x86-64.linux.base.s] Error 2
>>
>>
>

Announcement: PicoLisp in a docker container

[David Bloom]

Thanks to your collective help I'm pleased to announce the availability of
PicoLisp in a docker container!  Now anyone with docker installed can try
out 64-bit PicoLisp v16.2 running on Tinycore Linux by running:

docker pull progit/picolisp

The image is 187MB which I hope to trim further but this is already
hundreds of MB less than most popular images.  I'll maintain the latest
version in the container.

Please do offer up helpful suggestions if you have any and enjoy!

-David Bloom

PicoLisp Docker container

[David Bloom]

Hello List,

I'm trying to make a PicoLisp container for development and scaling of
PicoLisp applications.  At first I tried compiling within an Alpine Linux
container and got musl errors, then tried in a 64-bit Tinycore linux
container.

Using latest source 16.2 I get the error below, any thoughts?  I'm not a C
guy so this doesn't make much sense to me even when I look at the source
code.  Thank you in advance for any suggestions, for the amazing language,
and a very supportive community.

~/picoLisp/src $ gcc --version
gcc (GCC) 5.2.0
Copyright (C) 2015 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

~/picoLisp/src $ make --version
GNU Make 4.1
Built for x86_64-unknown-linux-gnu
Copyright (C) 1988-2014 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 

This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.

---
~/picoLisp/src $ make
gcc -c -O2 -pipe -falign-functions=32 -fomit-frame-pointer
-fno-strict-aliasing -W -Wimplicit -Wreturn-type -Wunused -Wformat
-Wuninitialized -Wstrict-prototypes -D_GNU_SOURCE  -D_FILE_OFFS
ET_BITS=64 -m32 -D_OS='"Linux"' main.c
In file included from /usr/include/features.h:389:0,
from /usr/include/stdio.h:27,
from pico.h:5,
from main.c:5:
/usr/include/gnu/stubs.h:7:27: fatal error: gnu/stubs-32.h: No such file or
directory
compilation terminated.
Makefile:129: recipe for target 'main.o' failed
make: *** [main.o] Error 1

---
~ $ cd picoLisp/src64/
~/picoLisp/src64 $ make
/mkAsm x86-64 ".linux" .s Linux base "" ../lib/map  version.l glob.l
main.l gc.l apply.l flow.l sym.l subr.l big.l io.l db.l net.l err.l
sys/x86-64.linux.code.l
./ersatz/pil: exec: line 5: java: not found
Makefile:142: recipe for target 'x86-64.linux.base.s' failed
make: *** [x86-64.linux.base.s] Error 2

Subscribe

[David Bloom]