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
Using mold or lld as a linker is desirable over the default ld.bfd or whatever gcc uses nowadays as at the very least these tools link binaries up faster. However after setting either of the following environment variables:
and then running just nextest stable will not work with an error along the lines of:
...
Compiling near-fork-network v0.0.0 (.../nearcore/tools/fork-network)
Finished dev-release [optimized] target(s) in 2m 50s
warning: the following packages contain code that will be rejected by a future version of Rust: fs_extra v1.2.0, wasmer-singlepass-backend-near v0.18.1, wasmparser v0.78.2
note: to see what the problems were, use the option `--future-incompat-report`, or run `cargo report future-incompatibilities --id 1`
error: creating test list failed
Caused by:
for `genesis-csv-to-json::bin/genesis-csv-to-json`, command `.../nearcore/target/dev-release/deps/genesis_csv_to_json-0f02e52b48fd6303 --list --format terse` exited with code 127
--- stdout:
--- stderr:
.../nearcore/target/dev-release/deps/genesis_csv_to_json-0f02e52b48fd6303: error while loading shared libraries: libstdc++.so.6: cannot open shared object file: No such file or directory
Usually I would suspect a system configuration problem, but:
Things work fine with the default linker gcc uses;
I know that gcc's linker is pretty lax about its interface and e.g. getting order of -largs wrong will fly past it but not past other linkers.
The text was updated successfully, but these errors were encountered:
nagisa
added
the
A-build
Area: Anything related to the build and configuration process for nearcore.
label
Jan 29, 2024
This may be a NixOS specific problem -- it enables rpath by default for the usual linker but if you ask for a plain mold or lld packages, you'll get the unwrapped stuff, it seems.
Using
mold
orlld
as a linker is desirable over the defaultld.bfd
or whatever gcc uses nowadays as at the very least these tools link binaries up faster. However after setting either of the following environment variables:and then running
just nextest stable
will not work with an error along the lines of:Usually I would suspect a system configuration problem, but:
-largs
wrong will fly past it but not past other linkers.The text was updated successfully, but these errors were encountered: