Hi: On MacPorts, I’ve been the port maintainer for gforth for the last 10 years. However, my interests have changed and I really haven’t done much with MacPorts in the last couple of years. And nothing with forth.
What is this “0.7.9” “release"? The Repology site seems to indicate that virtually all distributions that carry gforth are providing 0.7.3. As does MacPorts. https://repology.org/project/gforth/versions Also, I should note that the MacPorts philosophy is to build from formal releases. Not snapshots or git HEAD. The project seeks to provide repeatable builds. MacPorts mirrors tarballs and provides binary builds (for each supported Mac OS version) when permitted by license, etc. If someone would like to take over from me as port maintainer, that would be good. The MacPorts infrastructure is not complicated and Portfile syntax is well documented. The gforth port is about as simple as it gets. I’d be happy to provide some coaching for a new maintainer. Craig > On Feb 2, 2025, at 7:12 PM, Marvin Littlewood > <[email protected]> wrote: > > Thank you for the new release with bug fixes. > > As my idea is to make MacPorts build the latest tarball per the > instructions on gforth.org, using the 0.7.3_3 release, (already ported with > the aid of a patch), I gave the build a try: > > ./configure reported: > > configure: WARNING: The (old) lib.fs foreign function interface needs > either libffi or the ffcall libraries > > which I found less confusing than: > > *** Config summary: Warnings exist *** > Old foreign interfaces not supported (libffi or ffcall). > > I have not seen this message in my previous attempts at a build. I have > MacPorts libffi 3.4.6_1 installed. > > When building: > > Segmentation fault: 11. > *** Gforth kernel failed *** > make: *** [doc/extradoc.fd] Error 1 > > occurred but re-issuing the make command resulted in the process continuing > to completion and a working gforth with a rather nice green ok on my > solarized terminal. > > make check > > partially works. I attach the output files below. I hope they help... > <20250130-make1.log.txt><20250131-make2.log.txt><20250131-make-check.log.txt><20250131-configure-log.txt>
