On Sun, Nov 12, 2017 at 10:13:52PM +0300, Kirill Bychkov wrote: > On Sun, November 12, 2017 19:26, Brian Callahan wrote: > > Hi ports -- > > > > In preparation for importing devel/openmp, I have (at sthen@'s > > suggestion) been doing a careful review of the ports tree to figure out > > which ports will try to pull in OpenMP if it exists on the system. > > > > I'm nowhere near done, but I have looked at everything in the categories > > archivers through converters, and only two ports as far as I can tell > > will try to pull in OpenMP (according to configure output and build logs). > > > > I'm choosing to explicitly disable OpenMP for all these ports, as that > > makes the most sense to me and will produce the least surprises. Once > > devel/openmp is imported and people want to enable openmp on other > > ports, that to me is a separate discussion for later. > > > > Feedback/OK? > > > > ~Brian > > > > > Hi! > Probably you could hide openmp from pickng up by default like devel/libinotify > does? Just install it in non-standart directory. And then link ports which > will > benefit explicitly.
Except that in that case, it's a PITA to then explicitely link with it. For libnotify, it's flags all around and rpath and whatnot. Landry
