lay2dev / secp256r1-test

A Secp256r1 Lockscript for CKB (to be merge into pw-lock)
0 stars 0 forks source link

Problems during compilation #1

Open jordanmack opened 3 years ago

jordanmack commented 3 years ago

I'm having problems compiling and testing. Any idea how to rectify this?

# make all-via-docker
riscv64-unknown-elf-gcc -O3 -Ideps/molecule -I deps/libecc/src -I deps/libecc/src/external_deps -I deps/secp256k1/src -I deps/secp256k1 -I deps/ckb-c-std-lib -I c -I build -Wall -Werror -Wno-nonnull-compare -Wno-unused-function -g -DWORDSIZE=64  -DWITH_STDLIB -D__unix__ -Wl,-static -fdata-sections -ffunction-sections -Wl,--gc-sections -DWITH_STDLIB -D__unix__ -DWORDSIZE=64  c/always_success.c deps/libecc/build/libsign.a deps/libecc/src/external_deps/rand.c  deps/libecc/src/external_deps/print.c -o specs/cells/always_success
riscv64-unknown-elf-objcopy --only-keep-debug specs/cells/always_success build/always_success.debug
riscv64-unknown-elf-objcopy:build/always_success.debug: No such file or directory
Makefile:25: recipe for target 'specs/cells/always_success' failed
make: *** [specs/cells/always_success] Error 1
make: *** [Makefile:22: all-via-docker] Error 2
# cargo test --all
error: failed to run custom build command for `ckb-system-scripts v0.5.1 (/home/username/secp256r1-test)`

Caused by:
  process didn't exit successfully: `/home/username/secp256r1-test/target/debug/build/ckb-system-scripts-1d4915720d2b21a4/build-script-build` (exit code: 101)
  --- stdout
  cargo:rerun-if-changed=specs/cells/always_success

  --- stderr
  always_success: expect bf569d8cdf733002158fc9814814761a534ba2fdeecac0eec55d626e686f625c, actual 83fb35ea13124f4dabb0c8fb695c8d25def5e98d960a75b4054c8307796b5053
  thread 'main' panicked at 'not all hashes are right', build.rs:72:9
  note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
warning: build failed, waiting for other jobs to finish...
error: build failed
johnz1019 commented 3 years ago

This repository is for test purpose, and I have not maintain it for a long time. If you would like to test secp256r1 on CKB chain, you can move to pw-lock