On 2015-01-27 11:40, Maarten wrote:
Here you go:
> ldd
<INSTALL_PATH>/anaconda/envs/fenics27/lib/python2.7/site-packages/dolfin/cpp/_common.so
| grep libbz2
ldd: warning: you do not have execution permission for
`<INSTALL_PATH>/anaconda/envs/fenics27/lib/python2.7/site-packages/dolfin/cpp/_common.so'
<INSTALL_PATH>/anaconda/envs/fenics27/lib/python2.7/site-packages/dolfin/cpp/_common.so:
/lib64/libc.so.6: version `GLIBC_2.14' not found (required by
<INSTALL_PATH>/anaconda/envs/fenics27/lib/python2.7/site-packages/dolfin/cpp/../../../../libboost_filesystem.so.1.55.0)
<INSTALL_PATH>/anaconda/envs/fenics27/lib/python2.7/site-packages/dolfin/cpp/_common.so:
/lib64/libc.so.6: version `GLIBC_2.14' not found (required by
<INSTALL_PATH>/anaconda/envs/fenics27/lib/python2.7/site-packages/dolfin/cpp/../../../../libboost_program_options.so.1.55.0)
libbz2.so.1.0 => not found
Okay, I suspect you are installing some version cached in your system: I
say this because boost is trying to locate libc 2.14, but that was for
the package I compiled nearly a month ago in Linux Mint. I had already
recompiled it in CentOS 6.6, checked in my system and my linking
information is different than yours.
So what I think will solve the problem is:
1. Remove the boost 1.55 conda package from all your environments. If
you only have one:
(fenics27) $ conda remove boost
2. Clean the conda cache, both the packages and the tarballs. Important:
if you type these commands and boost is not in the list of things to
remove, you need to go to step 1 and find in which environment is boost
still installed. conda won't clean it from the cache until it's used
nowhere.
$ conda clean --packages
$ conda clean --tarballs
3. Go to step 4 :)
4. Reinstall it:
(fenics27) $ conda install "boost=1.55" --channel
https://conda.binstar.org/juanlu001/channel/fenics:1.4.0:centos
5. Repeat the ldd steps. If boost is still looking for GLIBC 2.14 then
I'm afraid you have to go back to step 1.
6. Our libbz2 libraries are the same, so there are good chances the next
one will be a happy email with a working FEniCS installation :)
7. You always have the option of removing the created environment with
all its packages, clean all the caches and start afresh:
$ conda remove -n fenics27 --all
$ conda clean --packages
$ conda clean --tarballs
I hope this helps!
Regards,
Juan Luis
_______________________________________________
fenics-support mailing list
[email protected]
http://fenicsproject.org/mailman/listinfo/fenics-support
