Follow-up Comment #2, bug #66066 (group gforth): m4 is an executable program. The directory m4/ is not the thing that is missing, it's the program. If it does not come with the command line developer tools, you need to install it separately. However, configure says that it found an executable m4 (but maybe that is just a fake that produces the message). If the message directs you to install the command line developer tools, but these tools don't contain m4, the message is misleading, and that should be reported as a bug (but it does not come from Gforth, but apparently from xcode-select).
Looking at your compilation output, my guess is that your "gcc" is actually
clang, and clang takes hours for every engine compilation (and building Gforth
requires many engine compilations). My recommendation is to install an actual
gcc; with that each engine compilation only takes a few seconds.
Once you have dealt with that:
Installing on an Intel Mac running MacOS worked last we tried it.
MacOS on Apple Silicon does not support all the functionality of mmap() that
Gforth uses. Gforth 0.7.3 falls back to a slower execution mode but works.
For the development version this does not work. I spent a day on that problem
two years ago and did not manage to get a workaround working, and since then
this has not risen to the top of my ToDo list.
Development Gforth works fine on Linux on Apple Silicon. The workaround I
plan for MacOS will mean that Gforth will run slower on MacOS than on Linux
(which may or may not be relevant to you).
_______________________________________________________
Reply to this item at:
<https://savannah.gnu.org/bugs/?66066>
_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/
signature.asc
Description: PGP signature
