Re: Compiling on Apple Silicon machines

Hi Roberto,

> I have downloaded the current sources (2.49.93+) and I have first
> compiled it with --enable-compatibility, and then I tried adding more
> modules and features.
> 
> Finally, I added
> 
>       # Mac OS X/arm64
>       darwin*--arm64)
>         XCFLAGS="$XCFLAGS -DNO_ASM"
>         ;;
> 
> to src/makemake.in (just after the corresponding block for Mac OS
> X/x86_64) and CLISP  compiles even with generational garbage
> collection.  It passes all tests except some socket related ones which
> seems to be known to give problems under macOS anyway also with intel
> CPUs. I was able to compile and run xindy.
> 
> My configuration command is
> 
> ./configure --with-libreadline-prefix=/opt/homebrew/opt/readline/            \
>             --with-libiconv-prefix=/opt/homebrew/opt/libiconv/               \
>             --with-module=libsvm --with-module=rawsock                       \
>             --with-module=pari --with-libpari-prefix=/opt/homebrew/opt/pari/ \
>             --cbc my-build-with-pari
> 
> - just to show which modules I load - and everything seems to run smoothly.

This is great news; thanks for sharing your experience and the recipe!

> I therefore suggest to perform the above addition to src/makemake.in

I followed the more detailed recipe from the file unix/PLATFORMS and
found that
  - all possible (non-experimental) configurations build fine and pass their
    tests (except for socket.tst, as you noted),
  - even the flag -DNO_ASM is not needed (most likely because the code
    so far has no assembly-language optimizations on arm64).

And the FFI is supported as well, through GNU libffcall version 2.4, which was
released two weeks ago.

I've committed the changes; the code from the git repository ('master'
branch) should now build out-of-the-box.

Bruno



_______________________________________________
clisp-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/clisp-devel