https://bugzilla.redhat.com/show_bug.cgi?id=1451138 --- Comment #4 from Tom Stellard <tstellar@xxxxxxxxxx> --- (In reply to Satish Balay from comment #3) > Thanks! > > One more issue: > > I have: > > clang-3.9.1-2.fc26.x86_64 > > However I'm able to install libomp-4.0.0 with it. [so the include dirs > between the 2 packages don't match] > > /usr/lib64/clang/3.9.1/include/ vs /usr/lib64/clang/4.0.0/include/omp.h > > [I can grab and install llvm-4.0 and clang-4.0 packages manually but] > perhaps there should be some rpm dependency info that should prevent these > versions from being out-of-sync? > I'm not sure what to do about the version mismatch. clang-4.0 will depend on libomp-4.0, so when you install clang-4.0 you will get the correct libomp. 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. > 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. -- 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 _______________________________________________ package-review mailing list -- package-review@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to package-review-leave@xxxxxxxxxxxxxxxxxxxxxxx
