[Bug]: unable to install latest pybamm on aarch64

[chuckliu1979]

PyBaMM Version

Pybamm 25.1.1

Python Version

python 3.10

Describe the bug

since solvers moved to new package pybammsolvers, i can not install pybamm on aarch64, even install pybammsolvers directly:

pip install pybammsolvers
Defaulting to user installation because normal site-packages is not writeable
Collecting pybammsolvers
Using cached pybammsolvers-0.1.0.tar.gz (44 kB)
Installing build dependencies ... done
Getting requirements to build wheel ... done
Preparing metadata (pyproject.toml) ... done
Collecting casadi (from pybammsolvers)
Using cached casadi-3.6.7-cp310-none-manylinux2014_aarch64.whl.metadata (2.2 kB)
Collecting numpy<2.0 (from pybammsolvers)
Using cached numpy-1.26.4-cp310-cp310-manylinux_2_17_aarch64.manylinux2014_aarch64.whl.metadata (62 kB)
Using cached numpy-1.26.4-cp310-cp310-manylinux_2_17_aarch64.manylinux2014_aarch64.whl (14.2 MB)
Using cached casadi-3.6.7-cp310-none-manylinux2014_aarch64.whl (43.9 MB)
Building wheels for collected packages: pybammsolvers
Building wheel for pybammsolvers (pyproject.toml) ... error
error: subprocess-exited-with-error

