[GH-ISSUE #205] Can't build at linux. ring v0.16.20 custom build command error #103

Closed
opened 2026-04-08 16:50:22 +03:00 by zhus · 1 comment
Owner

Originally created by @servomekanism on GitHub (Apr 14, 2023).
Original GitHub issue: https://github.com/sigoden/dufs/issues/205

Hello and thanks for your very useful awesome project.

I download with git clone https://github.com/sigoden/dufs.git. Then I did cargo build and got an error:

   Compiling ring v0.16.20 (/home/user/.cargo/registry/src/github.com-1ecc6299db9ec823/ring-0.16.20)
   Compiling libc v0.2.141
   Compiling once_cell v1.17.1
   Compiling untrusted v0.7.1
   Compiling spin v0.5.2
error: failed to run custom build command for `ring v0.16.20 (/home/user/.cargo/registry/src/github.com-1ecc6299db9ec823/ring-0.16.20)`

Caused by:
  process didn't exit successfully: `/home/user/.cargo/registry/src/github.com-1ecc6299db9ec823/ring-0.16.20/target/debug/build/ring-e700aa5ed5879cdc/build-script-build` (exit status: 101)
  --- stdout
  OPT_LEVEL = Some("0")
  TARGET = Some("x86_64-unknown-linux-gnu")
  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=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 = Some("-wall -pedantic")
  cargo:rerun-if-env-changed=CRATE_CC_NO_DEFAULTS
  CRATE_CC_NO_DEFAULTS = None
  DEBUG = Some("true")
  CARGO_CFG_TARGET_FEATURE = Some("fxsr,sse,sse2")

  --- stderr
  running "cc" "-O0" "-ffunction-sections" "-fdata-sections" "-fPIC" "-gdwarf-4" "-fno-omit-frame-pointer" "-m64" "-wall" "-pedantic" "-I" "include" "-pedantic" "-pedantic-errors" "-Wall" "-Wextra" "-Wcast-align" "-Wcast-qual" "-Wconversion" "-Wenum-compare" "-Wfloat-equal" "-Wformat=2" "-Winline" "-Winvalid-pch" "-Wmissing-field-initializers" "-Wmissing-include-dirs" "-Wredundant-decls" "-Wshadow" "-Wsign-compare" "-Wsign-conversion" "-Wundef" "-Wuninitialized" "-Wwrite-strings" "-fno-strict-aliasing" "-fvisibility=hidden" "-fstack-protector" "-g3" "-DNDEBUG" "-c" "-o/home/user/.cargo/registry/src/github.com-1ecc6299db9ec823/ring-0.16.20/target/debug/build/ring-fd4b97d407f3e2a5/out/aesni-x86_64-elf.o" "/home/user/.cargo/registry/src/github.com-1ecc6299db9ec823/ring-0.16.20/pregenerated/aesni-x86_64-elf.S"
  cc: error: unrecognized command-line option ‘-wall’; did you mean ‘-Wall’?
  thread 'main' panicked at 'execution failed', build.rs:656:9
  note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

For some reason, this line had the -Wall argument as -wall:

CFLAGS = Some("-wall -pedantic")

I resolved it with running: CFLAGS="-Wall -pedantic" cargo build

TBH I think that this issue should be reported at the ring crate, although I am not sure.

Originally created by @servomekanism on GitHub (Apr 14, 2023). Original GitHub issue: https://github.com/sigoden/dufs/issues/205 Hello and thanks for your very useful awesome project. I download with `git clone https://github.com/sigoden/dufs.git`. Then I did `cargo build` and got an error: ``` Compiling ring v0.16.20 (/home/user/.cargo/registry/src/github.com-1ecc6299db9ec823/ring-0.16.20) Compiling libc v0.2.141 Compiling once_cell v1.17.1 Compiling untrusted v0.7.1 Compiling spin v0.5.2 error: failed to run custom build command for `ring v0.16.20 (/home/user/.cargo/registry/src/github.com-1ecc6299db9ec823/ring-0.16.20)` Caused by: process didn't exit successfully: `/home/user/.cargo/registry/src/github.com-1ecc6299db9ec823/ring-0.16.20/target/debug/build/ring-e700aa5ed5879cdc/build-script-build` (exit status: 101) --- stdout OPT_LEVEL = Some("0") TARGET = Some("x86_64-unknown-linux-gnu") 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=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 = Some("-wall -pedantic") cargo:rerun-if-env-changed=CRATE_CC_NO_DEFAULTS CRATE_CC_NO_DEFAULTS = None DEBUG = Some("true") CARGO_CFG_TARGET_FEATURE = Some("fxsr,sse,sse2") --- stderr running "cc" "-O0" "-ffunction-sections" "-fdata-sections" "-fPIC" "-gdwarf-4" "-fno-omit-frame-pointer" "-m64" "-wall" "-pedantic" "-I" "include" "-pedantic" "-pedantic-errors" "-Wall" "-Wextra" "-Wcast-align" "-Wcast-qual" "-Wconversion" "-Wenum-compare" "-Wfloat-equal" "-Wformat=2" "-Winline" "-Winvalid-pch" "-Wmissing-field-initializers" "-Wmissing-include-dirs" "-Wredundant-decls" "-Wshadow" "-Wsign-compare" "-Wsign-conversion" "-Wundef" "-Wuninitialized" "-Wwrite-strings" "-fno-strict-aliasing" "-fvisibility=hidden" "-fstack-protector" "-g3" "-DNDEBUG" "-c" "-o/home/user/.cargo/registry/src/github.com-1ecc6299db9ec823/ring-0.16.20/target/debug/build/ring-fd4b97d407f3e2a5/out/aesni-x86_64-elf.o" "/home/user/.cargo/registry/src/github.com-1ecc6299db9ec823/ring-0.16.20/pregenerated/aesni-x86_64-elf.S" cc: error: unrecognized command-line option ‘-wall’; did you mean ‘-Wall’? thread 'main' panicked at 'execution failed', build.rs:656:9 note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace ``` For some reason, this line had the `-Wall` argument as `-wall`: ``` CFLAGS = Some("-wall -pedantic") ``` I resolved it with running: `CFLAGS="-Wall -pedantic" cargo build` TBH I think that this issue should be reported at the `ring` crate, although I am not sure.
zhus closed this issue 2026-04-08 16:50:22 +03:00
Author
Owner

@sigoden commented on GitHub (Jun 1, 2023):

I didn't run into this problem and couldn't fix it.

Maybe you need to visit https://github.com/briansmith/ring repo to find a solution

<!-- gh-comment-id:1572064457 --> @sigoden commented on GitHub (Jun 1, 2023): I didn't run into this problem and couldn't fix it. Maybe you need to visit https://github.com/briansmith/ring repo to find a solution
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: sigoden/dufs#103