libsecp256k1.so.0 cannot be found after updating nix and running nix-garbage-collect #54

New issue

2021-11-11T19:30:13Z

kwannoel commented

2021-11-11 19:30:13 +00:00

(Migrated from github.com)

After updating nix version and running nix-garbage-collect, I encounter the following error when trying to build gerbil-ethereum:

> ./build.ss
*** WARNING -- Could not find object file entry point "___LNK_secp256k1_2d_ffi____1_2e_o2"
Gerbil v0.16-192-gfa9537be on Gambit 4.9.3-1447-gc0753ff1
*** ERROR IN load-module -- libsecp256k1.so.0: cannot open shared object file: No such file or directory
(load "/home/noel/.gerbil/lib/clan/crypto/secp256k1-ffi__1.o2")
Process exited with non-zero status
512

The solution is to:

gxpkg clean github.com/fare/gerbil-crypto
gxpkg build github.com/fare/gerbil-crypto

NOTE: gxpkg build alone does not work.

Then ./build.ss for gerbil-ethereum continues to work as per normal.

Note that the file is still not located at that path even after the above steps:

ls: cannot access '/home/noel/.gerbil/lib/clan/crypto/secp256k1-ffi__1.o2': No such file or directory

This seems to suggest some issues with linking to the nix-store path,
either it went missing after garbage collection / there where changes to the store hash for secp256k1 package.

Either a better error message or a fix will be great for this.

After updating nix version and running `nix-garbage-collect`, I encounter the following error when trying to build gerbil-ethereum: ```sh > ./build.ss *** WARNING -- Could not find object file entry point "___LNK_secp256k1_2d_ffi____1_2e_o2" Gerbil v0.16-192-gfa9537be on Gambit 4.9.3-1447-gc0753ff1 *** ERROR IN load-module -- libsecp256k1.so.0: cannot open shared object file: No such file or directory (load "/home/noel/.gerbil/lib/clan/crypto/secp256k1-ffi__1.o2") Process exited with non-zero status 512 ``` The solution is to: ``` gxpkg clean github.com/fare/gerbil-crypto gxpkg build github.com/fare/gerbil-crypto ``` NOTE: `gxpkg build` alone does not work. Then `./build.ss` for `gerbil-ethereum` continues to work as per normal. Note that the file is still not located at that path even after the above steps: ``` > ls -l /home/noel/.gerbil/lib/clan/crypto/secp256k1-ffi__1.o2 ls: cannot access '/home/noel/.gerbil/lib/clan/crypto/secp256k1-ffi__1.o2': No such file or directory ``` This seems to suggest some issues with linking to the nix-store path, either it went missing after garbage collection / there where changes to the store hash for secp256k1 package. Either a better error message or a fix will be great for this.

Sign in to join this conversation.