<Regenaxer>
It calls ../pil, but this is probably not the right one
<Regenaxer>
A bootstrap problem ;)
<Regenaxer>
Ersatz could probably be used, but I don't know what Nistur did
<brandelune>
Good morning !
<Regenaxer>
:)
<brandelune>
Just 20mn from taking the ferry back~
<Regenaxer>
Does ErsatzLisp run at all on Mac?
<brandelune>
let me check
<Regenaxer>
I see :)
<brandelune>
it does
<Regenaxer>
cool
<brandelune>
I seem to remember that there was a reference to bootstraping in the instructions...
<Regenaxer>
yes, in INSTALL
<Regenaxer>
But then mkAsm would try ../ersatz/pil mkAsm.l "$@"
<brandelune>
" - Otherwise, download one of the pre-generated "*.s" file packages"
<Regenaxer>
Before it tries ../pil mkAsm.l "$@"
<Regenaxer>
so the file ../pil is in the way?
<Regenaxer>
The pre-generated "*.s" are the native ones, not available for Mac
<brandelune>
there is a ../pil indeed
<Regenaxer>
the pil is OK
<Regenaxer>
but you must remove the binary
<Regenaxer>
mkAsm does elif test -x ../bin/picolisp
<Regenaxer>
and executes it
<Regenaxer>
this must be some remainder from previous trials
<Regenaxer>
so it crashes
<Regenaxer>
can be safely removed, it is useless anyway
<brandelune>
sorry, what should I remove ? :)
<Regenaxer>
../bin/picolisp
<Regenaxer>
look at src64/mkAsm
<Regenaxer>
it tries to find a picolisp for the build
<Regenaxer>
and it finds ../bin/picolisp but this is faulty
<brandelune>
interesting. I don't have a ../bin/picolisp
<Regenaxer>
relative to src64/
<Regenaxer>
so it is bin/picolisp relative to the installation dir
<Regenaxer>
mkAsm must have found it: elif test -x ../bin/picolisp
<brandelune>
ok, I removed all the "if" branches and left only the reference to ersatz
<Regenaxer>
Not necessary, just remove bin/picolisw
<Regenaxer>
p
<brandelune>
:)
<Regenaxer>
It is built anyway as emu
<brandelune>
Ok, no segfault this time...
<Regenaxer>
:)
<brandelune>
and when I run ../bin/picolisp I get a segfault :(
<Regenaxer>
AFAIK this emu ran on Nistur's machine, just (usec/ did not pass the unit tests
<Regenaxer>
oh ;)
<brandelune>
mabinogion:bin suzume$ ./picolisp
<brandelune>
Segmentation fault: 11
<Regenaxer>
haha, "suzume" - sparrow?
<brandelune>
ok, time for the ferry. I'll be back later.
<brandelune>
right :)
brandelune has quit [Quit: This computer has gone to sleep]
orivej has joined #picolisp
alexshendi has quit [Ping timeout: 240 seconds]
brandelune has joined #picolisp
mtsd has quit [Quit: Leaving]
brandelune has quit [Quit: This computer has gone to sleep]
mtsd has joined #picolisp
freeemint has quit [Ping timeout: 255 seconds]
mtsd has quit [Quit: Leaving]
mtsd has joined #picolisp
freeemint has joined #picolisp
alexshendi has joined #picolisp
mtsd has quit [Quit: Lost terminal]
brandelune has joined #picolisp
brandelune has quit [Quit: This computer has gone to sleep]
orivej has quit [Ping timeout: 248 seconds]
brandelune has joined #picolisp
orivej has joined #picolisp
mtsd has joined #picolisp
brandelune has quit [Quit: This computer has gone to sleep]
brandelune has joined #picolisp
brandelune has quit [Client Quit]
brandelune has joined #picolisp
freeemint has quit [Ping timeout: 265 seconds]
freeemint has joined #picolisp
<freeemint>
<freeemint>
Nu3
freeemint has quit [Client Quit]
<Nistur>
brandelune: I keep missing you when you're around and trying to get things working, it seems :P
<brandelune>
no problem. I'm actually off to bed now :(
<brandelune>
I tried your script. thank you
<brandelune>
I managed to build without errors. The errors came when I run picolisp... :(
<Nistur>
Hmmm
<Nistur>
I seem to recall errors too
<Nistur>
I will try to remember what I did
<Nistur>
brandelune: I won't be around tomorrow morning (UK time) either, as I've got to drive to Gatwick and back... but if I figure it out, I'll be sure to let Regenaxer know what I did, so he can let you know :)
<brandelune>
thank you very much !
<Nistur>
it still doesn't run perfectly, as was mentioned, the tests fail, which appears to be at least usec being weird, but could be other things too after that
<brandelune>
I wish I knew how to investigate the thing myself :)
<brandelune>
I need to go now. Sorry. And thank you for the help.
brandelune has quit [Quit: Leaving]
mtsd has quit [Remote host closed the connection]
dmiles has joined #picolisp
<dmiles>
has anyone implmented full CL on top of picoLisp?
<tankf33der>
dmiles: hardly
<tankf33der>
why? picolisp itself the universe
<Regenaxer>
Why should one? CL is a much worse language
<Regenaxer>
tankf33der, hehe, yes
<dmiles>
i am trying to make a CL interpretor but onlyt want to start by implementing a minimal interpreter
<Regenaxer>
dmiles: PicoLisp is the *answer* to CL, cause CL is such a horror in my view
<dmiles>
maybe all the programs i want are alreayd ported to picoLisp :P
<Regenaxer>
Yes, sure ;)
<Regenaxer>
At least it is easier to port them than to write a full-blown CL
<dmiles>
picoLisp has some non-C impls right? liek Java?
<Regenaxer>
yes, the main one (64 bits) is in assembly, a reduced one in Java
<Regenaxer>
the 32 bit version is plain C
<Regenaxer>
All three are in the same distro TGZ file
* dmiles
looking
<Regenaxer>
The Java version is in the ersatz/ directory
<dmiles>
pretty neat and tiny
<Regenaxer>
You cannot use an existing CL?
<dmiles>
It is hard to decide.. I can use an existing CL if i can make an implementation that can run PowerLoom doing prolog caster than Prolog doing prolog
<dmiles>
caster/faster
<dmiles>
But at this point i could just use PowerLOOMs lisp impl called Stella
<dmiles>
I rewrote PowerLOOM in Prolog.. So i have bene considering jsut writing the lisp interp in that same Prolog
<dmiles>
I guess i have to compare the speed of PowerLOOM translated from Stella to C++ as compared to running on a Lisp
<Regenaxer>
I'm afraid however that if you try that in pil it will be rather slow due to multiple interpretation
<dmiles>
hrrm i wonder if pico-planner is Planner written in PicoLisp