> On 27 Feb 2019, at 21:58, Ken Cunningham <ken.cunningham.web...@gmail.com> > wrote: > >> is llvm39 still the one to be used? > > I still use +llvm39 > > $ port -v installed | grep ld64 > ld64 @3_1+universal-ld64_127-ld64_236-ld64_97 (active) platform='darwin 10' > archs='i386 x86_64' date='2018-09-20T16:56:39-0700' > ld64-latest @274.2_2+llvm39+universal-llvm34 (active) platform='darwin 10' > archs='i386 x86_64' date='2017-11-26T13:19:27-0800' > > > One thing you learn in this, is to be current but not too current. There is > no benefit to trying to ride the dragon's tale here -- you just run into a > lot of new errors that haven't been dealt with yet. > > llvm3.9 is about equal to Sierra. That's a pretty good spot. I haven't really > tried anything newer yet. > > I was configured to use clang-3.9 as my primary compiler up until a few weeks > ago, when I fixed clang-5.0+ to enable thread_local storage, and so have just > recently set clang-5.0 as my default compiler. > > > Ken
Right now I’ve finished the whole procedure described in <https://trac.macports.org/wiki/LibcxxOnOlderSystems> without hitting any issue (unlike when I had Xcode 4.2 installed). Will now attempt installing the usual packages I need. Thanks for your help, Ken! Franco