<div dir="ltr"><div dir="ltr">Try updating and going again; 7.0 needed to be added to the blacklist-if-not-installed loop in libomp. Not sure if this is your issue, but can't hurt.<div><br></div></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Fri, Feb 8, 2019 at 12:52 PM Chris Jones <<a href="mailto:jonesc@hep.phy.cam.ac.uk">jonesc@hep.phy.cam.ac.uk</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);padding-left:1ex">Hi,<br>
<br>
I was more referring to your macports configuration than the ports tree itself. Are you sure you aren’t overriding the compiler configuration from what would otherwise be the default setting ? That would be my best guess.<br>
<br>
Chris<br>
<br>
> On 8 Feb 2019, at 6:23 pm, Michael Dickens <<a href="mailto:michaelld@macports.org" target="_blank">michaelld@macports.org</a>> wrote:<br>
> <br>
> I'm trying rebuilding the PortIndex ... but, otherwise no the port tree is at the current GIT master and clean. I'm investigating ... - MLD<br>
> <br>
>> On Fri, Feb 8, 2019, at 11:40 AM, Chris Jones wrote:<br>
>> Hi,<br>
>> <br>
>> Clearly clang-7.0 and llvm-.7.0 cannot depend on clang-7.0 as a build <br>
>> dependency, that will never work.<br>
>> <br>
>> I do not see this though myself, in my OSX10.6 VM. There they both <br>
>> depend on clang-3.7 to build. See below. This is fine.<br>
>> <br>
>> You must have done something locally in your checkout to cause this <br>
>> circular dependency... ??<br>
>> <br>
>> cheers Chris<br>
>> <br>
>> MacVM106 ~/Projects/MacPorts/legacy-support > port info clang-7.0 llvm-7.0<br>
>> clang-7.0 @7.0.1 (lang)<br>
>> Variants: [+]analyzer, assertions, debug, [+]emulated_tls, <br>
>> [+]libstdcxx, universal<br>
>> <br>
>> Description: Clang is an LLVM native C/C++/Objective-C <br>
>> compiler, which aims to deliver amazingly fast compiles (e.g. about 3x <br>
>> faster than GCC when compiling<br>
>> Objective-C code in a debug configuration), <br>
>> extremely useful error and warning messages and to provide a platform <br>
>> for building great source level<br>
>> tools. The included Clang Static Analyzer is a <br>
>> tool that automatically finds bugs in your code, and is a great example <br>
>> of the sort of tool that can<br>
>> be built using the Clang frontend as a library to <br>
>> parse C/C++ code.<br>
>> Homepage: <a href="https://clang.llvm.org/" rel="noreferrer" target="_blank">https://clang.llvm.org/</a><br>
>> <br>
>> Extract Dependencies: xz<br>
>> Build Dependencies: cmake, cctools, cctools, clang-3.7<br>
>> Library Dependencies: libxml2, libomp, llvm-7.0, python27, libedit, <br>
>> libffi, ncurses, zlib, libcxx<br>
>> Runtime Dependencies: clang_select, ld64, cctools, perl5<br>
>> Platforms: darwin<br>
>> License: NCSA<br>
>> Maintainers: Email: <a href="mailto:jeremyhu@macports.org" target="_blank">jeremyhu@macports.org</a>, GitHub: jeremyhu<br>
>> Email: <a href="mailto:larryv@macports.org" target="_blank">larryv@macports.org</a>, GitHub: larryv<br>
>> --<br>
>> llvm-7.0 @7.0.1 (lang)<br>
>> Sub-ports: clang-7.0, lldb-7.0<br>
>> Variants: assertions, debug, [+]emulated_tls, ocaml, polly, <br>
>> universal<br>
>> <br>
>> Description: The LLVM Core libraries provide a modern source- <br>
>> and target-independent optimizer, along with code generation support for <br>
>> many popular CPUs (as well<br>
>> as some less common ones!) These libraries are <br>
>> built around a well specified code representation known as the LLVM <br>
>> intermediate representation ("LLVM<br>
>> IR").<br>
>> Homepage: <a href="https://llvm.org/" rel="noreferrer" target="_blank">https://llvm.org/</a><br>
>> <br>
>> Extract Dependencies: xz<br>
>> Build Dependencies: cmake, cctools, clang-3.7<br>
>> Library Dependencies: libedit, libffi, ncurses, xar, zlib, libcxx<br>
>> Runtime Dependencies: perl5, llvm_select<br>
>> Platforms: darwin<br>
>> License: NCSA<br>
>> Maintainers: Email: <a href="mailto:jeremyhu@macports.org" target="_blank">jeremyhu@macports.org</a>, GitHub: jeremyhu<br>
>> Email: <a href="mailto:larryv@macports.org" target="_blank">larryv@macports.org</a>, GitHub: larryv<br>
<br>
</blockquote></div>