and ideone.com have a special minipicolisp version, without IO, networking,
utf8, bignum, db, and etc.
perfect fro embedded beasts.


On Mon, May 30, 2016 at 9:03 PM, Mike <mike.pech...@gmail.com> wrote:

> also try add to glot.io
>
> https://github.com/prasmussen/glot/wiki/Instructions-for-adding-a-new-language-to-glot.io
>
> On 30 мая 2016 г., at 19:01, David Bloom <ipro...@gmail.com> wrote:
>
> Thank you everyone for your help.  Mike, that will definitely be helpful
> as I try to get 386 dev libraries to get 'make all' to work.  Alex, once
> again you have the answer right away:
>
>  ~/picoLisp $ tar xvzf x86-64.linux.tgz
> src64/x86-64.linux.base.s
> src64/x86-64.linux.ext.s
> src64/x86-64.linux.ht.s
> ~/picoLisp $ cd src64/
> ~/picoLisp/src64 $ ls
> Makefile             big.l                err.l                gc.l
>                 io.l                 mkAsm                subr.l
>               sysdefs.c            x86-64.linux.base.s
> apply.l              db.l                 ext.l                glob.l
>               lib                  mkAsm.l              sym.l
>                tags                 x86-64.linux.ext.s
> arch                 defs.l               flow.l               ht.l
>                 main.l               net.l                sys
>                  version.l            x86-64.linux.ht.s
> ~/picoLisp/src64 $ make
> as -o x86-64.linux.base.o x86-64.linux.base.s
> cc -o ../bin/picolisp x86-64.linux.base.o -Wl,--no-as-needed -rdynamic -lc
> -lm -ldl
> strip ../bin/picolisp
> as -o x86-64.linux.ext.o x86-64.linux.ext.s
> cc -o ../lib/ext x86-64.linux.ext.o -shared -export-dynamic
> strip ../lib/ext
> as -o x86-64.linux.ht.o x86-64.linux.ht.s
> cc -o ../lib/ht x86-64.linux.ht.o -shared -export-dynamic
> strip ../lib/ht
> ~/picoLisp/src64 $ cd ../bin/
> ~/picoLisp/bin $ ls
> picolisp   pil        pilIndent  pilPretty  psh        replica    watchdog
>
>
> ~/picoLisp/bin $ sudo ln -s /home/tc/picoLisp /usr/lib/picolisp
> ~/picoLisp/bin $ sudo ln -s /usr/lib/picolisp/bin/picolisp /usr/bin
> ~/picoLisp/bin $ sudo ln -s /usr/lib/picolisp/bin/pil /usr/bin
> ~/picoLisp/bin $ pil +
> : (+ 1 2 3)
> -> 6
>
>
> Success!  Soon I shall announce PicoLisp in a Tiny Core Linux container to
> the list.  Thanks again, what a great community.
>
>
> On Mon, May 30, 2016 at 3:38 AM, Alexander Burger <a...@software-lab.de>
> wrote:
>
>> Hi David, Rick,
>>
>> On Sun, May 29, 2016 at 03:08:06PM -0400, Rick Hanson wrote:
>> > On Sun, May 29, 2016 at 1:52 PM, David Bloom <ipro...@gmail.com> wrote:
>> > > ~/picoLisp/src $ make --version
>> > > GNU Make 4.1
>> > > ...
>> > > -------------------------------------------
>> > > ~ $ cd picoLisp/src64/
>> > > ~/picoLisp/src64 $ make
>>
>> OK, building pil64 is the way to go.
>>
>>
>> > > ./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
>> >
>> > This just means that the build process can't find java.  The `java`
>> > executable has to be installed and on your PATH.
>>
>> Correct. When the pil64 make process wants to build the *.s files, it
>> needs a running PicoLisp to bootstrap. If it can't find any, it falls
>> back to ErsatzLisp which runs on the JVM.
>>
>> You could easily avoid all this hassle if you download the pre-generated
>> *.s files e.g. from
>>
>>    http://software-lab.de/x86-64.linux.tgz
>>
>> ♪♫ Alex
>> --
>> UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe
>>
>
>

Reply via email to