https://bugzilla.redhat.com/show_bug.cgi?id=1451138
--- Comment #5 from Satish Balay <balay(a)fastmail.fm> ---
(In reply to Tom Stellard from comment #4)
(In reply to Satish Balay from comment #3)
clang-4.0 will depend
on libomp-4.0, so when you install clang-4.0 you will get the correct
libomp.
Ok. This is good.
I guess if you want to mix and match versions like this, you will
need to manually specify the libomp header/library paths when building clang.
I don't want to mix versions - my concern was - rpm/dnf should prevent mixing
of versions. [if clang depends on libomp - then presumably rpm/dnf will prevent
mixing of versions].
> Also should libomp package be built with clang - and not gcc?
I think it is preferred that packages are built with the system compiler
unless there is a compelling reason no to you. What would be the reason to
build with clang? Also this would create a circular dependency: clang ->
libomp -> clang.
ok.
--
You are receiving this mail because:
You are on the CC list for the bug.
You are always notified about changes to this product and component