Hi, The -mmacosx-version-min=10.5 was indeed the problem. Changing configure to use 10.8 instead resulted in a successful compilation. For reference, I'm running macOS Mojave (10.4.6) with Xcode 10.3: $ gcc -v Configured with: --prefix=/Applications/Xcode.app/Contents/Developer/usr --with-gxx-include-dir=/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.14.sdk/usr/include/c++/4.2.1 Apple LLVM version 10.0.1 (clang-1001.0.46.4) Target: x86_64-apple-darwin18.7.0 Thread model: posix InstalledDir: /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin Thanks for all the help. Cheers, Paulo > On 18 Sep 2019, at 17:26, Joachim Schimpf <jschimpf_at_...311...> wrote: > > On 18/09/2019 15:25, Paulo Moura wrote: >>> >>> Kish-Shens-iMac:text kish$ gcc t.c >>> >>> Kish-Shens-iMac:text kish$ ./a.out >>> >>> sizrof(int)= 4 >> I do get the expected result with this small program: >> $ ./a.out >> sizrof(int)= 4 > > > Well, if > > gcc t.c > > > works fine, and > > gcc -o conftest -m64 -mmacosx-version-min=10.5 \ > -D_REENTRANT -fPIC -fno-strict-overflow -Wno-logical-op-parentheses \ > -Wno-bitwise-op-parentheses -Wno-pointer-sign -m64 \ > -mmacosx-version-min=10.5 conftest.c -lm > ld: library not found for -lgcc_s.10.5 > clang: error: linker command failed with exit code 1 (use -v to see invocation) > > > makes a linker error, then one of these command line arguments causes it. > My guess was the -mmacosx-version-min=10.5, but I can't test it here. > > > Cheers, > Joachim > ----------------------------------------------------------------- Paulo Moura Logtalk developerReceived on Wed Sep 18 2019 - 20:10:38 CEST
This archive was generated by hypermail 2.3.0 : Wed Sep 25 2024 - 15:13:21 CEST