Quote from: Spoetnik on September 09, 2013, 04:07:16 AM

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..

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

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.

stonefoz

Posts

Merits