Show Posts
|
Pages: [1]
|
hangover: this version should build correctly with binutils 2.15. Let me know if the assembler still complains.
pooler, everything builds correctly, thank you!
|
|
|
Yes, you're right - base FreeBSD version is too old: $ ld --version GNU ld version 2.15 [FreeBSD] 2004-05-23 Copyright 2002 Free Software Foundation, Inc. Thank you, will search for workaround.
|
|
|
Unfortunately, new version doesn't compile under FreeBSD 8.2-RELEASE-p2 amd64 with following error: # gmake gmake all-recursive gmake[1]: Entering directory `/usr/home/qwe/cpuminer' Making all in compat gmake[2]: Entering directory `/usr/home/qwe/cpuminer/compat' Making all in jansson gmake[3]: Entering directory `/usr/home/qwe/cpuminer/compat/jansson' gmake[3]: Nothing to be done for `all'. gmake[3]: Leaving directory `/usr/home/qwe/cpuminer/compat/jansson' gmake[3]: Entering directory `/usr/home/qwe/cpuminer/compat' gmake[3]: Nothing to be done for `all-am'. gmake[3]: Leaving directory `/usr/home/qwe/cpuminer/compat' gmake[2]: Leaving directory `/usr/home/qwe/cpuminer/compat' gmake[2]: Entering directory `/usr/home/qwe/cpuminer' gcc -DHAVE_CONFIG_H -I. -pthread -fno-strict-aliasing -I./compat/jansson -I/usr/local/include -g -O2 -MT minerd-scrypt-x64.o -MD -MP -MF .deps/minerd-scrypt-x64.Tpo -c -o minerd-scrypt-x64.o `test -f 'scrypt-x64.S' || echo './'`scrypt-x64.S scrypt-x64.S: Assembler messages: scrypt-x64.S:1700: Error: `(%ebp,%ebp,2)' is not a valid 64 bit base/index expression scrypt-x64.S:1704: Error: `(%ebx,%ebx,2)' is not a valid 64 bit base/index expression scrypt-x64.S:1709: Error: `(%r8d,%r8d,2)' is not a valid 64 bit base/index expression gmake[2]: *** [minerd-scrypt-x64.o] Error 1 gmake[2]: Leaving directory `/usr/home/qwe/cpuminer' gmake[1]: *** [all-recursive] Error 1 gmake[1]: Leaving directory `/usr/home/qwe/cpuminer' gmake: *** [all] Error 2
|
|
|
Well, thank you for your care about my job, heh But my post wasn't about bitcoin mining soft only There are some new alternative crypto currencies (LiteCoin, Tenebrix, etc.) that grow rapidly enough, and it uses CPU proof of work (scrypt algorithm).
|
|
|
Sorry for necroposting, but there is solution. (I am using FreeBSD). $ cd cpuminer $ mkdir m4 $ cp /usr/local/share/doc/curl/libcurl/libcurl.m4 m4
Then add string "ACLOCAL_AMFLAGS = -I m4" to file Makefile.am and edit file autogen.sh - replace string "aclocal" with "aclocal -I m4". That's all.
|
|
|
Or you can write simple AutoIt script (miner-starter) to start miner from it and compile it to exe with corresponding option.
|
|
|
You can try aticonfig --od-gettemperature
|
|
|
My cpuminer work on Windows (32-bit) as well as Linux.
FreeBSD i386 too.
|
|
|
To double program output to file, you can make something like that: minerd --threads X --url http://mypool.local:8332 --userpass user:pass 2>&1 | tee /some/path/log.log Ok, that puts "1 miner threads started, using SHA256 'cryptopp_asm32' algorithm." into the logfile, but fails to record (or display) the hashcount. Progress, but still not 100% Thanks for the fast response, btw. Hmm. It seems to me that cpuminer with tee gives output 'by portions'. I started minerd and got this: hangover@hangover:~$ minerd --threads 2 --url http://mining.bitcoin.cz:8332 --userpass hangover.XX:YY 2>&1 | tee /home/hangover/loglog 2 miner threads started, using SHA256 'c' algorithm. And after waiting for 5 minutes I got this: HashMeter(1): 16777215 hashes, 628.20 khash/sec HashMeter(0): 16777215 hashes, 620.19 khash/sec HashMeter(0): 8388607 hashes, 643.54 khash/sec HashMeter(1): 8388607 hashes, 637.17 khash/sec HashMeter(1): 4194303 hashes, 502.27 khash/sec HashMeter(0): 4194303 hashes, 430.20 khash/sec HashMeter(1): 3194303 hashes, 582.57 khash/sec HashMeter(0): 3194303 hashes, 602.13 khash/sec HashMeter(1): 3194303 hashes, 582.68 khash/sec HashMeter(0): 3194303 hashes, 586.11 khash/sec HashMeter(0): 3194303 hashes, 632.09 khash/sec HashMeter(1): 3194303 hashes, 598.81 khash/sec HashMeter(0): 3194303 hashes, 643.12 khash/sec HashMeter(1): 3194303 hashes, 628.86 khash/sec HashMeter(0): 3294303 hashes, 638.16 khash/sec HashMeter(1): 3194303 hashes, 643.76 khash/sec HashMeter(0): 3294303 hashes, 661.30 khash/sec HashMeter(1): 3294303 hashes, 641.22 khash/sec HashMeter(0): 3394303 hashes, 645.43 khash/sec HashMeter(1): 3294303 hashes, 645.00 khash/sec HashMeter(0): 3394303 hashes, 647.02 khash/sec ...
|
|
|
One more thing to ask: Is there a way to log the output? I tried the standard > redirect, but nothing is dumped into the text file, and nothing displays in the terminal screen, either.
Interestingly, the redirect works with the --help switch, and does fill the text file with the help output, and once I try redirecting the live program output, the text is blanked, but even with the >> append, nothing is ever put into the file. What am I doing wrong?
OS: Linux 10.04 Processor: Crap GPU: Crap
To double program output to file, you can make something like that: minerd --threads X --url http://mypool.local:8332 --userpass user:pass 2>&1 | tee /some/path/log.log
|
|
|
Patch for successfull compilation of minerd under FreeBSD: --- miner.h.orig 2011-02-10 11:51:55.000000000 +0600 +++ miner.h 2011-02-16 16:04:28.000000000 +0600 @@ -5,7 +5,7 @@ #include <stdint.h> #include <sys/time.h> #include <jansson.h> -#include <curl/curl.h> +#include </usr/local/include/curl/curl.h> #ifdef __SSE2__ #define WANT_SSE2_4WAY 1 @@ -18,7 +18,12 @@ #if ((__GNUC__ > 4) || (__GNUC__ == 4 && __GNUC_MINOR__ >= 3)) #define WANT_BUILTIN_BSWAP #else -#include <byteswap.h> +/* #include <byteswap.h> */ // <-- doesn't exist under FreeBSD +# define bswap_64 __bswap64 +# define bswap_32 __bswap32 +# define bswap_16 __bswap16 +# define __BIG_ENDIAN__ (_BYTE_ORDER == _BIG_ENDIAN) +#include <sys/endian.h> #endif #if defined(__i386__)
|
|
|
I have the same thing. Trying to configure sources on FreeBSD 8.1-RELEASE-p2 i386. Maybe, there are some linker flags or workarounds or something?
The solution here is easy: don't build from git, build from tarball releases. The tarball already has the proper configure script generated, so you don't have to worry about missing macros or broken OS configurations. Thank you very much!
|
|
|
Because: $ ./configure [...] checking for pkg-config... /opt/local/bin/pkg-config checking pkg-config is at least version 0.9.0... yes ./configure: line 4301: syntax error near unexpected token `,' ./configure: line 4301: `LIBCURL_CHECK_CONFIG(, 7.10.1, ,'
autogen could not find your libcurl autoconf macros. Sounds like you have a non-standard installation, outside the normal autoconf/automake paths. I have the same thing. Trying to configure sources on FreeBSD 8.1-RELEASE-p2 i386. Maybe, there are some linker flags or workarounds or something?
|
|
|
|