numba: GLIBC version error in 0.55RC1 on AArch64

Cross-post from https://numba.discourse.group/t/numba-0-55-0-rc1/1075/2?u=gmarkall for tracking

On a Jetson AGX Xavier (AArch64, Ubuntu 18.04), I create an environment with:

conda create -n testnumba055 python=3.9 numba::numba=0.55.0rc1 ipython

Then when running Numba in the environment I get:

(testnumba055) gmarkall@gm-agx:~$ python -c "import numba"
Traceback (most recent call last):
  File "<string>", line 1, in <module>
  File "/data/gmarkall/miniforge/envs/testnumba055/lib/python3.9/site-packages/numba/__init__.py", line 38, in <module>
    from numba.core.decorators import (cfunc, generated_jit, jit, njit, stencil,
  File "/data/gmarkall/miniforge/envs/testnumba055/lib/python3.9/site-packages/numba/core/decorators.py", line 12, in <module>
    from numba.stencils.stencil import stencil
  File "/data/gmarkall/miniforge/envs/testnumba055/lib/python3.9/site-packages/numba/stencils/stencil.py", line 11, in <module>
    from numba.core import types, typing, utils, ir, config, ir_utils, registry
  File "/data/gmarkall/miniforge/envs/testnumba055/lib/python3.9/site-packages/numba/core/ir_utils.py", line 16, in <module>
    from numba.core.extending import _Intrinsic
  File "/data/gmarkall/miniforge/envs/testnumba055/lib/python3.9/site-packages/numba/core/extending.py", line 19, in <module>
    from numba.core.pythonapi import box, unbox, reflect, NativeValue  # noqa: F401
  File "/data/gmarkall/miniforge/envs/testnumba055/lib/python3.9/site-packages/numba/core/pythonapi.py", line 12, in <module>
    from numba import _helperlib
ImportError: /lib/aarch64-linux-gnu/libm.so.6: version `GLIBC_2.29' not found (required by /data/gmarkall/miniforge/envs/testnumba055/lib/python3.9/site-packages/numba/_helperlib.cpython-39-aarch64-linux-gnu.so)

About this issue

  • Original URL
  • State: closed
  • Created 3 years ago
  • Comments: 17 (17 by maintainers)

Most upvoted comments

@gmarkall the new docker container has been deployed to our anaconda internal build farm. Let’s keep this ticket open however, until a new 0.56.0dev0 becomes available and then we can test that.