Don't drop the entire version check, we do want to draw the line somewhere. If
not 4.5 then 4.0, if only because older than that hasn't been tested at all,
and we don't want to worry about ancient toolchains in new versions.
Compatibility defines like priority() here are quite commonly used, but it's a
slippery slope.
Way too much time is being spent on this silly little item. We quite clearly
state that we require openmp >= 4.5, error out if that is not met, and have a
way to disable dang thing. I don't see a *need* to do anything at all, really.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/pull/1454#issuecomment-737895631
_______________________________________________
Rpm-maint mailing list
Rpm-maint@lists.rpm.org
http://lists.rpm.org/mailman/listinfo/rpm-maint
