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

i can't build #496

Closed
iceyee opened this issue Aug 14, 2024 · 2 comments
Closed

i can't build #496

iceyee opened this issue Aug 14, 2024 · 2 comments
Assignees
Labels
question Further information is requested

Comments

@iceyee
Copy link

iceyee commented Aug 14, 2024

Problem:

a few months ago, it works well. but today i try "cargo update" and "cargo build", it wrong.

error message:

error: failed to run custom build command for `aws-lc-sys v0.20.1`

Caused by:
  process didn't exit successfully: `/home/ljq/git/rust_buff/iceyee_buff_sell/target/release/build/aws-lc-sys-01021d10d0778e38/build-script-main` (exit status: 101)
  --- stdout
  cargo:rerun-if-env-changed=AWS_LC_SYS_NO_PREFIX
  cargo:rerun-if-env-changed=AWS_LC_SYS_INTERNAL_BINDGEN
  cargo:rerun-if-env-changed=AWS_LC_SYS_EXTERNAL_BINDGEN
  cargo:rerun-if-env-changed=AWS_LC_SYS_NO_ASM
  cargo:rustc-cfg=x86_64_unknown_linux_gnu
  cargo:rerun-if-env-changed=AWS_LC_SYS_CMAKE_BUILDER
  cargo:rerun-if-env-changed=AWS_LC_SYS_STATIC
  default_for Target: 'x86_64-unknown-linux-gnu'
  cargo:rerun-if-env-changed=CARGO_FEATURE_SSL
  default_for Target: 'x86_64-unknown-linux-gnu'
  cargo:rerun-if-env-changed=CARGO_FEATURE_SSL
  cargo:root=/home/ljq/git/rust_buff/iceyee_buff_sell/target/release/build/aws-lc-sys-9affc2d379bf0b66/out
  default_for Target: 'x86_64-unknown-linux-gnu'
  OPT_LEVEL = Some(3)
  TARGET = Some(x86_64-unknown-linux-gnu)
  OUT_DIR = Some(/home/ljq/git/rust_buff/iceyee_buff_sell/target/release/build/aws-lc-sys-9affc2d379bf0b66/out)
  HOST = Some(x86_64-unknown-linux-gnu)
  cargo:rerun-if-env-changed=CC_x86_64-unknown-linux-gnu
  CC_x86_64-unknown-linux-gnu = None
  cargo:rerun-if-env-changed=CC_x86_64_unknown_linux_gnu
  CC_x86_64_unknown_linux_gnu = None
  cargo:rerun-if-env-changed=HOST_CC
  HOST_CC = None
  cargo:rerun-if-env-changed=CC
  CC = None
  cargo:rerun-if-env-changed=CC_ENABLE_DEBUG_OUTPUT
  RUSTC_WRAPPER = None
  cargo:rerun-if-env-changed=CRATE_CC_NO_DEFAULTS
  CRATE_CC_NO_DEFAULTS = None
  DEBUG = Some(false)
  CARGO_CFG_TARGET_FEATURE = Some(fxsr,sse,sse2)
  cargo:rerun-if-env-changed=CFLAGS_x86_64-unknown-linux-gnu
  CFLAGS_x86_64-unknown-linux-gnu = None
  cargo:rerun-if-env-changed=CFLAGS_x86_64_unknown_linux_gnu
  CFLAGS_x86_64_unknown_linux_gnu = None
  cargo:rerun-if-env-changed=HOST_CFLAGS
  HOST_CFLAGS = None
  cargo:rerun-if-env-changed=CFLAGS
  CFLAGS = None
  
  --- stderr
  thread 'main' panicked at /home/ljq/.cargo/registry/src/index.crates.io-6f17d22bba15001f/aws-lc-sys-0.20.1/builder/cc_builder.rs:244:13:
  Your compiler (cc) is not supported due to a memcmp related bug reported in https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95189.We strongly recommend against using this compiler.EXECUTED: true ERROR:  OUTPUT:
  note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
warning: build failed, waiting for other jobs to finish...

Relevant details

AWS-LC for Rust versions or commit: (6b1bce0...)

System information:

  • CPU architecture: x86-64
  • CPU name: 12th Gen Intel(R) Core(TM) i3-12100
  • OS: Ubuntu 20.04
  • cargo: 1.82.0-nightly
  • gcc: 9.4.0
@justsmth
Copy link
Contributor

Hello!

This sounds similar to the build failure reported here: #474

The error message you listed summarizes the reason for the failure:

Your compiler (cc) is not supported due to a memcmp related bug reported in https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95189.We strongly recommend against using this compiler.

This is supposedly a bug only present in GCC 10.1, but perhaps there are other compiler versions that have it as well?

As a debug step, would you try setting AWS_LC_SYS_CMAKE_BUILDER=1 in your environment so the build uses CMake? I'm curious whether the "CMake build" would also complain about this issue.

@justsmth justsmth added the question Further information is requested label Aug 14, 2024
@justsmth justsmth self-assigned this Aug 14, 2024
@iceyee
Copy link
Author

iceyee commented Aug 14, 2024

yes, i have tried your suggestion, and its ok. its a valid solution.

i also tried another solution, upgrade gcc to the newest version 10.5, it works well too.

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

No branches or pull requests

2 participants