You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
That is because Cargo doesn’t propagate the crate’s link arguments to higher-level crates. In Neptune’s build.rs, we set two arguments: rpath and link-search. The rpath is intended for the final binary to link to the library, and link-search allows Cargo to locate the library.
The problem is that link-search can be passed to crates that use Neptune, but rpath cannot, as noted in this Cargo issue. So, you can use cargo run to execute the program, but you can’t run Libra directly.
One way to address this is to add these arguments to any binaries's build.rs that use Neptune, either directly or indirectly, as demonstrated in this commit. Additionally, you would need to copy libpipy.so to the directory where the executable is located.
I used the following command to compile Libra into a binary:
The compilation process was OK, but when I ran
libra
command, I got an error:However, if I run
libra
directly viacargo run
, there are no problem at all.And this issue occurred after
libra
introducedgemini
for p2p download.The text was updated successfully, but these errors were encountered: