Package Details: xmr-stak-git r1457.67cf951-1

Git Clone URL: https://aur.archlinux.org/xmr-stak-git.git (read-only, click to copy)
Package Base: xmr-stak-git
Description: Unified All-in-one Monero miner
Upstream URL: https://github.com/fireice-uk/xmr-stak
Licenses: GPL3
Conflicts: xmr-stak
Provides: xmr-stak
Submitter: huiyiqun
Maintainer: a36233
Last Packager: a36233
Votes: 16
Popularity: 0.000000
First Submitted: 2017-11-22 03:03 (UTC)
Last Updated: 2020-04-20 10:13 (UTC)

Latest Comments

« First ‹ Previous 1 2 3 Next › Last »

wangbx_arch commented on 2017-12-16 06:08 (UTC)

Got the following error: /tmp/yaourt-tmp-[user]/aur-xmr-stak-git/src/xmr-stak/xmrstak/backend/nvidia/nvcc_code/cuda_extra.cu:9:32: fatal error: device_functions.hpp: No such file or directory

Renaming should be able to fix it, similar to: https://github.com/xmrig/xmrig-nvidia/issues/64

Thanks

GRBurst commented on 2017-12-11 22:43 (UTC)

@dominicm As you mentioned, the line starts with an "#", meaning that it is commented out ;-) To enable the patch, you have to remove the leading # and correct the path the path to ../no-donate.patch

huiyiqun commented on 2017-12-08 04:53 (UTC)

If this patch is enabled, then you can see

Configurable dev donation level is set to 0.0%

when you running it.

If you'd like to enable it automatically, you could try customizepkg.

huiyiqun commented on 2017-12-08 04:51 (UTC)

@noraj cuda require gcc6 yet.

If you'd like to use gcc7 and do not need cuda, you should try https://aur.archlinux.org/packages/xmr-stak-cpu-git/ instead.

noraj commented on 2017-12-08 00:42 (UTC)

Why forcing to use gcc6 and not gcc7 ?

dominicm commented on 2017-12-07 16:01 (UTC)

@GRBurst I though it was included by default, I even saw a boost in hashrate vs git install not to mention that the thank you note dissapeared from web UI. How can I verify if it's compiled with the patch? Also the line is #patch -p1 -i ../../no-donate.patch so unless I am missing something you also need to uncomment it.

dominicm commented on 2017-12-07 15:57 (UTC)

@arcmags Why not include a systemd service with this package? This way it could run as its own dedicated system user and set the proper config location as default. If there is need to run as user, systemd user services can be included too or just run an the executable from /bin like now.

GRBurst commented on 2017-12-07 09:53 (UTC)

Quick info: In order to use the no-donate.patch, you have to change the path from "../../no-donate.patch" to "../no-donate.patch" in the pkgconfig.

mags commented on 2017-12-06 22:23 (UTC)

@dominicm I agree it's not an ideal design, but that's how upstream does it. You could fork a repo, make changes, and build your own package; or you could write a simple wrapper script to switch to some chosen config directory with each launch...

dominicm commented on 2017-12-06 16:48 (UTC) (edited on 2017-12-06 17:06 (UTC) by dominicm)

That seems like a really bad design decision to me. Current directory will obviously change causing issues so why not use the standard config file directories like all the other packages do? I really do not understand why you wouldn't put the config file in the config directory like /etc or seeing as it isn't a system service, ~/.config seems like a good place.