-
Notifications
You must be signed in to change notification settings - Fork 1.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
xmr-stak-rx and xmr-stak both install libxmrstak_opencl_backend.so and libxmrstak_cuda_backend.so #2571
Comments
Do not put both miner into the same directory. Please use a new directory
for xmr-stak-rx and copy your pools.txt and config.txt into the xmr-stak-rx
folder. Please have a look to the release nodes
https://github.com/fireice-uk/xmr-stak/releases i to the section pre-fork
notes.
|
It's https://github.com/fireice-uk/xmr-stak/blob/1.0.1-rx/CMakeLists.txt#L564 which is installing the libraries - it puts them (correctly) in |
Ohh I never thought about that someone is installing the miner to the root
filesystem.
You can simple set the install path `cmake
-DCMAKE_INSTALL_PREFIX=$HOME/stak-rx`
|
That isn't a workable solution for Linux distributions :) Distros package to install globally, not in a user's home directory. |
I will fix it. As you wrote initial I forgot to rename the libraries.
|
psychocrypt
added a commit
to psychocrypt/xmr-stak
that referenced
this issue
Nov 28, 2019
Rename xmr-stak-rx backend libraries to avoid conflicts with xmr-stak libraries. fix fireice-uk#2571
#2573 will fix the issue. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
xmr-stak 2.10.7 and xmr-stak-rx 1.0.1-rx both install /usr/lib64/libxmrstak_opencl_backend.so which means that both xmr-stak and xmr-stak-rx cannot be installed at the same time.
Perhaps you could change rx's library name to include rx, from libxmrstak_opencl_backend.so to libxmrstakrx_opencl_backend.so ?
This issue also applies to the cuda library (libxmrstak_cuda_backend.so)
The text was updated successfully, but these errors were encountered: