search

crate-py / rpds

Python bindings to the Rust rpds crate for persistent data structures
https://rpds.readthedocs.io/
MIT License
35 stars 12 forks source link

Build Failure: rpds_py-0.18.1 - Error with pyo3-ffi Custom Build Command #90

Closed Sangeetha-E closed 5 days ago

Sangeetha-E commented 2 weeks ago

While building rpds_py-0.18.1, I encountered the following issues. Error logs:

cargo build
   Compiling target-lexicon v0.12.9
   Compiling once_cell v1.18.0
   Compiling autocfg v1.1.0
   Compiling proc-macro2 v1.0.66
   Compiling unicode-ident v1.0.11
   Compiling libc v0.2.147
   Compiling parking_lot_core v0.9.8
   Compiling scopeguard v1.1.0
   Compiling smallvec v1.11.0
   Compiling portable-atomic v1.6.0
   Compiling heck v0.4.1
   Compiling cfg-if v1.0.0
   Compiling triomphe v0.1.9
   Compiling static_assertions v1.1.0
   Compiling unindent v0.2.3
   Compiling indoc v2.0.4
   Compiling archery v1.2.0
   Compiling rpds v1.1.0
   Compiling lock_api v0.4.10
   Compiling memoffset v0.9.0
   Compiling quote v1.0.31
   Compiling pyo3-build-config v0.20.3
   Compiling syn v2.0.32
   Compiling parking_lot v0.12.1
   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: `rpds_py-0.18.1/target/debug/build/pyo3-ffi-7d7cd6ed9a51423a/build-script-build` (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.

Julian commented 1 week ago

Hi there, please share more about your build environment (versions, OS, etc.). I'd also possibly recommend trying to build pyo3-ffi itself and seeing whether that succeeds, given it seems like a dependency here for us.