Hello everyone! Some updates that need confirmation.
https://picolisp.com/wiki/?alternativeMacOSRepository It looks like picolisp now requires llvm-16. Also, for a reason that escapes me (maybe a bug on the part of the MacPort team, but I need to investigate), port installs llvm-16 binaries with the -mp-16 suffix *but* does not create aliases to the non-suffixed version. That generates a number of “command not found” errors, namely: - llvm-config - opt - llvm-link - llc I’ll check that with the MacPort teams before proposing a fix. But it’s weird because the non-suffixed aliases seemed to have been produced in previous versions of the llvm port. et voilà ! Jean-Christophe > On Aug 14, 2023, at 22:36, l@tlo <picolisp@software-lab.de> wrote: > > > >> On Aug 14, 2023, at 15:15, l@tlo <picolisp@software-lab.de> wrote: >> >> One year later... >> >> (I don't even remember sending that older mail... 😅) >> >> >> Building on macOS (13) seems to work fine with the following instructions: >> >> https://picolisp.com/wiki/?alternativeMacOSRepository > > I just noticed the reply by Louis Abraham: > > https://picolisp.com/wiki/-A725.html > > For readability it might be better to merge the two documents into one: the > brew style and the macport style. > > Louis, you seem to mean that your version works with M1 machines. Have you > tried it on Intel machines? > > JC > >> >> *and* >> >> Mike's Makefile here: >> >> https://git.envs.net/mpech/pil21-tests/raw/branch/master/Makefile.macos >> >> >> One question to Mike: >> >> Would it be possible that you merge your makefile with Alex's most recent >> and add conditionals to check whether the system is macOS? >> >> That way, we would not need any special instructions to build on macOS :) >> >> >> If not, I'll update the instructions and will add a link to your Makefile. >> >> >> And then, Mia's blog article could be updated to reflect the current status >> :) >> >> https://picolisp-explored.com/how-to-install-picolisp >> >> >> Jean-Christophe >> >>> On May 30, 2022, at 13:39, Jean-Christophe Helary >>> <li...@traduction-libre.org> wrote: >>> >>> >>> >>>> On May 30, 2022, at 18:18, Alexander Burger <a...@software-lab.de> wrote: >>>> >>>> Hi Jean-Christophe, >>>> >>>>> It looks like I'm slowly getting somewhere... >>>>> ... >>>> >>>> Great! :) >>>> >>>> >>>>> ./pil: line 2: exec: >>>>> /Users/suzume/Documents/Repositories/pil21+/src/./bin/picolisp: cannot >>>>> execute: No such file or directory >>>> >>>> That's an easy one. It tries to bootstrap, but bin/picolisp does not exist >>>> yet. >>>> For that reason the pre-build *.ll files are included in the distro. Just >>>> (re)install these. >>> >>> Yes, but now, I'm back to my readline errors... >>> >>> ➜ pil21+ git:(master) ✗ (cd src; make) >>> clang -O3 -w -c -o lib.bc -D_OS='"Darwin"' -D_CPU='"x86_64"' `pkg-config >>> --cflags libffi` -emit-llvm lib.c >>> lib.c:119:4: error: use of undeclared identifier 'rl_catch_signals' >>> rl_catch_signals = 0; >>> ^ >>> lib.c:121:4: error: use of undeclared identifier 'rl_input_available_hook' >>> rl_input_available_hook = rlAvail; >>> ^ >>> >>> (etc.) >>> >>> I'm using this in .profile: >>> >>> ## libffi >>> export >>> PKG_CONFIG_PATH="/usr/local/opt/libffi/lib/pkgconfig:$PKG_CONFIG_PATH" >>> export LDFLAGS="-L/usr/local/opt/libffi/lib:$LDFLAGS" >>> export CPPFLAGS="-I/usr/local/opt/libffi/include:$CPPFLAGS" >>> >>> ## openssl >>> export PATH="/usr/local/opt/openssl@3/bin:$PATH" >>> export LDFLAGS="-L/usr/local/opt/openssl@3/lib:$LDFLAGS" >>> export CPPFLAGS="-I/usr/local/opt/openssl@3/include:$CPPFLAGS" >>> >>> ## readline >>> export >>> PKG_CONFIG_PATH="/usr/local/opt/readline/lib/pkgconfig:$PKG_CONFIG_PATH" >>> export LDFLAGS="-L/usr/local/opt/readline/lib:$LDFLAGS" >>> export CPPFLAGS="-I/usr/local/opt/readline/include:$CPPFLAGS" >>> >>> ## llvm >>> export PATH="/usr/local/opt/llvm@11/bin:$PATH" >>> export LDFLAGS="-L/usr/local/opt/llvm@11/lib:$LDFLAGS" >>> export CPPFLAGS="-I/usr/local/opt/llvm@11/include:$CPPFLAGS" >>> >>> JC :( -- Jean-Christophe Helary https://sr.ht/~brandelune/ @jchelary@sciences.social -- UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe
