WARNING: this package now builds WITHOUT cuda support. To avoid errors like codemonkey's, I've decided to split this package up into ethminer, and ethminer-cuda. If someone wants to build with cuda support, he/she can install ethminer-cuda and makepkg will take care of the dependencies.
Search Criteria
Package Details: ethminer 0.13.0-2
| Git Clone URL: | https://aur.archlinux.org/ethminer.git (read-only) |
|---|---|
| Package Base: | ethminer |
| Description: | Ethereum miner with OpenCL and stratum support (built without CUDA). |
| Upstream URL: | https://github.com/ethereum-mining/ethminer |
| Licenses: | |
| Conflicts: | |
| Submitter: | 5chdn |
| Maintainer: | aimileus |
| Last Packager: | aimileus |
| Votes: | 10 |
| Popularity: | 0.274794 |
| First Submitted: | 2017-08-31 08:15 |
| Last Updated: | 2018-02-27 10:51 |
Dependencies (3)
- mesa (mesa-nowayland, mesa-hybris, mesa_mild_compatibility-git, mesa-noglvnd, mesa-grate-git, mesa-git)
- cmake (cmake-git) (make)
- python (make)
Required by (0)
Sources (1)
Latest Comments
aimileus commented on 2018-03-23 16:25
sarvex commented on 2018-03-23 08:45
The package does not depend on host libraries, it downloads boost and others again, even when the packages are already present on the system
aimileus commented on 2018-02-27 10:51
WARNING: this package now builds WITHOUT cuda support. To avoid errors like codemonkey's, I've decided to split this package up into ethminer, and ethminer-cuda. If someone wants to build with cuda support, he/she can install ethminer-cuda and makepkg will take care of the dependencies.
codemonkey commented on 2018-02-25 14:02
EDIT: I installed cuda AFTER running makepkg, my issue below is incorrect.
For some reason this did not build with CUDA support for me, despite having a CUDA compatible card and cuda installed.
Manually compiling source with -DETHASHCUDA=ON did work, and nvcc does exist, so -f '/opt/cuda/bin/nvcc' should evaluate to true, but does not?
Svenstaro commented on 2017-12-02 22:34
Why does this install the binary release without compiling the actual source and yet it requires all the dependencies for building?
@sarvex, it does that because that is the configuration supported by upstream, to prevent new bugs introduced by 'incorrect' versions of the dependencies.