Re: target mismatch building on different versions of darwin

From: Guillermo <>
Date: Sun, 28 Feb 2016 13:21:28 -0300

2016-02-28 7:34 GMT-03:00 Laurent Bercot:
> On 27/02/2016 22:22, Laurent Bercot wrote:
>> I'm not sure how gcc/clang -dumpmachine gets its information (on my Linux,
>> strace doesn't show anything conclusive) but if it's provided by the OS,
>> then I consider this a bug of Darwin that you can report
> I'm told it's hardcoded into the compiler at compiler build time.

Yes. I believe that unless it is explicitly specified at configuration
time, their build system tries to autodetect the host's architecture
and OS using GNU's config.guess script [1], which both the GCC and
Clang (well, LLMV) sources include. And yes, the triplet emitted by
config.guess does include the OS release for some of them.

However, assuming libraries and executables built on one version are
binary compatible with the other, specifying a --target option to
execline's configure script that matches the one in skalib's sysdeps
directory wouldn't also solve the issue? I.e.:

./configure --target=x86_64-apple-darwin13.4.0


[1] <>
Received on Sun Feb 28 2016 - 16:21:28 UTC

This archive was generated by hypermail 2.3.0 : Sun May 09 2021 - 19:38:49 UTC