Topic: [ANN] [QRK] Quark | Core 0.10 upgrade - page 388. (Read 1031025 times)
I was overwhelmed by the amount of logo on the quarkcoin web site. Nearly had a stroke. We need someone with talent to take over the website.
almost perfect exchange unfotunately so far it is missing one quite important ingredience..... there is no volume.....
and without volume it is quite a problem....
but I must admit that it is well done but they should offer something to attract people and liquidity, I tried to bought several coins but of course so far without success. And I am thinking of sending my funds away....
In this initial period they should offer eg trading of new coins which are not possible to trade anywhere else or low fees or some special news for cryptocoin community otherwise I dont know why I should put my money and enable them liquidity with my funds....
Agree 100 %. The pathetic trade volume is a serious problem. Also, the difficulty has halved over the past 24 hours. In other words, the support from both miners and traders is decreasing fast. Those are very bad signs for the future of Quarkcoin.
https://www.cryptsy.com/markets/view/71
that new exchange has pathetic trade volume, yes
For scrypt mining (and scrypt-jane) it takes 65536 hashes to get a share of diff 1. It also takes 65536 shares (diff 1) for every point of difficulty to find a block. This doesn't seem to be the case for QRK. Does anyone know these values for QRK?
That's not entirely right.
IMHO there is a somewhat defacto standard for stratum only, where the diff for scrypt based coins is a 65536 multiply if the original diff which the wallet reports.
So Bitcoin, Litecoin, and so on all require at average for a wallet-diff 1 2^32 hashes (means 65536*65536)
Quarkcoin and quarkcoin clones are "one byte off", means a wallet-diff 1 needs at average 2^24 hashes
Since scrypt is much slower than the sha stuff, scrypt based coins started with a much lower difficulty (i think 256*128 times lower) than bitcoin based ones.
I don't know if stratum at first only supported integer diffs and not the needed 0.00xxx diffs, or whatever the reason was, somehow on stratum the coins diff (as reported by the wallet) is multiplied by 65536.
As said for Quark: Diff 1 is 2^24. Stratum shouldn't modify this value. At least i didn't code any reversing of stratum diff in the minerd.
(If i did write garbage, please correct me)
Sounds like someone switched off a botnet (or his boss found out). The hashrate on the few p2pools I checked, including mine, is rather stable. Also, was the diff really above 950? I don't look for the diff often, didn't notice that.
Also we have some mainly 1:1 clones using the quark hashing algorithm
Did some benchmarks of the sse4 miner (just took this version https://bitcointalksearch.org/topic/m.3047868) on a bunch of Intel Core2 Duo and Ivy bridge, and here comes the great equation.
The hashrate is a linear frequency function (what a rocket science). For quark algo just divide frequency by 27.5 for no HT, or by 40 for HT to estimate Khashes PER THREAD. If you run less threads than CPUs on HT, the number is somewhere in between. E.g. for 3 threads on 4-thread CPU or 6 threads on 8-thread CPU it is ~35, see https://bitcointalksearch.org/topic/m.3076346. It would be nice if various CPU owners will try the formula and prove or disprove it.
I do not have any AMDs at hand, but it seems they follow "no HT" path for ALL cores (https://bitcointalksearch.org/topic/m.3021817). Thus, high-frequency AMD FXs are winners in terms of kh per CPU. I am getting 780kh on i7 3770k at 4GHz with HT (8 * 98), while FX 8350 gives 1100kh at 4 GHz (8 * 140). Here power consumption comes into play. For Intel it is ~8kh/watt for IB and ~2kh/watt or less for C2D. Can anyone provide wattage for AMDs (real-world numbers, not from online benchmarks)? Sandy Bridge and Haswell numbers would be usefull as well. Lets make quark hardware comparision table
The hashrate is a linear frequency function (what a rocket science). For quark algo just divide frequency by 27.5 for no HT, or by 40 for HT to estimate Khashes PER THREAD. If you run less threads than CPUs on HT, the number is somewhere in between. E.g. for 3 threads on 4-thread CPU or 6 threads on 8-thread CPU it is ~35, see https://bitcointalksearch.org/topic/m.3076346. It would be nice if various CPU owners will try the formula and prove or disprove it.
I do not have any AMDs at hand, but it seems they follow "no HT" path for ALL cores (https://bitcointalksearch.org/topic/m.3021817). Thus, high-frequency AMD FXs are winners in terms of kh per CPU. I am getting 780kh on i7 3770k at 4GHz with HT (8 * 98), while FX 8350 gives 1100kh at 4 GHz (8 * 140). Here power consumption comes into play. For Intel it is ~8kh/watt for IB and ~2kh/watt or less for C2D. Can anyone provide wattage for AMDs (real-world numbers, not from online benchmarks)? Sandy Bridge and Haswell numbers would be usefull as well. Lets make quark hardware comparision table
I have an AMD Sempron 145 Sargas 2.8GHz (single core) w/ "core unlocked" and overclocked a bit (with that motherboard's "OC Genie") that gets about 220khash.. my i7-960 (it's not overclocked, but I have turbomode enabled, so it does that automatically, goes to 3.35ghash or so) can get about 600-620khash/s tops.. i7-4770k is 1mhash+, but well, it costs a lot more than what you'd need for equivalent from AMD CPU
oh, *intel e6850 gets around 200khash w/o overclocking
err, never got around to this
had an emergency visit to the hospital to get my gall bladder removed
i haven't read posts after this yet, so if nothing is still there, i'll try it this weekend
hope he is definetely gone. He made a lot of bad things to quarkcoin and community.
I want to eat that. Can't someone make quark candy? And for every bag of quarks you buy, you get some coins.
And of course you eventually get enough coins to buy more quarks with it, or other goods/services. Let's get it into Walmart. 
For scrypt mining (and scrypt-jane) it takes 65536 hashes to get a share of diff 1. It also takes 65536 shares (diff 1) for every point of difficulty to find a block. This doesn't seem to be the case for QRK. Does anyone know these values for QRK?
That's not entirely right.
IMHO there is a somewhat defacto standard for stratum only, where the diff for scrypt based coins is a 65536 multiply if the original diff which the wallet reports.
So Bitcoin, Litecoin, and so on all require at average for a wallet-diff 1 2^32 hashes (means 65536*65536)
Quarkcoin and quarkcoin clones are "one byte off", means a wallet-diff 1 needs at average 2^24 hashes
Since scrypt is much slower than the sha stuff, scrypt based coins started with a much lower difficulty (i think 256*128 times lower) than bitcoin based ones.
I don't know if stratum at first only supported integer diffs and not the needed 0.00xxx diffs, or whatever the reason was, somehow on stratum the coins diff (as reported by the wallet) is multiplied by 65536.
As said for Quark: Diff 1 is 2^24. Stratum shouldn't modify this value. At least i didn't code any reversing of stratum diff in the minerd.
(If i did write garbage, please correct me)
Sounds like someone switched off a botnet (or his boss found out). The hashrate on the few p2pools I checked, including mine, is rather stable. Also, was the diff really above 950? I don't look for the diff often, didn't notice that.
Also we have some mainly 1:1 clones using the quark hashing algorithm
Sep 02 - 512
Sep 23 - 256
Oct 14 - 128
Nov 07 - 64
Nov 28 - 32
Dec 19 - 16
Sep 23 - 256
Oct 14 - 128
Nov 07 - 64
Nov 28 - 32
Dec 19 - 16
Can anyone list the approximate dates to when the coin reward will halve. Every three weeks. When was the last halve.
September 2nd was the last, putting 3 weeks at September 23rd.
How much coins is in block now? 1024 or 512?
Has now halved to 512
Can anyone list the approximate dates to when the coin reward will halve. Every three weeks. When was the last halve.
almost perfect exchange unfotunately so far it is missing one quite important ingredience..... there is no volume.....
and without volume it is quite a problem....
but I must admit that it is well done but they should offer something to attract people and liquidity, I tried to bought several coins but of course so far without success. And I am thinking of sending my funds away....
In this initial period they should offer eg trading of new coins which are not possible to trade anywhere else or low fees or some special news for cryptocoin community otherwise I dont know why I should put my money and enable them liquidity with my funds....
Agree 100 %. The pathetic trade volume is a serious problem. Also, the difficulty has halved over the past 24 hours. In other words, the support from both miners and traders is decreasing fast. Those are very bad signs for the future of Quarkcoin.
I didn't notice a big change in the difficulty. Recently it is always fluctuating around 500 (sometimes ~400, sometimes ~600). Also, the supply is decreasing dramatically due to the reduced block reward. So, to some extent, it is expected that the trade volume also goes down.
already tried adding it numerous times dude
trust me this shit is messed up.. if you can compile it feel free to gimme advice
so far i've gotten, "well some builds may be broken"
lol
so people may want to know their screwed if they see the getting started page on the SRC pool i'm on for example
whether it says to go grab it and compile it etc
people passing around failed messy broken git code links s pretty lame !
luckily no one seems to care hahha
and someone posting misc builds proves nothing.. doesn't mean it was current from GIT
trust me this shit is messed up.. if you can compile it feel free to gimme advice
so far i've gotten, "well some builds may be broken"
lol
so people may want to know their screwed if they see the getting started page on the SRC pool i'm on for example
whether it says to go grab it and compile it etc
people passing around failed messy broken git code links s pretty lame !
luckily no one seems to care hahha
and someone posting misc builds proves nothing.. doesn't mean it was current from GIT
NO NO NO, IT IS NOT ADDED.
Sounds like someone switched off a botnet (or his boss found out). The hashrate on the few p2pools I checked, including mine, is rather stable. Also, was the diff really above 950? I don't look for the diff often, didn't notice that.
almost perfect exchange unfotunately so far it is missing one quite important ingredience..... there is no volume.....
and without volume it is quite a problem....
but I must admit that it is well done but they should offer something to attract people and liquidity, I tried to bought several coins but of course so far without success. And I am thinking of sending my funds away....
In this initial period they should offer eg trading of new coins which are not possible to trade anywhere else or low fees or some special news for cryptocoin community otherwise I dont know why I should put my money and enable them liquidity with my funds....
Agree 100 %. The pathetic trade volume is a serious problem. Also, the difficulty has halved over the past 24 hours. In other words, the support from both miners and traders is decreasing fast. Those are very bad signs for the future of Quarkcoin.
already tried adding it numerous times dude
trust me this shit is messed up.. if you can compile it feel free to gimme advice
so far i've gotten, "well some builds may be broken"
lol
so people may want to know their screwed if they see the getting started page on the SRC pool i'm on for example
whether it says to go grab it and compile it etc
people passing around failed messy broken git code links s pretty lame !
luckily no one seems to care hahha
and someone posting misc builds proves nothing.. doesn't mean it was current from GIT
trust me this shit is messed up.. if you can compile it feel free to gimme advice
so far i've gotten, "well some builds may be broken"
lol
so people may want to know their screwed if they see the getting started page on the SRC pool i'm on for example
whether it says to go grab it and compile it etc
people passing around failed messy broken git code links s pretty lame !
luckily no one seems to care hahha
and someone posting misc builds proves nothing.. doesn't mean it was current from GIT
be nice to get uncle_bobs newest git code to work.. GCC on windows throws compiler errors. *STILL
can ANYONE get it to build ?
this is the best code base ? or should i go with the other one ?
here is my build log..
can ANYONE get it to build ?
this is the best code base ? or should i go with the other one ?
here is my build log..
Code:
$ make
make all-recursive
make[1]: Entering directory `/c/code/quarkminer'
Making all in compat
make[2]: Entering directory `/c/code/quarkminer/compat'
Making all in jansson
make[3]: Entering directory `/c/code/quarkminer/compat/jansson'
make[3]: Nothing to be done for `all'.
make[3]: Leaving directory `/c/code/quarkminer/compat/jansson'
make[3]: Entering directory `/c/code/quarkminer/compat'
make[3]: Nothing to be done for `all-am'.
make[3]: Leaving directory `/c/code/quarkminer/compat'
make[2]: Leaving directory `/c/code/quarkminer/compat'
make[2]: Entering directory `/c/code/quarkminer'
x86_64-w64-mingw32-gcc -std=gnu99 -DHAVE_CONFIG_H -I. -fno-strict-aliasing -I./
compat/jansson -I/c/mingw64/include -msse4.1 -O3 -MT minerd-quark.o -MD -MP -M
F .deps/minerd-quark.Tpo -c -o minerd-quark.o `test -f 'quark.c' || echo './'`qu
ark.c
quark.c: In function 'quarkhash':
quark.c:95:13: warning: assignment discards 'const' qualifier from pointer targe
t type [enabled by default]
quark.c:124:13: warning: right shift count >= width of type [enabled by default]
quark.c:124:13: warning: right shift count >= width of type [enabled by default]
quark.c:124:13: warning: right shift count >= width of type [enabled by default]
quark.c:124:13: warning: right shift count >= width of type [enabled by default]
mv -f .deps/minerd-quark.Tpo .deps/minerd-quark.Po
x86_64-w64-mingw32-gcc -std=gnu99 -msse4.1 -O3 -o minerd.exe minerd-cpu-miner
.o minerd-util.o minerd-sha2.o minerd-sha2-arm.o minerd-sha2-x86.o minerd-sha2-x
64.o minerd-scrypt.o minerd-scrypt-arm.o minerd-scrypt-x86.o minerd-scrypt-x64.o
minerd-quark.o minerd-grso.o -L/c/mingw64/lib -lcurl -lwldap32 -lws2_32 compat/
jansson/libjansson.a -lpthread -lws2_32
minerd-grso.o:grso.c:(.text+0x0): multiple definition of `grsoTransform'
minerd-quark.o:quark.c:(.text+0x1170): first defined here
minerd-grso.o:grso.c:(.text+0x3d0): multiple definition of `grsoOutputTransforma
tion'
minerd-quark.o:quark.c:(.text+0x7d0): first defined here
minerd-grso.o:grso.c:(.rdata+0x0): multiple definition of `grsoT7'
minerd-quark.o:quark.c:(.rdata+0x70): first defined here
minerd-grso.o:grso.c:(.rdata+0x800): multiple definition of `grsoT6'
minerd-quark.o:quark.c:(.rdata+0x870): first defined here
minerd-grso.o:grso.c:(.rdata+0x1000): multiple definition of `grsoT5'
minerd-quark.o:quark.c:(.rdata+0x1070): first defined here
minerd-grso.o:grso.c:(.rdata+0x1800): multiple definition of `grsoT4'
minerd-quark.o:quark.c:(.rdata+0x1870): first defined here
minerd-grso.o:grso.c:(.rdata+0x2000): multiple definition of `grsoT3'
minerd-quark.o:quark.c:(.rdata+0x2070): first defined here
minerd-grso.o:grso.c:(.rdata+0x2800): multiple definition of `grsoT2'
minerd-quark.o:quark.c:(.rdata+0x2870): first defined here
minerd-grso.o:grso.c:(.rdata+0x3000): multiple definition of `grsoT1'
minerd-quark.o:quark.c:(.rdata+0x3070): first defined here
minerd-grso.o:grso.c:(.rdata+0x3800): multiple definition of `grsoT0'
minerd-quark.o:quark.c:(.rdata+0x3870): first defined here
collect2.exe: error: ld returned 1 exit status
make[2]: *** [minerd.exe] Error 1
make[2]: Leaving directory `/c/code/quarkminer'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/c/code/quarkminer'
make: *** [all] Error 2
make all-recursive
make[1]: Entering directory `/c/code/quarkminer'
Making all in compat
make[2]: Entering directory `/c/code/quarkminer/compat'
Making all in jansson
make[3]: Entering directory `/c/code/quarkminer/compat/jansson'
make[3]: Nothing to be done for `all'.
make[3]: Leaving directory `/c/code/quarkminer/compat/jansson'
make[3]: Entering directory `/c/code/quarkminer/compat'
make[3]: Nothing to be done for `all-am'.
make[3]: Leaving directory `/c/code/quarkminer/compat'
make[2]: Leaving directory `/c/code/quarkminer/compat'
make[2]: Entering directory `/c/code/quarkminer'
x86_64-w64-mingw32-gcc -std=gnu99 -DHAVE_CONFIG_H -I. -fno-strict-aliasing -I./
compat/jansson -I/c/mingw64/include -msse4.1 -O3 -MT minerd-quark.o -MD -MP -M
F .deps/minerd-quark.Tpo -c -o minerd-quark.o `test -f 'quark.c' || echo './'`qu
ark.c
quark.c: In function 'quarkhash':
quark.c:95:13: warning: assignment discards 'const' qualifier from pointer targe
t type [enabled by default]
quark.c:124:13: warning: right shift count >= width of type [enabled by default]
quark.c:124:13: warning: right shift count >= width of type [enabled by default]
quark.c:124:13: warning: right shift count >= width of type [enabled by default]
quark.c:124:13: warning: right shift count >= width of type [enabled by default]
mv -f .deps/minerd-quark.Tpo .deps/minerd-quark.Po
x86_64-w64-mingw32-gcc -std=gnu99 -msse4.1 -O3 -o minerd.exe minerd-cpu-miner
.o minerd-util.o minerd-sha2.o minerd-sha2-arm.o minerd-sha2-x86.o minerd-sha2-x
64.o minerd-scrypt.o minerd-scrypt-arm.o minerd-scrypt-x86.o minerd-scrypt-x64.o
minerd-quark.o minerd-grso.o -L/c/mingw64/lib -lcurl -lwldap32 -lws2_32 compat/
jansson/libjansson.a -lpthread -lws2_32
minerd-grso.o:grso.c:(.text+0x0): multiple definition of `grsoTransform'
minerd-quark.o:quark.c:(.text+0x1170): first defined here
minerd-grso.o:grso.c:(.text+0x3d0): multiple definition of `grsoOutputTransforma
tion'
minerd-quark.o:quark.c:(.text+0x7d0): first defined here
minerd-grso.o:grso.c:(.rdata+0x0): multiple definition of `grsoT7'
minerd-quark.o:quark.c:(.rdata+0x70): first defined here
minerd-grso.o:grso.c:(.rdata+0x800): multiple definition of `grsoT6'
minerd-quark.o:quark.c:(.rdata+0x870): first defined here
minerd-grso.o:grso.c:(.rdata+0x1000): multiple definition of `grsoT5'
minerd-quark.o:quark.c:(.rdata+0x1070): first defined here
minerd-grso.o:grso.c:(.rdata+0x1800): multiple definition of `grsoT4'
minerd-quark.o:quark.c:(.rdata+0x1870): first defined here
minerd-grso.o:grso.c:(.rdata+0x2000): multiple definition of `grsoT3'
minerd-quark.o:quark.c:(.rdata+0x2070): first defined here
minerd-grso.o:grso.c:(.rdata+0x2800): multiple definition of `grsoT2'
minerd-quark.o:quark.c:(.rdata+0x2870): first defined here
minerd-grso.o:grso.c:(.rdata+0x3000): multiple definition of `grsoT1'
minerd-quark.o:quark.c:(.rdata+0x3070): first defined here
minerd-grso.o:grso.c:(.rdata+0x3800): multiple definition of `grsoT0'
minerd-quark.o:quark.c:(.rdata+0x3870): first defined here
collect2.exe: error: ld returned 1 exit status
make[2]: *** [minerd.exe] Error 1
make[2]: Leaving directory `/c/code/quarkminer'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/c/code/quarkminer'
make: *** [all] Error 2
Makefile.am must have "grso.c" added to "minerd_SOURCES", it shouldn't be there. At least some of the functions can get in-lined and confuse the compiler less, if all compiled at once.
quark.c just #includes "bunch of .c file". it shouldn't be also made separately. Anyway, you're log shows that it is brought in from #includes and compiled separate.
Edit Makefile.am, run autogen.sh, "make distclean", configure with CFLAGS, and make.
I know someone else had posted windows builds. I don't have a working system to test it, would require setting up probably cygwin... I can try it all out in a vm, but i wouldn't optimize around it.
10,000 QRK sent
let me know you got it?
never know, may buy you a car one day!
if quark gets to $1 each one day
btw, is the image on a transaperent background? would be cool to have a couple different sizes if possible so people can maybe use on their sites
couple smaller maybe, one bigger
no worries if too much hassle, appreciate work
$1 Quark is not such a fantasy, we have a sound base and community support will build.
Unable to upload full size for some strange reason, links to the others follow:
http://i973.photobucket.com/albums/ae214/promethium00/Quark-Rotating-240x180_zps12b5ea6e.gif
http://i973.photobucket.com/albums/ae214/promethium00/Quark-Rotating-160x120_zps6171c597.gif
http://i973.photobucket.com/albums/ae214/promethium00/Quark-Rotating-80x60_zps5e139fcc.gif
http://i973.photobucket.com/albums/ae214/promethium00/Quark-Rotating-32x24_zps0f0d8d49.gif
Cheers.
this looks awesome! is it free to for anyone to use now?
be nice to get uncle_bobs newest git code to work.. GCC on windows throws compiler errors. *STILL
can ANYONE get it to build ?
this is the best code base ? or should i go with the other one ?
here is my build log..
can ANYONE get it to build ?
this is the best code base ? or should i go with the other one ?
here is my build log..
Code:
$ make
make all-recursive
make[1]: Entering directory `/c/code/quarkminer'
Making all in compat
make[2]: Entering directory `/c/code/quarkminer/compat'
Making all in jansson
make[3]: Entering directory `/c/code/quarkminer/compat/jansson'
make[3]: Nothing to be done for `all'.
make[3]: Leaving directory `/c/code/quarkminer/compat/jansson'
make[3]: Entering directory `/c/code/quarkminer/compat'
make[3]: Nothing to be done for `all-am'.
make[3]: Leaving directory `/c/code/quarkminer/compat'
make[2]: Leaving directory `/c/code/quarkminer/compat'
make[2]: Entering directory `/c/code/quarkminer'
x86_64-w64-mingw32-gcc -std=gnu99 -DHAVE_CONFIG_H -I. -fno-strict-aliasing -I./
compat/jansson -I/c/mingw64/include -msse4.1 -O3 -MT minerd-quark.o -MD -MP -M
F .deps/minerd-quark.Tpo -c -o minerd-quark.o `test -f 'quark.c' || echo './'`qu
ark.c
quark.c: In function 'quarkhash':
quark.c:95:13: warning: assignment discards 'const' qualifier from pointer targe
t type [enabled by default]
quark.c:124:13: warning: right shift count >= width of type [enabled by default]
quark.c:124:13: warning: right shift count >= width of type [enabled by default]
quark.c:124:13: warning: right shift count >= width of type [enabled by default]
quark.c:124:13: warning: right shift count >= width of type [enabled by default]
mv -f .deps/minerd-quark.Tpo .deps/minerd-quark.Po
x86_64-w64-mingw32-gcc -std=gnu99 -msse4.1 -O3 -o minerd.exe minerd-cpu-miner
.o minerd-util.o minerd-sha2.o minerd-sha2-arm.o minerd-sha2-x86.o minerd-sha2-x
64.o minerd-scrypt.o minerd-scrypt-arm.o minerd-scrypt-x86.o minerd-scrypt-x64.o
minerd-quark.o minerd-grso.o -L/c/mingw64/lib -lcurl -lwldap32 -lws2_32 compat/
jansson/libjansson.a -lpthread -lws2_32
minerd-grso.o:grso.c:(.text+0x0): multiple definition of `grsoTransform'
minerd-quark.o:quark.c:(.text+0x1170): first defined here
minerd-grso.o:grso.c:(.text+0x3d0): multiple definition of `grsoOutputTransforma
tion'
minerd-quark.o:quark.c:(.text+0x7d0): first defined here
minerd-grso.o:grso.c:(.rdata+0x0): multiple definition of `grsoT7'
minerd-quark.o:quark.c:(.rdata+0x70): first defined here
minerd-grso.o:grso.c:(.rdata+0x800): multiple definition of `grsoT6'
minerd-quark.o:quark.c:(.rdata+0x870): first defined here
minerd-grso.o:grso.c:(.rdata+0x1000): multiple definition of `grsoT5'
minerd-quark.o:quark.c:(.rdata+0x1070): first defined here
minerd-grso.o:grso.c:(.rdata+0x1800): multiple definition of `grsoT4'
minerd-quark.o:quark.c:(.rdata+0x1870): first defined here
minerd-grso.o:grso.c:(.rdata+0x2000): multiple definition of `grsoT3'
minerd-quark.o:quark.c:(.rdata+0x2070): first defined here
minerd-grso.o:grso.c:(.rdata+0x2800): multiple definition of `grsoT2'
minerd-quark.o:quark.c:(.rdata+0x2870): first defined here
minerd-grso.o:grso.c:(.rdata+0x3000): multiple definition of `grsoT1'
minerd-quark.o:quark.c:(.rdata+0x3070): first defined here
minerd-grso.o:grso.c:(.rdata+0x3800): multiple definition of `grsoT0'
minerd-quark.o:quark.c:(.rdata+0x3870): first defined here
collect2.exe: error: ld returned 1 exit status
make[2]: *** [minerd.exe] Error 1
make[2]: Leaving directory `/c/code/quarkminer'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/c/code/quarkminer'
make: *** [all] Error 2
make all-recursive
make[1]: Entering directory `/c/code/quarkminer'
Making all in compat
make[2]: Entering directory `/c/code/quarkminer/compat'
Making all in jansson
make[3]: Entering directory `/c/code/quarkminer/compat/jansson'
make[3]: Nothing to be done for `all'.
make[3]: Leaving directory `/c/code/quarkminer/compat/jansson'
make[3]: Entering directory `/c/code/quarkminer/compat'
make[3]: Nothing to be done for `all-am'.
make[3]: Leaving directory `/c/code/quarkminer/compat'
make[2]: Leaving directory `/c/code/quarkminer/compat'
make[2]: Entering directory `/c/code/quarkminer'
x86_64-w64-mingw32-gcc -std=gnu99 -DHAVE_CONFIG_H -I. -fno-strict-aliasing -I./
compat/jansson -I/c/mingw64/include -msse4.1 -O3 -MT minerd-quark.o -MD -MP -M
F .deps/minerd-quark.Tpo -c -o minerd-quark.o `test -f 'quark.c' || echo './'`qu
ark.c
quark.c: In function 'quarkhash':
quark.c:95:13: warning: assignment discards 'const' qualifier from pointer targe
t type [enabled by default]
quark.c:124:13: warning: right shift count >= width of type [enabled by default]
quark.c:124:13: warning: right shift count >= width of type [enabled by default]
quark.c:124:13: warning: right shift count >= width of type [enabled by default]
quark.c:124:13: warning: right shift count >= width of type [enabled by default]
mv -f .deps/minerd-quark.Tpo .deps/minerd-quark.Po
x86_64-w64-mingw32-gcc -std=gnu99 -msse4.1 -O3 -o minerd.exe minerd-cpu-miner
.o minerd-util.o minerd-sha2.o minerd-sha2-arm.o minerd-sha2-x86.o minerd-sha2-x
64.o minerd-scrypt.o minerd-scrypt-arm.o minerd-scrypt-x86.o minerd-scrypt-x64.o
minerd-quark.o minerd-grso.o -L/c/mingw64/lib -lcurl -lwldap32 -lws2_32 compat/
jansson/libjansson.a -lpthread -lws2_32
minerd-grso.o:grso.c:(.text+0x0): multiple definition of `grsoTransform'
minerd-quark.o:quark.c:(.text+0x1170): first defined here
minerd-grso.o:grso.c:(.text+0x3d0): multiple definition of `grsoOutputTransforma
tion'
minerd-quark.o:quark.c:(.text+0x7d0): first defined here
minerd-grso.o:grso.c:(.rdata+0x0): multiple definition of `grsoT7'
minerd-quark.o:quark.c:(.rdata+0x70): first defined here
minerd-grso.o:grso.c:(.rdata+0x800): multiple definition of `grsoT6'
minerd-quark.o:quark.c:(.rdata+0x870): first defined here
minerd-grso.o:grso.c:(.rdata+0x1000): multiple definition of `grsoT5'
minerd-quark.o:quark.c:(.rdata+0x1070): first defined here
minerd-grso.o:grso.c:(.rdata+0x1800): multiple definition of `grsoT4'
minerd-quark.o:quark.c:(.rdata+0x1870): first defined here
minerd-grso.o:grso.c:(.rdata+0x2000): multiple definition of `grsoT3'
minerd-quark.o:quark.c:(.rdata+0x2070): first defined here
minerd-grso.o:grso.c:(.rdata+0x2800): multiple definition of `grsoT2'
minerd-quark.o:quark.c:(.rdata+0x2870): first defined here
minerd-grso.o:grso.c:(.rdata+0x3000): multiple definition of `grsoT1'
minerd-quark.o:quark.c:(.rdata+0x3070): first defined here
minerd-grso.o:grso.c:(.rdata+0x3800): multiple definition of `grsoT0'
minerd-quark.o:quark.c:(.rdata+0x3870): first defined here
collect2.exe: error: ld returned 1 exit status
make[2]: *** [minerd.exe] Error 1
make[2]: Leaving directory `/c/code/quarkminer'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/c/code/quarkminer'
make: *** [all] Error 2
Jump to: