Arch Linux

Please read this before reporting a bug:

Do NOT report bugs when a package is just outdated, or it is in Unsupported. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!

FS#65905 - [openmpi] Installation of 4.0.3-1 Does Not Create Symlink /usr/lib/pkgconfig/ompi-fort.pc

Attached to Project: Arch Linux
Opened by Ron Lovell (jrl64) - Friday, 20 March 2020, 15:13 GMT
Last edited by freswa (frederik) - Friday, 20 March 2020, 20:37 GMT
Task Type Bug Report
Category Packages: Extra
Status Assigned
Assigned To Levente Polyak (anthraxx)
Architecture x86_64
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 0%
Votes 0
Private No



Installation of the openmpi 4.0.3-1 package did not install a symlink

/usr/lib/pkgconfig/ompi-fort.pc -> /usr/lib/openmpi/pkgconfig/ompi-fort.pc

as it did for the other ompi-*.pc files in /usr/lib/openmpi/pkgconfig/. I'm assuming that was an oversight. Unless a user takes action to include /usr/lib/openmpi/pkgconfig/ in their PKG_CONFIG_PATH, the pkgconf(1) and pkg-config(1) utilities will not find it. In my case, meson(1) could not find 'ompi-fort' in a call dependency('ompi-fort',...).

As a workaround I manually installed the missing symlink. An alternative workaround would be to add /usr/lib/openmpi/pkgconfig/ to my PKG_CONFIG_PATH.

Additional info:

* openmpi 4.0.3-1

Steps to reproduce:

$ pkgconf -libs ompi-fort

Currently it shows that package ompi-fort was not found in the pkg-config search path. It should instead show the same output as this:

$ PKG_CONFIG_PATH=${PKG_CONFIG_PATH}:/usr/lib/openmpi/pkgconfig pkgconf -libs ompi-fort
This task depends upon