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 <jon.klei...@fsat.no> 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 <a...@software-lab.de> 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 > -- > > >
