Open minrk opened 3 weeks ago
@jsquyres Hey, is this intended behavior? Regarding the condition on when to install pkg-config files?
@minrk just fyi - but your link seems to point to an unofficial fork.
Many thanks for the report, @minrk.
Does https://github.com/open-mpi/ompi/pull/12627 fix your issue? (that PR is against main, but it should probably apply pretty easily to the v5.0.x branch)
@jsquyres yes, that fixes it. Thank you!
Sorry for the weird link, that fork keeps coming up first in my searches. Fixed it.
Background information
I'm exploring the consequences of enabling
--enable-script-wrapper-compilers
, and noticed that enabling the script wrappers prevents installation of pkg-config files.What version of Open MPI are you using? (e.g., v4.1.6, v5.0.1, git branch name and hash, etc.)
v5.0.3
Describe how Open MPI was installed (e.g., from a source/distribution tarball, from a git clone, from an operating system distribution package, etc.)
From source, with this script (for conda-forge, but currently running by hand for testing)
I think the only relevant argument there is
--enable-script-wrapper-compilers
, the rest should probably be ignored.Please describe the system on which you are running
Details of the problem
The openmpi pkg-config files are conditionally installed, and the condition is:
when presumably it should be:
Which means they don't get installed if
--enable-script-wrapper-compilers
is given. The files are generated correctly, they just get left out of installation, so I imagine this is not deliberate. Addingcp -v ompi/tools/wrappers/*.pc $PREFIX/lib/pkgconfig/
after installation produces the desired result.Perhaps relevant to https://github.com/open-mpi/ompi/issues/10572 where
--enable-script-wrapper-compilers
is discussed in reference to pkg-config, but it is not mentioned that enabling it removes all pkg-config files.