 Show Posts
|
|
Pages: [1]
|
Alright, I figured out one of my problems compiling and am working on the others. First off, this artefact... $ sudo make install
[sudo] password for user:
make: stat: GNUmakefile: Permission denied
make: stat: makefile: Permission denied
make: stat: Makefile: Permission denied
make: stat: install: Permission denied
make: *** No rule to make target `install'. Stop.
$
... is because I was in a directory on a volume where root, of all things, has no privileges.  In a normal directory, 'sudo make install' now generates the same output as 'make' alone, 'nvcc: command not found' error included. I finally explored github deeply enough, I think, to sort out where to get the source code I should be focusing on: https://github.com/KBomba/ccminer-KBomba/releases/tag/V1.0.02https://github.com/KBomba/ccminer-KBomba/archive/V1.0.02.tar.gz... which is advertised as: Brings back the look&feel of good ol' cudaminer! Uses the commit of 19/05/'14 as working base. Compiled with VS2010 for compute 2.x, 3.0, 3.5 & 5.0.
Does the master branch of this release include the Compute 2.x support, then? I still haven't been able to clone anything with a /tree/ in the url, including the above release, but at least I have the tarball now. Is there a trick to that, or is it not correct to even try? Meanwhile, I still have a dependency issue with the opencl libraries. nvidia-cuda-toolkit wants to uninstall some previously installed versions of a couple of libraries along with wine, which depends on them. Any suggestions what to do with that? I don't have any real experience resolving dependency issues... The package management system has always handled all that stuff!  Thanks, M. |
|
|
|
So, I'm connected to a p2pool node with my CPU miner churning out a scorching ~130 kH/s from 3 of 4 cores. the total hashrate for darkcoin (dash) is at the minimum 1000000times bigger than your hashrate.... so your payout over a few hours of running should be close to zero. The better thing for the moment is to run on another algo Thanks for the comment, djm! Looking at blocks recently solved by p2pool I see payouts in the generation transactions as small as .00004 Dash, which, if I have the orders of magnitude right, correspond to the low 10's of kH/s, proportionately, though that's not how it actually works... So, is it right to say that it's not a mathematical impossibility to get paid, it just becomes extremely unlikely that a share you solve that's accepted by the pool will be included in the part of the share-chain that gets counted when a block goes public? In other words, you're phrasing, "over a few hours of running," is key. With the hashrate and difficulty as high as they are, the number of shares included in the payout window will shrink to a few hours-worth? So, rather than waiting for lightning to strike, what do you suggest? Which coin, or how to select one? Or would a Dash pool with a different payout scheme work better? Any specifics? Also, I've read about a test network. Would that let me demonstrate that my setup is functioning? Thank you. M. |
|
|
|
I'm learning how to run mining software just to gain some experience with it. Right now I'm CPU mining Dash at a very low hash rate, while working on bringing my GPU online next. I've never used any of this tech before... wallets, miners, anything. I've never even done a crypto transaction, so it's all new to me. So, I'm connected to a p2pool node with my CPU miner churning out a scorching ~130 kH/s from 3 of 4 cores. I get a lot of these: [2015-04-03 17:38:39] Stratum detected new block I get a few of these per minute: [2015-04-03 17:39:36] accepted: 168/169 (99.41%), 132.47 khash/s (yay!!!) And I occasionally get one of these: [2015-04-03 17:45:28] Stratum connection timed out
[2015-04-03 17:45:28] Stratum connection interrupted It's been 4 days so far and, as expected, there've been no payouts. Looking at other miners in the pool with similar hash rates, it could easily be a couple of weeks before I score anything, if I do at all. I'm curious, though, about a few things:  How will I know if I am paid? Does the miner alert me to that fact? Will my wallet simply update as coin goes into the receiving address? Is there anything else I need to do to allow it to happen? Is there anything I can do (besides waiting and hoping or adding more hash rate!) to make sure my configuration is working? How long do I give it (at this ridiculously low hash rate) before I decide it's broken? Is there actually a minimum hash rate below which the pool will never pay anything? I'm simply piecing together the minimum of mining rigs from odds and ends I've got laying around, with no expectation of profit. If I can "earn" a few millicoins in exchange for $20-30 worth of extra electricity, it'll be a fair exchange for the education I'm getting. Those of you who jumped right in with decent hardware already know the answers to these questions, since you didn't have to wait very long to see results. If you could humor me by sharing your experience, I'd be grateful.  M. |
|
|
|
@matthew1820: I suggest you get onto Freenode IRC #ccminer, and ask around there for compilation help. If you're not an IRC regular, you can just use this link: #ccminer webchat You'll find the author of that particular branch is frequently around, as are other miner developers.  Thanks myagui. Good suggestion. I've signed in via the web interface and will lurk a while to get a feel of the place.  M. |
|
|
|
first ı cant help you at compiling second i was meant windows version you can get that version by clicking release tab and downloading the miner that ı mean.have a nice day.
Thank you, temroa. I've now found the release tab and learned a little more about github.  M. |
|
|
|
Thank you for replying, djm. $ make
<big snip>
/bin/bash: nvcc: command not found
make[2]: *** [heavy/heavy.o] Error 127
make[2]: Leaving directory `/home/user/test/ccminer-KBomba'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/home/user/test/ccminer-KBomba'
make: *** [all] Error 2
$ [This] one means (just saw nvcc not found in my small windows) means it can't find the path to nvcc, you should add to the PATH variable the location of cuda (as well as to LD_LIBRARY_PATH the path to cuda dynamic libraries 64bit version...) I'd seen that in my earlier attempts. The nvcc compiler is in package nvidia-cuda-toolkit, which for some reason wants to uninstall wine and a few other packages on my system -- which is a question I intended to post once we got this far... The apt-get simulation output: $ su
Password:
# apt-get -s install nvidia-cuda-toolkit
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following package was automatically installed and is no longer required:
liblcms2-2:i386
Use 'apt-get autoremove' to remove it.
The following extra packages will be installed:
nvidia-libopencl1-331 nvidia-opencl-dev nvidia-profiler opencl-headers
Suggested packages:
libcupti-dev nvidia-opencl-icd-331
Recommended packages:
nvidia-cuda-doc nvidia-cuda-gdb nvidia-visual-profiler libgl1-mesa-dev
libgl-dev
The following packages will be REMOVED:
ocl-icd-libopencl1 ocl-icd-libopencl1:i386 wine wine1.6 wine1.6-amd64
wine1.6-i386:i386
The following NEW packages will be installed:
nvidia-cuda-toolkit nvidia-libopencl1-331 nvidia-opencl-dev nvidia-profiler
opencl-headers
0 upgraded, 5 newly installed, 6 to remove and 39 not upgraded.
Remv wine [1:1.6.2-0ubuntu4]
Remv wine1.6-amd64 [1:1.6.2-0ubuntu4] [wine1.6:amd64 ]
Remv wine1.6 [1:1.6.2-0ubuntu4] [wine1.6-i386:i386 ]
Remv wine1.6-i386:i386 [1:1.6.2-0ubuntu4]
Remv ocl-icd-libopencl1 [2.1.3-4]
Remv ocl-icd-libopencl1:i386 [2.1.3-4]
Inst nvidia-libopencl1-331 (331.113-0ubuntu1~xedgers14.04.1 xorg-edgers fresh X crack:14.04/trusty [amd64])
Inst nvidia-profiler (5.5.22-3ubuntu1 Ubuntu:14.04/trusty [amd64])
Inst opencl-headers (1.2-2013.10.23-1 Ubuntu:14.04/trusty [all])
Inst nvidia-opencl-dev (5.5.22-3ubuntu1 Ubuntu:14.04/trusty [amd64])
Inst nvidia-cuda-toolkit (5.5.22-3ubuntu1 Ubuntu:14.04/trusty [amd64])
Conf nvidia-libopencl1-331 (331.113-0ubuntu1~xedgers14.04.1 xorg-edgers fresh X crack:14.04/trusty [amd64])
Conf nvidia-profiler (5.5.22-3ubuntu1 Ubuntu:14.04/trusty [amd64])
Conf opencl-headers (1.2-2013.10.23-1 Ubuntu:14.04/trusty [all])
Conf nvidia-opencl-dev (5.5.22-3ubuntu1 Ubuntu:14.04/trusty [amd64])
Conf nvidia-cuda-toolkit (5.5.22-3ubuntu1 Ubuntu:14.04/trusty [amd64])
#
I'd guess the opencl libraries are in conflict. I don't know the best way to deal with that, yet. Suggestions would be appreciated! $ sudo make install
[sudo] password for user:
make: stat: GNUmakefile: Permission denied
make: stat: makefile: Permission denied
make: stat: Makefile: Permission denied
make: stat: install: Permission denied
make: *** No rule to make target `install'. Stop.
$
I haven't looked into all the errors you reported, but that one is entirely yours: permission denied, means your password is wrong...  Unless make has a password of its own, something else is going on here. If I typed in my admin password wrong, there'd be an authentication error. I get the same result using su, then make install. In fact, it's exactly the output I get issuing 'make install' as superuser in an empty directory. As if that was make's response to not having target files to act upon... That may not be the normal result. I'm not sure my superuser privileges are working correctly right now. Another issue I'll look into separately. (also you don't need to compile it with root privilege... ) The somewhat more verbose sgminer documentation mentions that you can omit the 'make install' step; that it is only needed if you want to install the command system-wide. So it looks like the compile step is the 'make' command above, rather than this one, which does need to be done as admin if you choose to do it. sorry for being a little harsh but may-be you should stay on windows... (doing things with linux requires some knowledge you still don't have... cf quoting as error your wrong password, well we have lots of humor and are always ready to help, but if you don't see it yourself... well I guess it would take for us forever to walk you through the whole compilation process...) Well, after 10 years using Linux as a beginning and intermediate user, that'd be awful hard. In all that time this is the first dependency issue I've ever had to deal with, and the first time I've ever had problems following compile instructions. I not ashamed of asking for help with things that are new to me. Nor am I blind to the amusement value of my efforts!  Thanks, M. |
|
|
|
Yes! I saw references to that repository for this exact purpose. If you mean for me to use the branch at this URL: https://github.com/KBomba/ccminer-KBomba/tree/ccminer-for-compute-2.x...I had problems cloning it. Here are the results from two variations on the URL, depending on where on the github page I copied it: $ git clone https://github.com/KBomba/ccminer-KBomba/tree/ccminer-for-compute-2.x
Cloning into 'ccminer-for-compute-2.x'...
fatal: repository 'https://github.com/KBomba/ccminer-KBomba/tree/ccminer-for-compute-2.x/' not found
$ git clone https://github.com/KBomba/ccminer-KBomba/tree/ccminer-for-compute-2.x#
Cloning into 'ccminer-for-compute-2.x#'...
fatal: https://github.com/KBomba/ccminer-KBomba/tree/ccminer-for-compute-2.x#/info/refs not valid: is this a git repository? Is there some subtlety to working with different branches on github? I've never dealt with it much before now... As for the main branch at https://github.com/KBomba/ccminer-KBomba, it clones without a problem, but I can't get past the 'make' command, which seems to end in an error. The 'sudo make install' command barfs, looking like it's not finding the files it's looking for. Thus: $ git clone https://github.com/KBomba/ccminer-KBomba
Cloning into 'ccminer-KBomba'...
remote: Counting objects: 1329, done.
remote: Total 1329 (delta 0), reused 0 (delta 0), pack-reused 1329
Receiving objects: 100% (1329/1329), 2.04 MiB | 1.90 MiB/s, done.
Resolving deltas: 100% (783/783), done.
Checking connectivity... done. $ ./autogen.sh
Makefile.am:16: warning: source file 'sph/bmw.c' is in a subdirectory,
Makefile.am:16: but option 'subdir-objects' is disabled
automake: warning: possible forward-incompatibility.
automake: At least a source file is in a subdirectory, but the 'subdir-objects'
automake: automake option hasn't been enabled. For now, the corresponding output
automake: object file(s) will be placed in the top-level directory. However,
automake: this behaviour will change in future Automake versions: they will
automake: unconditionally cause object files to be placed in the same subdirectory
automake: of the corresponding sources.
automake: You are advised to start using 'subdir-objects' option throughout your
automake: project, to avoid future incompatibilities.
Makefile.am:16: warning: source file 'sph/blake.c' is in a subdirectory,
Makefile.am:16: but option 'subdir-objects' is disabled
Makefile.am:16: warning: source file 'sph/groestl.c' is in a subdirectory,
Makefile.am:16: but option 'subdir-objects' is disabled
Makefile.am:16: warning: source file 'sph/jh.c' is in a subdirectory,
Makefile.am:16: but option 'subdir-objects' is disabled
Makefile.am:16: warning: source file 'sph/keccak.c' is in a subdirectory,
Makefile.am:16: but option 'subdir-objects' is disabled
Makefile.am:16: warning: source file 'sph/skein.c' is in a subdirectory,
Makefile.am:16: but option 'subdir-objects' is disabled
Makefile.am:16: warning: source file 'sph/fugue.c' is in a subdirectory,
Makefile.am:16: but option 'subdir-objects' is disabled
Makefile.am:16: warning: source file 'sph/cubehash.c' is in a subdirectory,
Makefile.am:16: but option 'subdir-objects' is disabled
Makefile.am:16: warning: source file 'sph/echo.c' is in a subdirectory,
Makefile.am:16: but option 'subdir-objects' is disabled
Makefile.am:16: warning: source file 'sph/luffa.c' is in a subdirectory,
Makefile.am:16: but option 'subdir-objects' is disabled
Makefile.am:16: warning: source file 'sph/shavite.c' is in a subdirectory,
Makefile.am:16: but option 'subdir-objects' is disabled
Makefile.am:16: warning: source file 'sph/simd.c' is in a subdirectory,
Makefile.am:16: but option 'subdir-objects' is disabled
Makefile.am:16: warning: source file 'sph/hamsi.c' is in a subdirectory,
Makefile.am:16: but option 'subdir-objects' is disabled
Makefile.am:16: warning: source file 'sph/hamsi_helper.c' is in a subdirectory,
Makefile.am:16: but option 'subdir-objects' is disabled
Makefile.am:16: warning: source file 'sph/shabal.c' is in a subdirectory,
Makefile.am:16: but option 'subdir-objects' is disabled
Makefile.am:16: warning: source file 'sph/whirlpool.c' is in a subdirectory,
Makefile.am:16: but option 'subdir-objects' is disabled
$ $ ./configure
checking build system type... x86_64-unknown-linux-gnu
checking host system type... x86_64-unknown-linux-gnu
checking target system type... x86_64-unknown-linux-gnu
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
/home/user/test/ccminer-KBomba/missing: Unknown `--is-lightweight' option
Try `/home/user/test/ccminer-KBomba/missing --help' for more information
configure: WARNING: 'missing' script is too old or missing
checking for a thread-safe mkdir -p... /bin/mkdir -p
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking whether make supports nested variables... yes
checking whether to enable maintainer-specific portions of Makefiles... no
checking for style of include used by make... GNU
checking for gcc... gcc
checking whether the C compiler works... yes
checking for C compiler default output file name... a.out
checking for suffix of executables...
checking whether we are cross compiling... no
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ISO C89... none needed
checking whether gcc understands -c and -o together... yes
checking dependency style of gcc... gcc3
checking for gcc option to accept ISO C99... -std=gnu99
checking how to run the C preprocessor... gcc -std=gnu99 -E
checking for grep that handles long lines and -e... /bin/grep
checking for egrep... /bin/grep -E
checking whether gcc -std=gnu99 needs -traditional... no
checking dependency style of gcc -std=gnu99... gcc3
checking for ranlib... ranlib
checking for g++... g++
checking whether we are using the GNU C++ compiler... yes
checking whether g++ accepts -g... yes
checking dependency style of g++... gcc3
checking for gcc -std=gnu99 option to support OpenMP... -fopenmp
checking for ANSI C header files... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking sys/endian.h usability... no
checking sys/endian.h presence... no
checking for sys/endian.h... no
checking sys/param.h usability... yes
checking sys/param.h presence... yes
checking for sys/param.h... yes
checking syslog.h usability... yes
checking syslog.h presence... yes
checking for syslog.h... yes
checking for sys/sysctl.h... yes
checking whether be32dec is declared... no
checking whether le32dec is declared... no
checking whether be32enc is declared... no
checking whether le32enc is declared... no
checking for size_t... yes
checking for working alloca.h... yes
checking for alloca... yes
checking for getopt_long... yes
checking whether we can compile AVX code... yes
checking whether we can compile XOP code... yes
checking whether we can compile AVX2 code... yes
checking for json_loads in -ljansson... no
checking for pthread_create in -lpthread... yes
checking for SSL_library_init in -lssl... yes
checking for EVP_DigestFinal_ex in -lcrypto... yes
checking for gawk... (cached) gawk
checking for curl-config... /usr/bin/curl-config
checking for the version of libcurl... 7.35.0
checking for libcurl >= version 7.15.2... yes
checking whether libcurl is usable... yes
checking for curl_free... yes
checking that generated files are newer than configure... done
configure: creating ./config.status
config.status: creating Makefile
config.status: creating compat/Makefile
config.status: creating compat/jansson/Makefile
config.status: creating cpuminer-config.h
config.status: executing depfiles commands
$
$ make
/bin/bash ./config.status
config.status: creating Makefile
config.status: creating compat/Makefile
config.status: creating compat/jansson/Makefile
config.status: creating cpuminer-config.h
config.status: cpuminer-config.h is unchanged
config.status: executing depfiles commands
make all-recursive
make[1]: Entering directory `/home/user/test/ccminer-KBomba'
Making all in compat
make[2]: Entering directory `/home/user/test/ccminer-KBomba/compat'
Making all in jansson
make[3]: Entering directory `/home/user/test/ccminer-KBomba/compat/jansson'
gcc -std=gnu99 -DHAVE_CONFIG_H -I. -I../.. -g -O2 -MT dump.o -MD -MP -MF .deps/dump.Tpo -c -o dump.o dump.c
mv -f .deps/dump.Tpo .deps/dump.Po
gcc -std=gnu99 -DHAVE_CONFIG_H -I. -I../.. -g -O2 -MT hashtable.o -MD -MP -MF .deps/hashtable.Tpo -c -o hashtable.o hashtable.c
mv -f .deps/hashtable.Tpo .deps/hashtable.Po
gcc -std=gnu99 -DHAVE_CONFIG_H -I. -I../.. -g -O2 -MT load.o -MD -MP -MF .deps/load.Tpo -c -o load.o load.c
mv -f .deps/load.Tpo .deps/load.Po
gcc -std=gnu99 -DHAVE_CONFIG_H -I. -I../.. -g -O2 -MT strbuffer.o -MD -MP -MF .deps/strbuffer.Tpo -c -o strbuffer.o strbuffer.c
mv -f .deps/strbuffer.Tpo .deps/strbuffer.Po
gcc -std=gnu99 -DHAVE_CONFIG_H -I. -I../.. -g -O2 -MT utf.o -MD -MP -MF .deps/utf.Tpo -c -o utf.o utf.c
mv -f .deps/utf.Tpo .deps/utf.Po
gcc -std=gnu99 -DHAVE_CONFIG_H -I. -I../.. -g -O2 -MT value.o -MD -MP -MF .deps/value.Tpo -c -o value.o value.c
mv -f .deps/value.Tpo .deps/value.Po
rm -f libjansson.a
ar cru libjansson.a dump.o hashtable.o load.o strbuffer.o utf.o value.o
ranlib libjansson.a
make[3]: Leaving directory `/home/user/test/ccminer-KBomba/compat/jansson'
make[3]: Entering directory `/home/user/test/ccminer-KBomba/compat'
make[3]: Nothing to be done for `all-am'.
make[3]: Leaving directory `/home/user/test/ccminer-KBomba/compat'
make[2]: Leaving directory `/home/user/test/ccminer-KBomba/compat'
make[2]: Entering directory `/home/user/test/ccminer-KBomba'
gcc -std=gnu99 -DHAVE_CONFIG_H -I. -msse2 -fopenmp -pthread -fno-strict-aliasing -I./compat/jansson -DSCRYPT_KECCAK512 -DSCRYPT_CHACHA -DSCRYPT_CHOOSE_COMPILETIME -g -O2 -MT ccminer-cpu-miner.o -MD -MP -MF .deps/ccminer-cpu-miner.Tpo -c -o ccminer-cpu-miner.o `test -f 'cpu-miner.c' || echo './'`cpu-miner.c
mv -f .deps/ccminer-cpu-miner.Tpo .deps/ccminer-cpu-miner.Po
gcc -std=gnu99 -DHAVE_CONFIG_H -I. -msse2 -fopenmp -pthread -fno-strict-aliasing -I./compat/jansson -DSCRYPT_KECCAK512 -DSCRYPT_CHACHA -DSCRYPT_CHOOSE_COMPILETIME -g -O2 -MT ccminer-util.o -MD -MP -MF .deps/ccminer-util.Tpo -c -o ccminer-util.o `test -f 'util.c' || echo './'`util.c
mv -f .deps/ccminer-util.Tpo .deps/ccminer-util.Po
gcc -std=gnu99 -DHAVE_CONFIG_H -I. -msse2 -fopenmp -pthread -fno-strict-aliasing -I./compat/jansson -DSCRYPT_KECCAK512 -DSCRYPT_CHACHA -DSCRYPT_CHOOSE_COMPILETIME -g -O2 -MT ccminer-bmw.o -MD -MP -MF .deps/ccminer-bmw.Tpo -c -o ccminer-bmw.o `test -f 'sph/bmw.c' || echo './'`sph/bmw.c
mv -f .deps/ccminer-bmw.Tpo .deps/ccminer-bmw.Po
gcc -std=gnu99 -DHAVE_CONFIG_H -I. -msse2 -fopenmp -pthread -fno-strict-aliasing -I./compat/jansson -DSCRYPT_KECCAK512 -DSCRYPT_CHACHA -DSCRYPT_CHOOSE_COMPILETIME -g -O2 -MT ccminer-blake.o -MD -MP -MF .deps/ccminer-blake.Tpo -c -o ccminer-blake.o `test -f 'sph/blake.c' || echo './'`sph/blake.c
mv -f .deps/ccminer-blake.Tpo .deps/ccminer-blake.Po
gcc -std=gnu99 -DHAVE_CONFIG_H -I. -msse2 -fopenmp -pthread -fno-strict-aliasing -I./compat/jansson -DSCRYPT_KECCAK512 -DSCRYPT_CHACHA -DSCRYPT_CHOOSE_COMPILETIME -g -O2 -MT ccminer-groestl.o -MD -MP -MF .deps/ccminer-groestl.Tpo -c -o ccminer-groestl.o `test -f 'sph/groestl.c' || echo './'`sph/groestl.c
mv -f .deps/ccminer-groestl.Tpo .deps/ccminer-groestl.Po
gcc -std=gnu99 -DHAVE_CONFIG_H -I. -msse2 -fopenmp -pthread -fno-strict-aliasing -I./compat/jansson -DSCRYPT_KECCAK512 -DSCRYPT_CHACHA -DSCRYPT_CHOOSE_COMPILETIME -g -O2 -MT ccminer-jh.o -MD -MP -MF .deps/ccminer-jh.Tpo -c -o ccminer-jh.o `test -f 'sph/jh.c' || echo './'`sph/jh.c
mv -f .deps/ccminer-jh.Tpo .deps/ccminer-jh.Po
gcc -std=gnu99 -DHAVE_CONFIG_H -I. -msse2 -fopenmp -pthread -fno-strict-aliasing -I./compat/jansson -DSCRYPT_KECCAK512 -DSCRYPT_CHACHA -DSCRYPT_CHOOSE_COMPILETIME -g -O2 -MT ccminer-keccak.o -MD -MP -MF .deps/ccminer-keccak.Tpo -c -o ccminer-keccak.o `test -f 'sph/keccak.c' || echo './'`sph/keccak.c
mv -f .deps/ccminer-keccak.Tpo .deps/ccminer-keccak.Po
gcc -std=gnu99 -DHAVE_CONFIG_H -I. -msse2 -fopenmp -pthread -fno-strict-aliasing -I./compat/jansson -DSCRYPT_KECCAK512 -DSCRYPT_CHACHA -DSCRYPT_CHOOSE_COMPILETIME -g -O2 -MT ccminer-skein.o -MD -MP -MF .deps/ccminer-skein.Tpo -c -o ccminer-skein.o `test -f 'sph/skein.c' || echo './'`sph/skein.c
mv -f .deps/ccminer-skein.Tpo .deps/ccminer-skein.Po
gcc -std=gnu99 -DHAVE_CONFIG_H -I. -msse2 -fopenmp -pthread -fno-strict-aliasing -I./compat/jansson -DSCRYPT_KECCAK512 -DSCRYPT_CHACHA -DSCRYPT_CHOOSE_COMPILETIME -g -O2 -MT ccminer-hefty1.o -MD -MP -MF .deps/ccminer-hefty1.Tpo -c -o ccminer-hefty1.o `test -f 'hefty1.c' || echo './'`hefty1.c
mv -f .deps/ccminer-hefty1.Tpo .deps/ccminer-hefty1.Po
gcc -std=gnu99 -DHAVE_CONFIG_H -I. -msse2 -fopenmp -pthread -fno-strict-aliasing -I./compat/jansson -DSCRYPT_KECCAK512 -DSCRYPT_CHACHA -DSCRYPT_CHOOSE_COMPILETIME -g -O2 -MT ccminer-scrypt.o -MD -MP -MF .deps/ccminer-scrypt.Tpo -c -o ccminer-scrypt.o `test -f 'scrypt.c' || echo './'`scrypt.c
scrypt.c: In function ‘scanhash_scrypt’:
scrypt.c:724:4: warning: implicit declaration of function ‘scrypt_1024_1_1_256_4way’ [-Wimplicit-function-declaration]
scrypt_1024_1_1_256_4way(data, hash, midstate, scratchbuf);
^
scrypt.c:729:4: warning: implicit declaration of function ‘scrypt_1024_1_1_256_12way’ [-Wimplicit-function-declaration]
scrypt_1024_1_1_256_12way(data, hash, midstate, scratchbuf);
^
scrypt.c:734:4: warning: implicit declaration of function ‘scrypt_1024_1_1_256_24way’ [-Wimplicit-function-declaration]
scrypt_1024_1_1_256_24way(data, hash, midstate, scratchbuf);
^
scrypt.c:739:4: warning: implicit declaration of function ‘scrypt_1024_1_1_256_3way’ [-Wimplicit-function-declaration]
scrypt_1024_1_1_256_3way(data, hash, midstate, scratchbuf);
^
mv -f .deps/ccminer-scrypt.Tpo .deps/ccminer-scrypt.Po
gcc -std=gnu99 -DHAVE_CONFIG_H -I. -msse2 -fopenmp -pthread -fno-strict-aliasing -I./compat/jansson -DSCRYPT_KECCAK512 -DSCRYPT_CHACHA -DSCRYPT_CHOOSE_COMPILETIME -g -O2 -MT ccminer-sha2.o -MD -MP -MF .deps/ccminer-sha2.Tpo -c -o ccminer-sha2.o `test -f 'sha2.c' || echo './'`sha2.c
mv -f .deps/ccminer-sha2.Tpo .deps/ccminer-sha2.Po
nvcc -g -O2 -I . -Xptxas "-abi=no -v" -gencode=arch=compute_30,code=\"sm_30,compute_30\" -gencode=arch=compute_35,code=\"sm_35,compute_35\" --maxrregcount=80 --ptxas-options=-v -I./compat/jansson -o heavy/heavy.o -c heavy/heavy.cu
/bin/bash: nvcc: command not found
make[2]: *** [heavy/heavy.o] Error 127
make[2]: Leaving directory `/home/user/test/ccminer-KBomba'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/home/user/test/ccminer-KBomba'
make: *** [all] Error 2
$ $ sudo make install
[sudo] password for user:
make: stat: GNUmakefile: Permission denied
make: stat: makefile: Permission denied
make: stat: Makefile: Permission denied
make: stat: install: Permission denied
make: *** No rule to make target `install'. Stop.
$
So that's the farthest I got trying to compile ccminer, whatever version. you must use 1.0.02 What do you mean by that? I don't see this version number anywhere? Sorry if I'm being obtuse. I'm new to git and haven't done many compiles before. Thank you very much for responding! M. |
|
|
|
Hello, I'm teaching myself to mine alt-coins, using whatever minimal hardware I have on hand. I'm not concerned over hash rate or profitability at this point. I consider my energy cost an educational expense. If I score a few millicoins in the process, it's a bonus! I got cpuminer running a few days ago and have been busily churning out ~140 kH/s on Dash from 3 cores of my 2.66GHz Intel quad core processor under Linux Mint 17.1. Now I'm trying to graduate to a gpu setup and running into problems. I've tried compiling ccminer several times without success. Before wasting anybody's time with specific questions about the errors I've been getting, I want to make sure I'm trying to use the correct software. My "newest" video card is an ancient nVidia GeForce GT 440, a Compute 2 card. What will ccminer do if I try to run it on that old of a card? Will it run at all, which is all I'm looking for, or will it crash or fail to operate? What mining software will work with this old hardware? Those're my first questions. Thanks in advance for your help. M. |
|
|
|
|
