This increases the Mac OS requirement for building libc++ to 10.12.
Note that it doesn't change whether the *headers* still support older
platforms -- it's only that macOS >= 10.12 is required to build the
dylib from sources.
Details
Details
- Reviewers
EricWF mclow.lists - Group Reviewers
Restricted Project - Commits
- rGbabd3aefc919: [libc++] Remove workarounds for the lack of clock_gettime on older macOS…
Diff Detail
Diff Detail
- Repository
- rG LLVM Github Monorepo
Event Timeline
Comment Actions
Feedback on this change was requested in http://lists.llvm.org/pipermail/libcxx-dev/2020-February/000688.html and nobody objected, so I think we're good to move forward.
@EricWF @mclow.lists Good?
Comment Actions
We're looking into bumping libc++ in chromium, and this is a problem for us. We statically link libc++, and we still support 10.11. (We _just_ dropped support for 10.10 in our last release iirc.) What do you recommend as path forward?
Comment Actions
Ugh, that's unfortunate. I see two options:
- We revert the patch here, or
- You carry a local patch until you don't support 10.11 anymore
The underlying question I'm really curious to hear the answer to is why don't you use the system libc++.dylib? How do you make sure that you don't have ODR issues when linking against macOS system frameworks that might be linking against libc++.dylib?