search for: lc_version_min_macosx

...he following: a) In lib/Support/Unix/Host.inc, sys::getDefaultTargetTriple() sets the OS name to darwin14.5 when running on MaxOS X 10.10. 14.5 is the Darwin kernel version as reported by uname. b) In lib/CodeGen/AsmPrinter.cpp, AsmPrinter::doInitialization() writes out this version number to the LC_VERSION_MIN_MACOSX of the generated object. c) The XCode 7 linker seems to expect that LC_VERSION_MIN_MACOSX contains the minimum version number of the MacOS X SDK (10.9, 10.11, ...), NOT the Darwin kernel version number! AFAICT, LLVM had this wrong behaviour for a long time. The only new thing with Xcode 7 is that...

...iple is not enough to have the build system set an older macOS deployment target. I.e the 6.0.0-rc1 binaries I've just uploaded have the same deployment target problem. Looking at the 5.0.0 and 6.0.0-rc1 binaries, I can confirm that their deployment target was too new: Load command 9 cmd LC_VERSION_MIN_MACOSX cmdsize 16 version 10.12 sdk 10.13 I'm not sure why this is happening, because the build logs are peppered with instances of -mmacosx-version-min=10.9. At any rate, it looks like we currently lack support for inferring an older deployment target based on the triple passed to test-relea...

...ve the build system set an older macOS deployment target. I.e the 6.0.0-rc1 binaries I've just uploaded have the same deployment target problem. > > Looking at the 5.0.0 and 6.0.0-rc1 binaries, I can confirm that their deployment target was too new: > > Load command 9 > cmd LC_VERSION_MIN_MACOSX > cmdsize 16 > version 10.12 > sdk 10.13 > > I'm not sure why this is happening, because the build logs are peppered with instances of -mmacosx-version-min=10.9. > > At any rate, it looks like we currently lack support for inferring an older deployment target based on...

Hi Zac, Thanks for the heads-up. I've started targeting a minimum macOS deployment target of 10.9 for the release binaries. Hope this helps. Let me know if there are any issues. vedant > On May 1, 2018, at 4:13 PM, Zac Hansen via llvm-dev <llvm-dev at lists.llvm.org> wrote: > > The past few packages on http://releases.llvm.org/download.html

The past few packages on http://releases.llvm.org/download.html for mac have required the latest version of mac os. Previously they were built for 10.5 (I believe). I was just wondering if there is a technical reason for this change in requirements and if not, if it could be revered. I have systems I actively use which are 10.10 and 10.11 and it would be awesome if I didn't have to build