Skip to content
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

Build Failure: pyo3-ffi v0.20.3 - SOABI not found in sysconfigdata file #4526

Open
Sangeetha-E opened this issue Sep 4, 2024 · 3 comments
Open

Comments

@Sangeetha-E
Copy link

I'm encountering an issue when trying to compile the pyo3-ffi v0.20.3. The build fails with the following error:

Error logs:

Compiling pyo3-ffi v0.20.3
Compiling pyo3 v0.20.3
error: failed to run custom build command for `pyo3-ffi v0.20.3`

Caused by:
  process didn't exit successfully: (exit status: 1)
  --- stdout
  cargo:rerun-if-env-changed=PYO3_CROSS
  cargo:rerun-if-env-changed=PYO3_CROSS_LIB_DIR
  cargo:rerun-if-env-changed=PYO3_CROSS_PYTHON_VERSION
  cargo:rerun-if-env-changed=PYO3_CROSS_PYTHON_IMPLEMENTATION
  cargo:rerun-if-env-changed=PYO3_NO_PYTHON
  cargo:rerun-if-env-changed=_PYTHON_SYSCONFIGDATA_NAME
  cargo:rerun-if-env-changed=PYO3_ENVIRONMENT_SIGNATURE
  cargo:rerun-if-env-changed=PYO3_PYTHON
  cargo:rerun-if-env-changed=VIRTUAL_ENV
  cargo:rerun-if-env-changed=CONDA_PREFIX

  --- stderr
  error: SOABI not found in sysconfigdata file
warning: build failed, waiting for other jobs to finish...

I am looking for guidance on how to resolve this build issue. Any help or suggestions would be greatly appreciated.

@messense
Copy link
Member

messense commented Sep 4, 2024

What's the output of python3 -m sysconfig? Can you find SOABI in it?

@Sangeetha-E
Copy link
Author

Sangeetha-E commented Sep 4, 2024

Yes. I found SOABI.

$ python3 -m sysconfig | grep SOABI
	ALT_SOABI = "0"
	SOABI = "cpython-311-x86_64-linux-gnu"

Note: I am cross compiling pyo3-ffi.

@davidhewitt
Copy link
Member

What target are you cross compiling to? Are you able to try latest PyO3 (0.22.2)? We might have improved things (or at least improved error messages), and if it's still a problem maybe we can improve the error message further.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants