-
Notifications
You must be signed in to change notification settings - Fork 28
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
symbol not found #190
Comments
Would suggest including enough info to explain how things were installed so someone else can reproduce. If Conda, |
this is the output of
I removed the whole conda environment and reinstalled z5py, still got the same error. I used python 3.8 this time. These are the packages I got.
z5py used to work in my laptop with python 3.7. I need to upgrade to 3.8 or 3.9 since another package used new features of python. |
Also please include |
|
It looks like this mixing packages from |
@jakirkham I am currently trying to build using std::filesystem instead of boost::filesystem to get rid of the boost linking all together and make z5py easier to install. |
@jakirkham the |
No |
I created a fresh environment but still got the same symbol error.
all the packages are from
|
My guess is that the boost version is incompatible with the one z5py was built with. In theory conda-forge should pin the correct version, but maybe this fails here? I am trying to update the conda-forge build to use std::filesystem, so that linking to boost is not necessary any longer in conda-forge/z5py-feedstock#47. |
@jingpengw there is a z5py version available on conda-forge now that does not rely on boost. |
can not find this version.
|
It's listed here: https://anaconda.org/conda-forge/z5py/files. But was only added ~ 30 minutes ago. |
conda-forge mirrors packages to a CDN (hence the delay) |
I just tried, it works! thanks a lot! @constantinpape @jakirkham |
it is probably some library version conflict in my environment.
When I installed z5py, libboost 1.77 was installed.
has anyone seen this error and has a solution?
The text was updated successfully, but these errors were encountered: