Skip to content
This repository has been archived by the owner on Mar 16, 2022. It is now read-only.

Problem with HDF5 and downloaded binary #83

Closed
pb-cdunn opened this issue Jul 14, 2017 · 4 comments
Closed

Problem with HDF5 and downloaded binary #83

pb-cdunn opened this issue Jul 14, 2017 · 4 comments

Comments

@pb-cdunn
Copy link

pb-cdunn commented Jul 14, 2017

+ /home/UNIXHOME/cdunn/repo/gh/FALCON-integrate/FALCON-examples/run/greg200k-sv2/DOWN/bin/pbalign -h
Warning! ***HDF5 library version mismatched error***
The HDF5 header files used to compile this application do not match
the version used by the HDF5 library to which this application is linked.
Data corruption or segmentation faults may occur if the application continues.
This can happen when an application was compiled by one version of HDF5 but
linked with a different version of static or shared HDF5 library.
You should recompile the application or check your shared library related
settings such as 'LD_LIBRARY_PATH'.
You can, at your own risk, disable this warning by setting the environment
variable 'HDF5_DISABLE_VERSION_CHECK' to a value of '1'.
Setting it to 2 or higher will suppress the warning messages totally.
Headers are 1.8.16, library is 1.8.17
@pb-cdunn
Copy link
Author

$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:    Ubuntu 14.04 LTS
Release:        14.04
Codename:       trusty

@pb-cdunn
Copy link
Author

Also happens on Centos6.6.

@pb-cdunn
Copy link
Author

Apparently, our Anaconda picks up its own shared libraries, despite my LD_LIBRARY_PATH.

@pb-cdunn
Copy link
Author

export HDF5_DISABLE_VERSION_CHECK=1

Seems to work for pbalign, but fails for ConsensusCore.

ImportError: /mnt/software/a/anaconda2/4.2.0/bin/../lib/libstdc++.so.6: version `GLIBCXX_3.4.20' not found (required by /home/UNIXHOME/cdunn/repo/gh/FALCON-integrate/FALCON-examples/run/greg200k-sv2/DOWN/lib/python2.7/site-packages/ConsensusCore-1.0.2-py2.7.egg/_ConsensusCore.so)

Yes, I first ran module load gcc/4.9.2, which solved the glibcxx problem for other Pythons. Possibly, Anaconda uses its own libgcc too? Maybe via rpath when built?

Other Python works fine. Closing.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant