xmrig icon indicating copy to clipboard operation
xmrig copied to clipboard

xmrig: error while loading shared libraries: libhwloc.so.15

Open toxicroadkill opened this issue 3 years ago • 8 comments

When I execute xmrig, I get "xmrig: error while loading shared libraries: libhwloc.so.15". Ive installed the following with no luck getting rid of the error:

apt install hwloc apt install libhwloc-dev

running debian 10 (buster) on a intel i5

toxicroadkill avatar May 24 '21 03:05 toxicroadkill

debian 10 has too old of an hwloc version, maybe try the compact version (i dont know diffrance but i know its a static binary) or compile on your own

a8underscore avatar May 25 '21 04:05 a8underscore

debian 10 is not that old, is there a way you can make it compat with 10?

since debian 11 has not even been released yet, 10 is the latest version there is

On May 24, 2021, at 11:17 PM, a8underscore @.***> wrote:

debian 10 has too old of an hwloc version, maybe try the compact version (i dont know diffrance but i know its a static binary) or compile on your own

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/MoneroOcean/xmrig/issues/57#issuecomment-847517134, or unsubscribe https://github.com/notifications/unsubscribe-auth/ASD5O32E46NCWSDVGFANL4TTPMQHLANCNFSM45MMMNCQ.

toxicroadkill avatar May 25 '21 04:05 toxicroadkill

Buster has 1.11.12 and the bundled/targeted version is 2.4.1

Install the things needed to build the deps: sudo apt install build-essential autoconf automake libtool and then use the bundled lib builder: cd ./scripts && bash ./build_deps.sh and then add -DXMRIG_DEPS=../scripts/deps to your CMake command

Spudz76 avatar May 25 '21 12:05 Spudz76

how about just making a prebuilt binary for those who really dont want to compile it?

it would be very useful for people

On May 25, 2021, at 7:50 AM, Tony Butler @.***> wrote:

Buster has 1.11.12 and the bundled/targeted version is 2.4.1

Install the things needed to build the deps: sudo apt install build-essential autoconf automake libtool and then use the bundled lib builder: cd ./scripts && bash ./build_deps.sh and then add -DXMRIG_DEPS=../scripts/deps to your CMake command

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/MoneroOcean/xmrig/issues/57#issuecomment-847841537, or unsubscribe https://github.com/notifications/unsubscribe-auth/ASD5O36NMQJ7SLDWVNFQNATTPOMLBANCNFSM45MMMNCQ.

toxicroadkill avatar May 25 '21 15:05 toxicroadkill

Because there would be a build for every Debian version, Ubuntu version, CentOS version, FreeBSD version...

They change libs every release and therefore must be targeted for what set of libs each one has. Static release can not work with OpenCL. Other problems.

It's pretty easy to compile, way easier than Windows. Especially with the bundled deps it works almost anywhere.

Spudz76 avatar May 26 '21 03:05 Spudz76

ill probably do that, but I just detect compiling c programs

how much is a typical gain by using the monero ocean version vs the standard xmrig?

im running cpu only mining

On May 25, 2021, at 10:42 PM, Tony Butler @.***> wrote:

Because there would be a build for every Debian version, Ubuntu version, CentOS version, FreeBSD version...

They change libs every release and therefore must be targeted for what set of libs each one has. Static release can not work with OpenCL. Other problems.

It's pretty easy to compile, way easier than Windows. Especially with the bundled deps it works almost anywhere.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/MoneroOcean/xmrig/issues/57#issuecomment-848430697, or unsubscribe https://github.com/notifications/unsubscribe-auth/ASD5O32RAAGJJOEF7KWH2F3TPRUZDANCNFSM45MMMNCQ.

toxicroadkill avatar May 26 '21 03:05 toxicroadkill

Well it's got no choice but to be the most profitable for whatever your CPU can do across all supported algos.

If you compare to earning XMR the normal way by mining rx/0 algo (actual Monero Blockchain) then your CPU probably isn't as good at it as it would be processing an easier algo (that fits cache better, doesn't need ultra fast memory...) Unless it's a Ryzen but even then depending on values it may earn more on something like cn-heavy/xhv

So it automatically leverages whatever talents your equipment has for the highest value in XMR.

Spudz76 avatar May 26 '21 04:05 Spudz76

thats cool, im running old dell optiplexes with i5 and i7's

got a amazing deal on them..dude has a pallet of them, and will sell them to me dirt cheap :)

On May 25, 2021, at 11:08 PM, Tony Butler @.***> wrote:

Well it's got no choice but to be the most profitable for whatever your CPU can do across all supported algos.

If you compare to earning XMR the normal way by mining rx/0 algo (actual Monero Blockchain) then your CPU probably isn't as good at it as it would be processing an easier algo (that fits cache better, doesn't need ultra fast memory...) Unless it's a Ryzen but even then depending on values it may earn more on something like cn-heavy/xhv

So it automatically leverages whatever talents your equipment has for the highest value in XMR.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/MoneroOcean/xmrig/issues/57#issuecomment-848437845, or unsubscribe https://github.com/notifications/unsubscribe-auth/ASD5O34TKVK2VPX4R3PZL6TTPRX3ZANCNFSM45MMMNCQ.

toxicroadkill avatar May 26 '21 04:05 toxicroadkill