Comment 4 for bug 1804762

Hi!

I'm asking for the details because I think they do matter. It could be that the problem is resolved by changing your link flags.

Libomp's packaging looks to be arranged in the correct way. The -dev package contains files ending in .so. Those are symbolic links to a file ending in .so.5 that is contained in the libomp5 package. Usually a compiled program only requires the .so.5 file to be present. This is how it's described in Debian policy: https://www.debian.org/doc/debian-policy/ch-sharedlibs.html

My perception is that when I link a program with -liomp5, I get this dependency: "libomp.so.5 => /usr/lib/x86_64-linux-gnu/libomp.so.5 (0x00007f78ae8b2000)".

Because *.so in -dev package is usually the correct thing to do in Ubuntu, I believe your conclusion that the packaging is wrong, might not be true.

Regards,
Juhani