Hi all 1. Yes, Makefile and lib.c as included in pil21/src. 2. No, I built pil21/bin/picolisp directly. The two bitcode files base.bc and ext.bc were already included and I was able to build lib.bc from the modified lib.c (with the clang C compiler). After that I just typed: touch *.bc ; make.
The problem is that I can't regenerate the bitcode files from the Lisp files. Otherwise the executable seems to work fine. The question is: Do you or the current maintainer want these changes? Best Regards, Alexander Am 12. April 2020 17:42:47 MESZ schrieb Alexander Burger <a...@software-lab.de>: >Hi Alexander, > >> Sorry to follow up on my own post, but with some hacking at lib.c and >changing >> the Makefile I was able to bootstrap a working picolisp binary. > >The lib.c and Makefile in pil21/src/? So it worked with emu? > > >> However I can't seem to be able to regenerate the *.bc files from the >Lisp files. Two questions: >> >> 1. would anyone be interested in the changes I made? And who is the >maintainer? > >What changes are those? > >> 2. Any suggestions how to rebuild the system? Do I need a standard >picolisp (i.e. http://software-lab.de/picoLisp.tgz) install? > >Yes, download and unpack that TGZ, then "make emu" in the src64/ >directory. >Then, in pil21/src, change the path to 'pil' to the proper path, e.g > > $ tar xvfz picoLisp.tgz > $ (cd picoLisp/src64; make emu) > $ cd pil21/src/ > >Change the two "pil" calls to "../../picoLisp/pil", or plant a symbolic >link to that 'pil' etc. > > $ make > >☺/ A!ex > > >-- >UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe -- You have zero privacy anyway. Get over it. Scott McNealy 1999
