Jon, Well, it seems I thought I had llvm installed but it was not the case... :) I added the relevant data to ~/.profile and now
cd pil21 (cd src; make) && bin/picolisp works like a charm :) Thank you, and thank you Alex :) Jean-Christophe > On Feb 13, 2020, at 15:29, Jon Kleiser <jon.klei...@icloud.com> wrote: > > Hi Jean-Christophe, > > If you find llvm-link by doing "which llvm-link”, and get something like this: > /usr/local/opt/llvm/bin/llvm-link > and you have added the two exports to your ~/.bash_profile, then I think you > only need to make a new terminal window or tab for these exports to take > effect. > (In brew there is no separate formula with the name "llvm-link”.) > > /Jon > >> On 13 Feb 2020, at 05:02, Jean-Christophe Helary >> <jean.christophe.hel...@traduction-libre.org> wrote: >> >> >> >>> On Feb 13, 2020, at 1:50, Alexander Burger <a...@software-lab.de> wrote: >>> >>> Hi Jean-Christophe and Kashyap, >>> >>>> Quick related question - I can build pl21 using LLVM target on Linux right? >>>> I am planning to give it a shot on docker this weekend. >>> >>> It should require just these steps: >>> >>> apt install make clang llvm libffi pkg-config >>> tar xfz pil21.tgz >>> cd pil21 >>> (cd src; make) && bin/picolisp >> >> I seem to have all the required packages intalled with brew on macos but I >> get this error: >> >> make: llvm-link: No such file or directory >> make: *** [picolisp.bc] Error 1 >> >> >> Jean-Christophe >> >>> >>> (or analog for other package managers). >>> >>> Note that a running PicoLisp is no longer required for bootstrapping (as it >>> is >>> for pil64), because a pre-built src/base.bc is included in the release. >>> >>> ☺/ A!ex >>> >>> -- >>> UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe -- UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe
