MACOS build: configure: error: libmpfr not found or uses a different ABI (including static vs shared).

[anchorz]

./build.sh ends up with the error message. I have no idea how to fix it. normally the library will be installed as part of the build step. Is there a chance I can get some help?

sorry, i cant delete this issue anymore. but there are several issues, that blocks me from compiling the toolchain. after deleting everthing and start from clean build, the error message is different:
In file included from ../../gcc-src/zlib/zutil.c:10:
In file included from ../../gcc-src/zlib/gzguts.h:21:
In file included from /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk/usr/include/stdio.h:61:
/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk/usr/include/_stdio.h:318:7: error: expected ')'
318 | FILE *fdopen(int, const char ) __DARWIN_ALIAS_STARTING(__MAC_10_6, __IPHONE_2_0, __DARWIN_ALIAS(fdopen));
| ^
../../gcc-src/zlib/zutil.h:128:33: note: expanded from macro 'fdopen'
128 | # define fdopen(fd,mode) NULL / No fdopen() */

3 warnings and 3 errors generated.

i cant get the tool chain compiled.

[anchorz]

i tried gcc-ia16 as well:
*** Configuration arm-apple-darwin24.5.0 not supported

[ghaerr]

Hello @anchorz,

I'm sorry about the troubles you're having. I use macOS myself but x86 not arm.

i tried gcc-ia16 as well:

You mean from a different repo? Which one and what exactly did you try? The purpose of ./build.sh is pretty much to compile gcc-elf-ia16. We don't actually maintain ia16-elf-gcc here, but instead use build.sh to avoid having to use an external build for the compiler.

I see earlier you got an error libmpfr not found, but above in your edited post the compilation is failing in zlib with some header.
It would seem the issue is that various gcc sources are not compatible with macOS ARM header files, but I can't be sure unless I can see the entire build log - can you post that?

I don't have an ARM system to help duplicate these issues, so this will be at best trial and error. GCC is a huge complex mess and hard to understand as well. We first will need to ensure that everything is in fact downloaded (e.g. libmpfr) and then after that, try to determine exactly the reasons for each subsequent compilation error - likely a slow process.

The ia16-elf-gcc maintainer has moved off github to https://gitlab.com/tkchia/build-ia16 and https://codeberg.org/tkchia/build-ia16. Have you tried posting this issue over there? TK Chia is very knowledgable about IA16 and if the build-ia16 scripts can be used to get ia16-gcc to compile, we should be able to make those changes work here as well.