Question 46647 in Debian Question posted in
The oficial documentation can be found here.

'GLIBCXX_3.4.30' not found for librosa in conda virtual environment (after trying out a lot of solutions)? – Debian

I am trying to import librosa, but I am thrown with this error:

/home/lakshya/anaconda3/envs/tff_env/lib/python3.9/site-packages/zmq/backend/cython/../../../../.././libstdc++.so.6: version `GLIBCXX_3.4.30' not found (required by /home/lakshya/anaconda3/envs/tff_env/lib/python3.9/site-packages/scipy/fft/_pocketfft/pypocketfft.cpython-39-x86_64-linux-gnu.so)

I tried the following to fix it based on the other similar questions that I browsed through:

  1. sudo apt-get install libstdc++6

    It’s output: libstdc++6 is already the newest version (10.2.1-6).

  2. sudo apt-get dist-upgrade

    It’s output: 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

  3. strings /usr/lib/x86_64-linux-gnu/libstdc++.so.6 | grep GLIBCXX

    It’s output: GLIBCXX version up to GLIBCXX_3.4.28

  4. conda install libgcc in my virtual env "tff_env"

    It’s output: libgcc-7.2.0 installed in tff_env

  5. Pip installed the libgcc package in the virtual environment as well. Didn’t work.

What can I do?

My OS: Debian GNU/Linux 11 (bullseye)

Tags:

10

Answers


  1. Chosen as BEST ANSWER
    0

    So what worked for me was to manually remove Python3.10 which I had installed using make altinstall and upgrade scipy to the latest version.


  2. 0

    Just been tackling a similar problem, it looks like you need to ensure you have the latest version of gcc. Running:

    conda install -c conda-forge gcc=12.1.0

    Fixed the error for me.

    Login or Signup to reply.
  3. 0

    One solution that fixed this problem for while trying to run mujoco or mujoco-py was as follows

    OSError: /home/ubuntu/anaconda3/envs/tensorflow_p36/bin/../lib/libstdc++.so.6: version `GLIBCXX_3.4.20′ not foundwhen starting ipython. For some reason this library isnt in the
    anaconda environments libstdc++.so.6. It is in the base ubuntu
    library. So link the anaconda version of this library back to the os
    version:

    cd /home/ubuntu/anaconda3/envs/tensorflow_p36/lib
mv libstdc++.so.6 libstdc++.so.6.old
ln -s /usr/lib/x86_64-linux-gnu/libstdc++.so.6 libstdc++.so.6

    credits: https://bcourses.berkeley.edu/courses/1478831/pages/glibcxx-missing

    Login or Signup to reply.
  4. 0

    The soln given above doesn’t work for me. I got it working by downgrading my scipy from 1.9.1 to 1.6.1.

    Login or Signup to reply.
  5. 0

    If the accepted answer didn’t work, try this

    I had the same conditions as the original poster and the accepted answer didn’t work as conda was taking forever. I tried down-versioning scipy from 1.9.3 to 1.9.1 and it did work.

    You can use the following command to do so:

    conda install -c anaconda scipy==1.9.1
    Login or Signup to reply.
  6. 0

    After my search on anaconda packages, I found only the package "libstdcxx" will substantially bring new "libstdc++.so.6" file to the conda environment (while "gcc", "gcc_linux-64", and "libgcc-ng" cannot).
    Thus, installing the following package can fix this problem for me.

    conda install -c conda-forge libstdcxx-ng=12

    PS: dfcorbin’s answer conda install -c conda-forge gcc=12 not works for me.

    Login or Signup to reply.
  7. 0

    None of the other answers worked for me. This did work though:

    pip install scikit-build
    Login or Signup to reply.
  8. 0

    None of the above answers worked for me, unfortunately. What I ended up doing was to manually inspect the libstdc++.so.6 file.

    First, I checked the system file, and it returned nothing on my side:

    strings /usr/lib/x86_64-linux-gnu/libstdc++.so.6 | grep GLIBCXX_3.4.30

    Then, I took a look the conda file, and it was there:

    strings /path-to-your-conda/envs/your-env-name/lib/libstdc++.so.6 | grep GLIBCXX_3.4.30

    This indicates that the simple solution is to append the path to the conda file to the LD_LIBRARY_PATH.

    export LD_LIBRARY_PATH=/path-to-your-conda/envs/your-env-name/lib:$LD_LIBRARY_PATH

    Login or Signup to reply.
  9. 0

    In some cases, there exist multiple installations of glibcxx and runtime your app wants to connect to it but finds the library in the wrong place. It can be solved by changing the imported libraries’ order. The problem has been solved by importing librosa on top of the running script.

    Login or Signup to reply.
  10. 0

    None of the other answers worked for me, but this solved the problem:

    import torch
    Login or Signup to reply.
Please signup or login to give your own answer.

Back To Top
Search