<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">Oh, I see. It’s clock_gettime that we’ll be expecting from now onwards.<div class=""><br class=""></div><div class="">We do have a compatibility implementation of this for MacPorts already that we use when needed <<a href="https://github.com/macports/macports-legacy-support/blob/master/src/time.c" class="">https://github.com/macports/macports-legacy-support/blob/master/src/time.c</a>> . I suppose I might leverage that implementation for older systems…</div><div class=""><br class=""></div><div class="">Ken</div><div class=""><br class=""></div><div class=""><br class=""></div><div class=""><br class=""></div><div class=""><br class=""><div><br class=""><blockquote type="cite" class=""><div class="">On Feb 17, 2020, at 11:37 PM, Ken Cunningham <<a href="mailto:ken.cunningham.webuse@gmail.com" class="">ken.cunningham.webuse@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div class="">Hi,<br class=""><br class="">We do build libc++.dylib on MacPorts for users to install, currently on systems from 10.5 up, but some intrepid users have built it for 10.4. <br class=""><br class="">Users have the option to replace their system installed libc++.dylib as well on 10.7+ if they choose to do so. <br class=""><br class="">I was recently contemplating a way to co-install a newer libc++.dylib to use for MacPorts-installed software to build against to get newer libc++ features, but have not as yet embarked on that.<br class=""><br class="">To build libc++ and libc++abi at present, Jeremy resuscitated the “buildit” and “testit” Makefiles so as to remove the need for a full cmake installation to bootstrap to libc++.dylib and to allow fine-grained tweaking, but moving to the monorepo and installing libc++ from there in the usual fashion is also a consideration.<br class=""><br class="">For interest, we add the linux cxa_thread_atexit implementation to libc++abi.dylib for thread_local support on < 10.7, and it works quite nicely.<br class=""><br class="">What part of the build is going to become 10.12+ only? If it’s a compiler issue, that is easy enough to work around. If it’s system infrastructure, not so easy…<br class=""><br class="">I guess I’ll look at D74489 and see. This may cap out out libc++ offerings for older systems at 10.0 I suppose.<br class=""><br class="">Best,<br class=""><br class="">Ken<br class=""><br class=""><br class=""><blockquote type="cite" class="">On Feb 17, 2020, at 7:06 AM, Louis Dionne via libcxx-dev <<a href="mailto:libcxx-dev@lists.llvm.org" class="">libcxx-dev@lists.llvm.org</a>> wrote:<br class=""><br class="">Hi,<br class=""><br class="">This is a heads up that building the libc++ dylib on Mac OS will require Mac OS >= 10.12 once I land D74489. This will allow us to perform code simplifications in libc++, which is sorely needed because maintenance has become difficult with time. Please note that this only means that Mac OS >= 10.12 will be required to build the dylib.<br class=""><br class="">If you are building the libc++ dylib on Mac OS < 10.12, please reach out so we can talk about a way forward.<br class=""><br class="">Cheers,<br class="">Louis<br class=""><br class="">_______________________________________________<br class="">libcxx-dev mailing list<br class=""><a href="mailto:libcxx-dev@lists.llvm.org" class="">libcxx-dev@lists.llvm.org</a><br class="">https://lists.llvm.org/cgi-bin/mailman/listinfo/libcxx-dev<br class=""></blockquote><br class=""></div></div></blockquote></div><br class=""></div></body></html>