<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="">[sorry forgot to reply to the list earlier]<div class=""><br class=""></div><div class="">Thanks Ken, I am not sure if I can be of much help here - if you’d be willing to take a look that would be great! For now I’ll just blacklist clang below version 8.</div><div class=""><br class=""></div><div class="">Best,</div><div class="">Renee</div><div class=""><br class=""><div><br class=""><blockquote type="cite" class=""><div class="">On Nov 21, 2019, at 12:52 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 style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; " class="">yes, clang 800+ supported thread_local.<div class=""><br class=""></div><div class="">the open-source clangs support thread_local using libc++ way back, but certainly macports-clang-5.0+. </div><div class=""><br class=""></div><div class="">the c++11 gcc versions support it as well, using macports-installed libstdc++.</div><div class=""><br class=""></div><div class="">All of that blacklisting logic is incorporated into Marcus' compiler.thread_local command, and the guts are in 'portconfigure.tcl'. The whole idea was to do it once there correctly, and then everyone could use that instead of figuring it out themselves.</div><div class=""><br class=""></div><div class="">So -- if that is not being honoured in the build, something weird must be going on to make this build ignore base.</div><div class=""><br class=""></div><div class="">That's what I'll have to help sort out, using a VM or real system running those OS versions.</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 class=""><div class="">On 2019-11-21, at 9:35 AM, Renee Otten wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite" class=""><meta http-equiv="Content-Type" content="text/html; charset=utf-8" class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">hi Ken, <div class=""><br class=""></div><div class=""><br class=""></div><div class="">see commits the following commits:</div><div class=""><br class=""></div><div class=""><a href="https://github.com/macports/macports-ports/commit/d6e27064e928b43d412618ac7227cc016e461738" class="">https://github.com/macports/macports-ports/commit/d6e27064e928b43d412618ac7227cc016e461738</a></div><div class=""><a href="https://github.com/macports/macports-ports/commit/c9e9e2a6263bbf9d915d9ba61877c80eed1a3089" class="">https://github.com/macports/macports-ports/commit/c9e9e2a6263bbf9d915d9ba61877c80eed1a3089</a></div><div class=""><br class=""></div><div class="">in the last commit, doing <span class="blob-code-inner blob-code-marker" data-code-marker="+">compiler.blacklist-append {clang < 700} does make it build on OS X 10.8 and 10.9, but not on 10.10 yet, because there it uses Clang “</span>700.1.81”</div><div class=""><br class=""></div><div class="">I’d appreciate your help with it, perhaps the issue is actually different and I don’t understand it correctly. </div><div class=""><br class=""></div><div class="">Thanks again!</div><div class="">Renee</div></div></blockquote></div></div></div></div></blockquote></div><br class=""></div></body></html>