Closed blackmennewstyle closed 4 months ago
I can confirm, as soon as i created the missing symlink. Everything works:
ln -s /usr/local/lib/x86_64-linux-gnu/libwarthogsecp256k1.so /usr/lib/x86_64-linux-gnu/libwarthogsecp256k1.so
ln -s /usr/local/lib/x86_64-linux-gnu/libusockets.so /usr/lib/x86_64-linux-gnu/libusockets.so
ln -s /usr/local/lib/x86_64-linux-gnu/libuvw.so /usr/lib/x86_64-linux-gnu/libuvw.so
wart-node --help
Usage: wart-node [OPTION]...
The reference implementation node of the Warthog Network.
By Pumbaa, Timon & Rafiki
-h, --help Print help and exit
--detailed-help Print help, including all details and hidden
options, and exit
-V, --version Print version and exit
Node options:
-b, --bind=IP:PORT Socket to listen on, defaults to "0.0.0.0:9186"
for main net and "0.0.0.0:9286" for test net
-C, --connect=IP:PORT,... Specify peer list
--isolated Do not allow peers (for testing purposes, do not
use in production)
--temporary Use temporary database (for testing purposes, do
not use in production)
--testnet Enable testnet
Data file options:
--chain-db=STRING specify chain data file
--peers-db=STRING specify data file
Logging options:
-d, --debug Enable debug messages
JSON RPC endpoint options:
-r, --rpc=IP:PORT JSON RPC endpoint socket, defaults to
"127.0.0.1:3000" for main net and
"127.0.0.1:3100" for test net
--publicrpc=IP:PORT Public JSON RPC endpoint socket, disabled by
default
--stratum=IP:PORT Solo mining stratum
--enable-public Shorthand for --publicrpc=0.0.0.0:3001
Configuration file options:
-c, --config=FILENAME Configuration file, default is "config.toml", in
testnet "testnet3_chain.db3"
-t, --test test the configuration file (check for correct
syntax)
--dump-config dump the current configuration to stdout
You must add /usr/local/lib/x86_64-linux-gnu to your library path. Using symbolic links is possible but not a good way to solve the issue. Which OS?
You can read some more info here https://askubuntu.com/questions/165027/why-cant-my-program-find-the-libraries-in-usr-local-lib I am not sure why meson copies into a directory that is not part of the default library search paths. According to this issue it is a distro problem.
meson
seems to have a lot of issues like that one, it's the same with gcc
detection.
Hello beautiful devs,
I'm trying to build the latest release from the sources. It went well except i think the ninja install forget to create some symlink.
With root privileges:
Sadly when i run:
Judging by the trace of
ninja install
, i think you forgot to create some necessarysymlink
.