× Building wheel for pybammsolvers (pyproject.toml) did not run successfully.
│ exit code: 1
╰─> [321 lines of output]
running bdist_wheel
running build
running build_py
creating build/lib.linux-aarch64-cpython-310/pybammsolvers
copying src/pybammsolvers/version.py -> build/lib.linux-aarch64-cpython-310/pybammsolvers
copying src/pybammsolvers/init.py -> build/lib.linux-aarch64-cpython-310/pybammsolvers
running egg_info
writing src/pybammsolvers.egg-info/PKG-INFO
writing dependency_links to src/pybammsolvers.egg-info/dependency_links.txt
writing requirements to src/pybammsolvers.egg-info/requires.txt
writing top-level names to src/pybammsolvers.egg-info/top_level.txt
reading manifest file 'src/pybammsolvers.egg-info/SOURCES.txt'
adding license file 'LICENSE'
writing manifest file 'src/pybammsolvers.egg-info/SOURCES.txt'
/tmp/pip-build-env-fbr81j_m/overlay/lib/python3.10/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'pybammsolvers.idaklu_source' is absent from the packages configuration.
!!

          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'pybammsolvers.idaklu_source' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.
  
          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'pybammsolvers.idaklu_source' is explicitly added
          to the `packages` configuration field.
  
          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).
  
          You can read more about "package discovery" on setuptools documentation page:
  
          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
  
          If you don't want 'pybammsolvers.idaklu_source' to be distributed and are
          already explicitly excluding 'pybammsolvers.idaklu_source' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.
  
          You can read more about "package data files" on setuptools documentation page:
  
          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html
  
  
          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************
  
  !!
    check.warn(importable)
  /tmp/pip-build-env-fbr81j_m/overlay/lib/python3.10/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'pybammsolvers.idaklu_source.Expressions' is absent from the `packages` configuration.
  !!
  
          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'pybammsolvers.idaklu_source.Expressions' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.
  
          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'pybammsolvers.idaklu_source.Expressions' is explicitly added
          to the `packages` configuration field.
  
          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).
  
          You can read more about "package discovery" on setuptools documentation page:
  
          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
  
          If you don't want 'pybammsolvers.idaklu_source.Expressions' to be distributed and are
          already explicitly excluding 'pybammsolvers.idaklu_source.Expressions' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.
  
          You can read more about "package data files" on setuptools documentation page:
  
          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html
  
  
          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************
  
  !!
    check.warn(importable)
  /tmp/pip-build-env-fbr81j_m/overlay/lib/python3.10/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'pybammsolvers.idaklu_source.Expressions.Base' is absent from the `packages` configuration.
  !!
  
          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'pybammsolvers.idaklu_source.Expressions.Base' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.
  
          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'pybammsolvers.idaklu_source.Expressions.Base' is explicitly added
          to the `packages` configuration field.
  
          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).
  
          You can read more about "package discovery" on setuptools documentation page:
  
          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
  
          If you don't want 'pybammsolvers.idaklu_source.Expressions.Base' to be distributed and are
          already explicitly excluding 'pybammsolvers.idaklu_source.Expressions.Base' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.
  
          You can read more about "package data files" on setuptools documentation page:
  
          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html
  
  
          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************
  
  !!
    check.warn(importable)
  /tmp/pip-build-env-fbr81j_m/overlay/lib/python3.10/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'pybammsolvers.idaklu_source.Expressions.Casadi' is absent from the `packages` configuration.
  !!
  
          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'pybammsolvers.idaklu_source.Expressions.Casadi' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.
  
          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'pybammsolvers.idaklu_source.Expressions.Casadi' is explicitly added
          to the `packages` configuration field.
  
          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).
  
          You can read more about "package discovery" on setuptools documentation page:
  
          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
  
          If you don't want 'pybammsolvers.idaklu_source.Expressions.Casadi' to be distributed and are
          already explicitly excluding 'pybammsolvers.idaklu_source.Expressions.Casadi' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.
  
          You can read more about "package data files" on setuptools documentation page:
  
          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html
  
  
          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************
  
  !!
    check.warn(importable)
  /tmp/pip-build-env-fbr81j_m/overlay/lib/python3.10/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'pybammsolvers.idaklu_source.Expressions.IREE' is absent from the `packages` configuration.
  !!
  
          ********************************************************************************
          ############################
          # Package would be ignored #
          ############################
          Python recognizes 'pybammsolvers.idaklu_source.Expressions.IREE' as an importable package[^1],
          but it is absent from setuptools' `packages` configuration.
  
          This leads to an ambiguous overall configuration. If you want to distribute this
          package, please make sure that 'pybammsolvers.idaklu_source.Expressions.IREE' is explicitly added
          to the `packages` configuration field.
  
          Alternatively, you can also rely on setuptools' discovery methods
          (for example by using `find_namespace_packages(...)`/`find_namespace:`
          instead of `find_packages(...)`/`find:`).
  
          You can read more about "package discovery" on setuptools documentation page:
  
          - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
  
          If you don't want 'pybammsolvers.idaklu_source.Expressions.IREE' to be distributed and are
          already explicitly excluding 'pybammsolvers.idaklu_source.Expressions.IREE' via
          `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
          you can try to use `exclude_package_data`, or `include-package-data=False` in
          combination with a more fine grained `package-data` configuration.
  
          You can read more about "package data files" on setuptools documentation page:
  
          - https://setuptools.pypa.io/en/latest/userguide/datafiles.html
  
  
          [^1]: For Python, any directory (with suitable naming) can be imported,
                even if it does not contain any `.py` files.
                On the other hand, currently there is no concept of package data
                directory, all directories are treated like packages.
          ********************************************************************************
  
  !!
    check.warn(importable)
  copying src/pybammsolvers/idaklu.cpp -> build/lib.linux-aarch64-cpython-310/pybammsolvers
  creating build/lib.linux-aarch64-cpython-310/pybammsolvers/idaklu_source
  copying src/pybammsolvers/idaklu_source/IDAKLUSolver.cpp -> build/lib.linux-aarch64-cpython-310/pybammsolvers/idaklu_source
  copying src/pybammsolvers/idaklu_source/IDAKLUSolver.hpp -> build/lib.linux-aarch64-cpython-310/pybammsolvers/idaklu_source
  copying src/pybammsolvers/idaklu_source/IDAKLUSolverGroup.cpp -> build/lib.linux-aarch64-cpython-310/pybammsolvers/idaklu_source
  copying src/pybammsolvers/idaklu_source/IDAKLUSolverGroup.hpp -> build/lib.linux-aarch64-cpython-310/pybammsolvers/idaklu_source
  copying src/pybammsolvers/idaklu_source/IDAKLUSolverOpenMP.hpp -> build/lib.linux-aarch64-cpython-310/pybammsolvers/idaklu_source
  copying src/pybammsolvers/idaklu_source/IDAKLUSolverOpenMP.inl -> build/lib.linux-aarch64-cpython-310/pybammsolvers/idaklu_source
  copying src/pybammsolvers/idaklu_source/IDAKLUSolverOpenMP_solvers.cpp -> build/lib.linux-aarch64-cpython-310/pybammsolvers/idaklu_source
  copying src/pybammsolvers/idaklu_source/IDAKLUSolverOpenMP_solvers.hpp -> build/lib.linux-aarch64-cpython-310/pybammsolvers/idaklu_source
  copying src/pybammsolvers/idaklu_source/IdakluJax.cpp -> build/lib.linux-aarch64-cpython-310/pybammsolvers/idaklu_source
  copying src/pybammsolvers/idaklu_source/IdakluJax.hpp -> build/lib.linux-aarch64-cpython-310/pybammsolvers/idaklu_source
  copying src/pybammsolvers/idaklu_source/Options.cpp -> build/lib.linux-aarch64-cpython-310/pybammsolvers/idaklu_source
  copying src/pybammsolvers/idaklu_source/Options.hpp -> build/lib.linux-aarch64-cpython-310/pybammsolvers/idaklu_source
  copying src/pybammsolvers/idaklu_source/Solution.cpp -> build/lib.linux-aarch64-cpython-310/pybammsolvers/idaklu_source
  copying src/pybammsolvers/idaklu_source/Solution.hpp -> build/lib.linux-aarch64-cpython-310/pybammsolvers/idaklu_source
  copying src/pybammsolvers/idaklu_source/SolutionData.cpp -> build/lib.linux-aarch64-cpython-310/pybammsolvers/idaklu_source
  copying src/pybammsolvers/idaklu_source/SolutionData.hpp -> build/lib.linux-aarch64-cpython-310/pybammsolvers/idaklu_source
  copying src/pybammsolvers/idaklu_source/common.cpp -> build/lib.linux-aarch64-cpython-310/pybammsolvers/idaklu_source
  copying src/pybammsolvers/idaklu_source/common.hpp -> build/lib.linux-aarch64-cpython-310/pybammsolvers/idaklu_source
  copying src/pybammsolvers/idaklu_source/idaklu_solver.hpp -> build/lib.linux-aarch64-cpython-310/pybammsolvers/idaklu_source
  copying src/pybammsolvers/idaklu_source/observe.cpp -> build/lib.linux-aarch64-cpython-310/pybammsolvers/idaklu_source
  copying src/pybammsolvers/idaklu_source/observe.hpp -> build/lib.linux-aarch64-cpython-310/pybammsolvers/idaklu_source
  copying src/pybammsolvers/idaklu_source/sundials_functions.hpp -> build/lib.linux-aarch64-cpython-310/pybammsolvers/idaklu_source
  copying src/pybammsolvers/idaklu_source/sundials_functions.inl -> build/lib.linux-aarch64-cpython-310/pybammsolvers/idaklu_source
  creating build/lib.linux-aarch64-cpython-310/pybammsolvers/idaklu_source/Expressions
  copying src/pybammsolvers/idaklu_source/Expressions/Expressions.hpp -> build/lib.linux-aarch64-cpython-310/pybammsolvers/idaklu_source/Expressions
  creating build/lib.linux-aarch64-cpython-310/pybammsolvers/idaklu_source/Expressions/Base
  copying src/pybammsolvers/idaklu_source/Expressions/Base/Expression.hpp -> build/lib.linux-aarch64-cpython-310/pybammsolvers/idaklu_source/Expressions/Base
  copying src/pybammsolvers/idaklu_source/Expressions/Base/ExpressionSet.hpp -> build/lib.linux-aarch64-cpython-310/pybammsolvers/idaklu_source/Expressions/Base
  copying src/pybammsolvers/idaklu_source/Expressions/Base/ExpressionTypes.hpp -> build/lib.linux-aarch64-cpython-310/pybammsolvers/idaklu_source/Expressions/Base
  creating build/lib.linux-aarch64-cpython-310/pybammsolvers/idaklu_source/Expressions/Casadi
  copying src/pybammsolvers/idaklu_source/Expressions/Casadi/CasadiFunctions.cpp -> build/lib.linux-aarch64-cpython-310/pybammsolvers/idaklu_source/Expressions/Casadi
  copying src/pybammsolvers/idaklu_source/Expressions/Casadi/CasadiFunctions.hpp -> build/lib.linux-aarch64-cpython-310/pybammsolvers/idaklu_source/Expressions/Casadi
  creating build/lib.linux-aarch64-cpython-310/pybammsolvers/idaklu_source/Expressions/IREE
  copying src/pybammsolvers/idaklu_source/Expressions/IREE/IREEBaseFunction.hpp -> build/lib.linux-aarch64-cpython-310/pybammsolvers/idaklu_source/Expressions/IREE
  copying src/pybammsolvers/idaklu_source/Expressions/IREE/IREEFunction.hpp -> build/lib.linux-aarch64-cpython-310/pybammsolvers/idaklu_source/Expressions/IREE
  copying src/pybammsolvers/idaklu_source/Expressions/IREE/IREEFunctions.cpp -> build/lib.linux-aarch64-cpython-310/pybammsolvers/idaklu_source/Expressions/IREE
  copying src/pybammsolvers/idaklu_source/Expressions/IREE/IREEFunctions.hpp -> build/lib.linux-aarch64-cpython-310/pybammsolvers/idaklu_source/Expressions/IREE
  copying src/pybammsolvers/idaklu_source/Expressions/IREE/ModuleParser.cpp -> build/lib.linux-aarch64-cpython-310/pybammsolvers/idaklu_source/Expressions/IREE
  copying src/pybammsolvers/idaklu_source/Expressions/IREE/ModuleParser.hpp -> build/lib.linux-aarch64-cpython-310/pybammsolvers/idaklu_source/Expressions/IREE
  copying src/pybammsolvers/idaklu_source/Expressions/IREE/iree_jit.cpp -> build/lib.linux-aarch64-cpython-310/pybammsolvers/idaklu_source/Expressions/IREE
  copying src/pybammsolvers/idaklu_source/Expressions/IREE/iree_jit.hpp -> build/lib.linux-aarch64-cpython-310/pybammsolvers/idaklu_source/Expressions/IREE
  running build_ext
  CMake Warning:
    Ignoring extra path from command line:
  
     "/tmp/pip-install-ml11b504/pybammsolvers_a88d40bc6d0547688960ec5d0c66dd00"
  
  
  CMake Error: The source directory "/tmp/pip-install-ml11b504/pybammsolvers_a88d40bc6d0547688960ec5d0c66dd00" does not appear to contain CMakeLists.txt.
  Specify --help for usage, or press the help button on the CMake GUI.
  ---------- Running CMake for IDAKLU solver ----------------------------------------
  Traceback (most recent call last):
    File "/home/liuchengkun/.local/lib/python3.10/site-packages/pip/_vendor/pyproject_hooks/_in_process/_in_process.py", line 389, in <module>
      main()
    File "/home/liuchengkun/.local/lib/python3.10/site-packages/pip/_vendor/pyproject_hooks/_in_process/_in_process.py", line 373, in main
      json_out["return_val"] = hook(**hook_input["kwargs"])
    File "/home/liuchengkun/.local/lib/python3.10/site-packages/pip/_vendor/pyproject_hooks/_in_process/_in_process.py", line 280, in build_wheel
      return _build_backend().build_wheel(
    File "/tmp/pip-build-env-fbr81j_m/overlay/lib/python3.10/site-packages/setuptools/build_meta.py", line 438, in build_wheel
      return _build(['bdist_wheel', '--dist-info-dir', str(metadata_directory)])
    File "/tmp/pip-build-env-fbr81j_m/overlay/lib/python3.10/site-packages/setuptools/build_meta.py", line 426, in _build
      return self._build_with_temp_dir(
    File "/tmp/pip-build-env-fbr81j_m/overlay/lib/python3.10/site-packages/setuptools/build_meta.py", line 407, in _build_with_temp_dir
      self.run_setup()
    File "/tmp/pip-build-env-fbr81j_m/overlay/lib/python3.10/site-packages/setuptools/build_meta.py", line 320, in run_setup
      exec(code, locals())
    File "<string>", line 285, in <module>
    File "/tmp/pip-build-env-fbr81j_m/overlay/lib/python3.10/site-packages/setuptools/__init__.py", line 117, in setup
      return distutils.core.setup(**attrs)
    File "/tmp/pip-build-env-fbr81j_m/overlay/lib/python3.10/site-packages/setuptools/_distutils/core.py", line 186, in setup
      return run_commands(dist)
    File "/tmp/pip-build-env-fbr81j_m/overlay/lib/python3.10/site-packages/setuptools/_distutils/core.py", line 202, in run_commands
      dist.run_commands()
    File "/tmp/pip-build-env-fbr81j_m/overlay/lib/python3.10/site-packages/setuptools/_distutils/dist.py", line 983, in run_commands
      self.run_command(cmd)
    File "/tmp/pip-build-env-fbr81j_m/overlay/lib/python3.10/site-packages/setuptools/dist.py", line 999, in run_command
      super().run_command(command)
    File "/tmp/pip-build-env-fbr81j_m/overlay/lib/python3.10/site-packages/setuptools/_distutils/dist.py", line 1002, in run_command
      cmd_obj.run()
    File "<string>", line 232, in run
    File "/tmp/pip-build-env-fbr81j_m/overlay/lib/python3.10/site-packages/setuptools/command/bdist_wheel.py", line 379, in run
      self.run_command("build")
    File "/tmp/pip-build-env-fbr81j_m/overlay/lib/python3.10/site-packages/setuptools/_distutils/cmd.py", line 339, in run_command
      self.distribution.run_command(command)
    File "/tmp/pip-build-env-fbr81j_m/overlay/lib/python3.10/site-packages/setuptools/dist.py", line 999, in run_command
      super().run_command(command)
    File "/tmp/pip-build-env-fbr81j_m/overlay/lib/python3.10/site-packages/setuptools/_distutils/dist.py", line 1002, in run_command
      cmd_obj.run()
    File "/tmp/pip-build-env-fbr81j_m/overlay/lib/python3.10/site-packages/setuptools/_distutils/command/build.py", line 136, in run
      self.run_command(cmd_name)
    File "/tmp/pip-build-env-fbr81j_m/overlay/lib/python3.10/site-packages/setuptools/_distutils/cmd.py", line 339, in run_command
      self.distribution.run_command(command)
    File "/tmp/pip-build-env-fbr81j_m/overlay/lib/python3.10/site-packages/setuptools/dist.py", line 999, in run_command
      super().run_command(command)
    File "/tmp/pip-build-env-fbr81j_m/overlay/lib/python3.10/site-packages/setuptools/_distutils/dist.py", line 1002, in run_command
      cmd_obj.run()
    File "<string>", line 138, in run
    File "/usr/local/lib/python3.10/subprocess.py", line 526, in run
      raise CalledProcessError(retcode, process.args,
  subprocess.CalledProcessError: Command '['cmake', '/tmp/pip-install-ml11b504/pybammsolvers_a88d40bc6d0547688960ec5d0c66dd00', '-DCMAKE_BUILD_TYPE=RELEASE', '-DPYTHON_EXECUTABLE=/usr/local/bin/python3.10', '-DUSE_PYTHON_CASADI=TRUE', '-DPYBAMM_IDAKLU_EXPR_CASADI=ON', '-DPYBAMM_IDAKLU_EXPR_IREE=OFF', '-DSuiteSparse_ROOT=/tmp/pip-install-ml11b504/pybammsolvers_a88d40bc6d0547688960ec5d0c66dd00/.idaklu', '-DSUNDIALS_ROOT=/tmp/pip-install-ml11b504/pybammsolvers_a88d40bc6d0547688960ec5d0c66dd00/.idaklu']' returned non-zero exit status 1.
  [end of output]

note: This error originates from a subprocess, and is likely not a problem with pip.
ERROR: Failed building wheel for pybammsolvers
Failed to build pybammsolvers
ERROR: Failed to build installable wheels for some pyproject.toml based projects (pybammsolvers)

Steps to Reproduce

pip install pybammsolvers

Relevant log output

[kratman]

@chuckliu1979 We are working on linux arm64 support at the moment. This will be fixed in the near future, we have two different work packages trying to resolve this issue

[kratman]

This will be covered by this ticket: pybamm-team/pybammsolvers#19

I am working on the issues now

[agriyakhetarpal]

I think it makes sense to keep it open for visibility, for now, as this affects both PyBaMM and pybammsolvers. Your PR pybamm-team/pybammsolvers#28 (or a newer one after that) could reference this issue to close it as both repositories are under the same organisation.