vcflib: vcflib 1.0.9 conda build "symbol lookup error"
Describe the bug
vcfstreamsort is not functional in the 1.0.9 conda build as it seems to have some error with compilation linking.
To Reproduce
conda create -n vcflib -c bioconda -y -q vcflib=1.0.9
/home/ubuntu/miniconda3/envs/vcflib/bin/vcfstreamsort
gives error:
/home/ubuntu/miniconda3/envs/vcflib/bin/vcfstreamsort: symbol lookup error: /home/ubuntu/miniconda3/envs/vcflib/bin/../lib/libvcflib.so.1: undefined symbol: wavefront_align
Additional context
This manifests as an issue for freebayes parallel which uses vcflib. Error looks like this when running freebayes-parallel:
vcfuniq: symbol lookup error: /venv/bin/../lib/libvcflib.so.1: undefined symbol: wavefront_align
vcfstreamsort: symbol lookup error: /venv/bin/../lib/libvcflib.so.1: undefined symbol: wavefront_align
Traceback (most recent call last):
File "/venv/bin/vcffirstheader", line 10, in <module>
print(line.strip())
BrokenPipeError: [Errno 32] Broken pipe
For any who encounter this (like I did) while running freebayes you “fix” by pinning vcflib to an older release:
conda create -n freebayes_test -c bioconda -y -q vcflib=1.0.3 freebayes=1.3.6
About this issue
- Original URL
- State: closed
- Created 3 years ago
- Reactions: 6
- Comments: 16 (2 by maintainers)
Commits related to this issue
- fix: freebayes wrapper (#1715) <!-- Ensure that the PR title follows conventional commit style (<type>: <description>)--> <!-- Possible types are here: https://github.com/commitizen/conventional-c... — committed to snakemake/snakemake-wrappers by FelixMoelder 3 years ago
- add tabixpp=1.1.0 to the vcflib conda environment — committed to grunwaldlab/pathogensurveillance by cahuparo 3 years ago
Same here… Pinning vcflib to 1.03 and tabixpp to 1.1.0 will do the trick, but I’d like to see a fix to be able to use vcflib 1.0.9
mamba create --name vcflib_new -c bioconda -c conda-forge vcflib=1.0.3 tabixpp=1.1.0Oh, how interesting @maxineliu. I also built it on a cluster and it worked fine. But sure, here is the link to download the SIF.
Hope that helps!
@pjotrp, there is no update on bioconda, which is still at 1.0.9, so the fix in trunk does not really help here, due to the whole issue being about installation via conda. Could you maybe push the fixed version 1.0.10 to bioconda as well? Right now, I still need to work with 1.0.3, for the reasons explained above. Thanks!
Yeah, it works! Thanks so much!
I came back to this issue hoping that it would have been solved, as I would have liked to be able to create a conda environment with vcflib, mainly to be used with Snakemake, but to no avail. Therefore, I settled to create a singularity recipe that solves the issues with vcfwave and the many library dependencies. If it might be of interest to anyone, it’s here
@mencian, you made some quite extensive changes in the way we build vcflib in Bioconda here: https://github.com/bioconda/bioconda-recipes/commit/032977aed9bcf6941284034e443b234e36af62e5, after which the error seems to occur. Would you be so kind to have a look what might be wrong?
cc @bgruening