Changes between Version 1 and Version 2 of Ticket #54358, comment 17
- Timestamp:
- Jun 29, 2017, 2:35:25 AM (7 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #54358, comment 17
v1 v2 1 1 Although trying to monkey around a way through this is an interesting intellectual exercise at times, my real, practical, and workable recommendation for you is to follow the instructions in the LibcxxOnOlderSystems page to bring your 10.6 system up to current standards with libc++ and a current compiler (presently clang-3.8 or clang-3.9 seem to be ideal on 10.6). This will solve this and all similar issues for you, pretty much forever. Jeremy did a lot of work on this for exactly this reason, and it makes life much easier on 10.6 to 10.8. I wouldn't ignore it. It is exactly what I did, and it works very very well. I highly recommend it. 2 2 3 There are still occasional issues on 10.6 with deficiencies in libc (most of them fixed with my snowleopardfixes library), deficiencies in the SDK (no good way around those), deficiencies in threa l-local-storage (again, you're hooped there unless you can get away with using gcc6 which supports TLS on 10.6, and hoping for no ABI issues), and deficiencies with ports that use xcodebuild (which I haven't yet figured a way around, but might someday get to).3 There are still occasional issues on 10.6 with deficiencies in libc (most of them fixed with my snowleopardfixes library), deficiencies in the SDK (no good way around those), deficiencies in thread-local-storage (again, you're hooped there unless you can get away with using gcc6 which supports TLS on 10.6, and hoping for no ABI issues), and deficiencies with ports that use xcodebuild (which I haven't yet figured a way around, but might someday get to). 4 4 5 5 For 10.5 PPC, I'm working on it. Clang-3.8 is working nicely, and looks to be successfully building almost everything. It can link against libc++ on 10.5 PPC. There is also gcc6, which has some ABI issues, but looks like there are ways around that...