-
Notifications
You must be signed in to change notification settings - Fork 2.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
lib/libxml2.so.2: undefined reference to `gzopen64@ZLIB_1.2.3.3' #5758
Comments
probably that. edit: compiler wrappers should inject rpath's so ideally packages built with Spack shall not depend on environment (i.e. |
Hi all, I just noticed we have the same issue on our setup as well. I can confirm the error with the following compiler/openmpi implementations:
If there is something I can contribute that would aid debugging please let me know. I suppose it should be something in the libxml2 build, right? |
Knowing the following would be useful:
Can you replicate the results in the original post where you succeed when a zlib module is loaded? If so, is this a module for a spack-built zlib? |
Hi @scheibelp,
I don't have spack output files as this was observed when building an application that is not in the Spack manifest. Actually, I don't have any output files but I could re-generate something if needed. |
That is useful to know! FYI RPATHs don't affect linking, only how libraries are found at runtime. When you build a package with Spack it also does work to add If you are building this package outside of Spack because you are developing it, then Anyhow I'm closing this because I think the cause is known and not a Spack bug. But if you disagree feel free to reopen. |
I was trying to compile a software (Serpent 2 from VTT) out of the spack environment by loading modules for gcc-7.2.0, openmpi-3.0.0 and libgd.
I get the following error message:
However, the program successfully compiles if I also load the module zlib, which is a dependency of libxml2, which is a dependency of openmpi.
This also affects the program execution. If I unload all the modules except zlib, it executes fine. If I unload zlib, I get:
Would this indicate that libxml2 did not get configured with relative paths to zlib? Is this expected and a current limitation of libxml2 configurations or a package problem? Or neither and I just don't know what I'm doing?
The text was updated successfully, but these errors were encountered: