Set $PKG_CONFIG in pkgconf modules#22005
Conversation
|
@boegelbot: please test @ generoso |
|
@smoors: Request for testing this PR well received on login1 PR test command '
Test results coming soon (I hope)... Details- notification for comment with ID 2538723522 processed Message to humans: this is just bookkeeping information for me, |
|
Test report by @boegelbot |
|
the installations /tmp all succeeded, let's install for real now |
|
@boegelbot: please test @ generoso |
|
@smoors: Request for testing this PR well received on login1 PR test command '
Test results coming soon (I hope)... Details- notification for comment with ID 2538878352 processed Message to humans: this is just bookkeeping information for me, |
|
Test report by @boegelbot |
|
@boegelbot please test @ jsc-zen3 |
|
@smoors: Request for testing this PR well received on jsczen3l1.int.jsc-zen3.fz-juelich.de PR test command '
Test results coming soon (I hope)... Details- notification for comment with ID 2539153881 processed Message to humans: this is just bookkeeping information for me, |
|
Test report by @boegelbot |
|
Going in, thanks @Micket! |
$PKG_CONFIG in pkgconf modules
(created using
eb --new-pr)I believe this would solve #21980
It also makes it needless to add the extra export to ImageMagick so i cleaned those up.
This prevents configure tools from trying to find their own pkg-config somewhere (even when we have it in PATH). I think it's a cross-compilation thing, where they look for
x86_64-xxx-linux-gnu-pkg-configby default or something like that. This should tell those tools to no; use this exakt PKG_CONFIG please.Untested.