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

bug: Cargo is broken after #15182 #15200

Closed
andylokandy opened this issue Apr 9, 2024 · 3 comments · Fixed by #15144 or #15209
Closed

bug: Cargo is broken after #15182 #15200

andylokandy opened this issue Apr 9, 2024 · 3 comments · Fixed by #15144 or #15209
Labels
C-bug Category: something isn't working

Comments

@andylokandy
Copy link
Contributor

cargo test --package databend-common-ast
    Updating crates.io index
   Compiling hyper-timeout v0.4.1
   Compiling axum v0.6.20
   Compiling geos-sys v2.0.6
   Compiling hyper-rustls v0.24.2
   Compiling geo-types v0.7.13
   Compiling tantivy-sstable v0.2.0
   Compiling arrow-ipc v50.0.0
error: failed to run custom build command for `geos-sys v2.0.6`

Caused by:
  process didn't exit successfully: `/home/andy/Code/databend3/target/debug/build/geos-sys-f24f80e2b2032052/build-script-build` (exit status: 101)
  --- stdout
  cargo:rerun-if-changed=build.rs
  cargo:rerun-if-env-changed=GEOS_LIB_DIR
  cargo:rerun-if-env-changed=GEOS_VERSION
  cargo:rerun-if-env-changed=GEOS_NO_PKG_CONFIG
  cargo:rerun-if-env-changed=PKG_CONFIG_x86_64-unknown-linux-gnu
  cargo:rerun-if-env-changed=PKG_CONFIG_x86_64_unknown_linux_gnu
  cargo:rerun-if-env-changed=HOST_PKG_CONFIG
  cargo:rerun-if-env-changed=PKG_CONFIG
  cargo:rerun-if-env-changed=GEOS_STATIC
  cargo:rerun-if-env-changed=GEOS_DYNAMIC
  cargo:rerun-if-env-changed=PKG_CONFIG_ALL_STATIC
  cargo:rerun-if-env-changed=PKG_CONFIG_ALL_DYNAMIC
  cargo:rerun-if-env-changed=PKG_CONFIG_PATH_x86_64-unknown-linux-gnu
  cargo:rerun-if-env-changed=PKG_CONFIG_PATH_x86_64_unknown_linux_gnu
  cargo:rerun-if-env-changed=HOST_PKG_CONFIG_PATH
  cargo:rerun-if-env-changed=PKG_CONFIG_PATH
  cargo:rerun-if-env-changed=PKG_CONFIG_LIBDIR_x86_64-unknown-linux-gnu
  cargo:rerun-if-env-changed=PKG_CONFIG_LIBDIR_x86_64_unknown_linux_gnu
  cargo:rerun-if-env-changed=HOST_PKG_CONFIG_LIBDIR
  cargo:rerun-if-env-changed=PKG_CONFIG_LIBDIR
  cargo:rerun-if-env-changed=PKG_CONFIG_SYSROOT_DIR_x86_64-unknown-linux-gnu
  cargo:rerun-if-env-changed=PKG_CONFIG_SYSROOT_DIR_x86_64_unknown_linux_gnu
  cargo:rerun-if-env-changed=HOST_PKG_CONFIG_SYSROOT_DIR
  cargo:rerun-if-env-changed=PKG_CONFIG_SYSROOT_DIR

  --- stderr
  thread 'main' panicked at /home/andy/.cargo/registry/src/index.crates.io-6f17d22bba15001f/geos-sys-2.0.6/build.rs:137:13:
  Could not detect GEOS using pkg-config or geos-config
  note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
warning: build failed, waiting for other jobs to finish...

For anybody seeking for a temporary solution

Adding geos = { version = "8.3", features = ["static"] } to src/query/expression/Cargo.toml temporarily solved the problem.

Originally posted by @andylokandy in #15182 (comment)

@andylokandy andylokandy added the C-bug Category: something isn't working label Apr 9, 2024
@BohuTANG
Copy link
Member

If we change to geos = { version = "8.3", features = ["static"] }, what will be the effects?

@andylokandy
Copy link
Contributor Author

geos is an indirect dependency included by the with_geos feature flag on geozero, where geos doesn't be given a static flag. The workaround manually adds the static flag to geos.

drmingdrmer added a commit to drmingdrmer/databend that referenced this issue Apr 11, 2024
drmingdrmer added a commit to drmingdrmer/databend that referenced this issue Apr 11, 2024
drmingdrmer added a commit to drmingdrmer/databend that referenced this issue Apr 11, 2024
BohuTANG pushed a commit that referenced this issue Apr 11, 2024
@andylokandy andylokandy reopened this Apr 11, 2024
@andylokandy
Copy link
Contributor Author

andylokandy commented Apr 11, 2024

cargo test --package databend-common-ast is still breaking.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
C-bug Category: something isn't working
Projects
None yet
2 participants