Re: llvm / clang / cctools / ld64 version consistency question

2016-07-27 Thread Mihai Moldovan
On 28.07.2016 04:26 AM, Mihai Moldovan wrote: > On 27.07.2016 03:22 PM, Ken Cunningham wrote: >> Also, cctools and ld64 also have a specific variant for each version of >> llvm, it >> appears from the following command. > > The MacPorts-provided compilers (gcc-mp-*, clang-mp-*) (to my knowledge)

Re: llvm / clang / cctools / ld64 version consistency question

2016-07-27 Thread Ken Cunningham
Thanks for taking the time to give such a detailed answer. I can see what I did, after reading your note and ticket -- I ran into the libLTO bug as well, but instead of seeing it as a bug, I thought I had messed up something in the tool configuration by mixing clang/ld64 versions (and I guess

Re: llvm / clang / cctools / ld64 version consistency question

2016-07-27 Thread Mihai Moldovan
On 27.07.2016 03:22 PM, Ken Cunningham wrote: > Having run into an unexpected problem with clang-3.7 segfaulting not long ago > after a 3.7 minor version update, and then an interesting libLTO incorrect > "version error" when I tried to upgrade the compiler chain from clang-3.7 to > clang-3.8, I'd

llvm / clang / cctools / ld64 version consistency question

2016-07-27 Thread Ken Cunningham
Dear smart people, Having run into an unexpected problem with clang-3.7 segfaulting not long ago after a 3.7 minor version update, and then an interesting libLTO incorrect "version error" when I tried to upgrade the compiler chain from clang-3.7 to clang-3.8, I'd like to have a slightly better