use patch to fix finding libraries when linking ImageMagick#21640
Conversation
|
Test report by @Flamefire |
|
Test report by @Flamefire |
|
Test report by @Flamefire |
|
Test report by @Flamefire |
|
Test report by @akesandgren |
|
This can also be solved by explicitly adding libheif as a dependency (which it really should be anyway since it is directly used, see configure step) Only tested with ImageMagick-7.1.1-15-GCCcore-12.3.0.eb though |
|
@akesandgren Can you post the relevant part of the configure step for reference please? I'm also not sure if libheif changes anything for this issue, it seems unrelated. But if it is used we should either add it (we don't yet, do we? So where does it come from or is it optional?) independent of this. IIRC the issue is not (only?) building ImageMagick but e.g. linking it to HarfBuzz. Did you test that with the libheif dependency instead of this patch? |
|
This is from 7.1.1-15: It's being brought in by JasPer, and the problem I'm seeing without this patch and without it listed explicitly is: With an explicit libheif in dependencies everything works. |
How is that possible? IIRC there is no difference by LMod or EasyBuild whether a module is a direct or indirect dependency, unless of course it is only a build-dep of a dependency which here it isn't. And it seemingly hasn't been an issue before/for others, has it? Could you compare the environments for the 2 cases? |
|
The difference is that without libheif being explicit there is no -L/..../libheif/version/lib in LDFLAGS |
That explains why it works (LIBRARYPATH gets cleaned by ImageMagick without the patch). And we set |
|
Going in, thanks @Flamefire! |
libheif is a new addition to JasPer. So this wasn't an issue before. Harfbuzz should would be an issue though without this patch: In GCC/13.3 toolchains we use MesonNinja for HarfBuzz so without it being an explicit dependency for ImageMagick it would fail in the same way as libheif. |
(created using
eb --new-pr)