On Tuesday, March 14, 2023, 06:02:35 PM GMT+2, Herman ten Brugge <hermantenbru...@home.nl> wrote:
> The config-new-macho=no was the default with commit 62096265. Right, so that explains why --config-new-macho=no didn't help, and I'd guess there are no options which would make it work, right? (I don't have a need for this specific commit, so just curiosity). > Can you change the code in 'tests/tcctest.c' on line 3865 to '#if > GCC_MAJOR >= 40'. This did make all tests pass with mob. Nice. > You probably have a very very old clang that does not have some builtin > support but stll sets GCC_MAJOR to a value >= 4. I have MacOSX10.14 SDK installed (with xcode), which I think is the latest xcode/sdk which can be installed on 10.13.6, but I don't know whether or not the default gcc/clang is from this SDK. I guess yes. 'gcc --version' prints: Configured with: --prefix=/Applications/Xcode.app/Contents/Developer/usr --with-gxx-include-dir=/usr/include/c++/4.2.1 Apple LLVM version 10.0.0 (clang-1000.11.45.5) Target: x86_64-apple-darwin17.7.0 Thread model: posix InstalledDir: /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin 'clang --version' is identical, sans the 1st line (Configured...). > Not all platforms in tcc are auto detected. For some platforms have set > configure options like '--with-selinux' or '--config-pie'. Sure, but it's still nice if it is automated, assuming it can be. Can it? - avih
_______________________________________________ Tinycc-devel mailing list Tinycc-devel@nongnu.org https://lists.nongnu.org/mailman/listinfo/tinycc-devel
