<div><br></div><div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Sat, Dec 5, 2020 at 1:25 PM Ken Cunningham <<a href="mailto:ken.cunningham.webuse@gmail.com">ken.cunningham.webuse@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><br>
<br>
> On Dec 5, 2020, at 11:21 AM, Eric Borisch <<a href="mailto:eborisch@macports.org" target="_blank">eborisch@macports.org</a>> wrote:<br>
> <br>
> We could:<br>
> <br>
> * leave the current patch applied to clang-* (to teach clang where to get the library if it is installed)<br>
> * make clang-* no longer depend upon libomp<br>
> * Add a post-install note of "to enable OpenMP support, install libomp"<br>
> * Have libomp depends_build upon the latest clang on the platform (is there an automagic way to do this?)<br>
> <br>
> For most (standard install; many pre-compiled binaries) users, libomp would be installed via pre-built packages, and wouldn't have to pull down clang to build it.<br>
> <br>
> This would also avoid having multiple libomp instances on the system, which seems like a "good thing".<br>
> <br>
> How does that sound? I like having 'sudo port install clang-X' yield a fully featured (-fopenmp just works) compiler, but a reminder note and simple "sudo port install libomp" isn't all bad...<br>
> <br>
> - Eric<br>
<br>
>From a practical point of view great.<br>
<br>
But requiring the manual step to get libomp will never be acceptable to MacPorts, as it is buildbot-unfriendly and breaks the reproducible builds model.<br>
<br>
So we just (I think…) have to have the Portfile addition<br>
<br>
compiler.omp-required 4.5 <br>
<br>
(or whatever the command is) also mandate a lilb dep on "port:libomp”.<br>
<br>
Sounds trivial, and gets it out of the clang/llvm tree.<br>
<br>
<br>
Ken</blockquote><div dir="auto"><br></div><div dir="auto">I think we’re envisioning the same thing; ports that want OpenMP support would depends_lib on libomp through some path. The post-install note would be there to inform users who are explicitly installing clang-X for their own use, and want it to support OpenMP. (Since we are suggesting removing the clang -> libomp dep.)</div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex" dir="auto"></blockquote></div></div><div dir="auto"> - Eric</div>