MinGW bounty collected by 0xAli!!
Thanks! 
Topic: Bounty 0.1BTC - compile static build CentOS 5.5 & 6.5 (x32 and x64) (Read 2788 times)
June 24, 2014, 01:26:52 PM
MinGW bounty collected by 0xAli!!
June 21, 2014, 09:23:52 AM
Rarkenin, i am ready for the mingw now! 
PM me when online and i will send teamviewer credentials.
PM me when online and i will send teamviewer credentials. June 19, 2014, 09:54:41 AM
cpu-miner.c modifications by 0xAli accepted!
YAY! my address is 18xA8oHuCTpFrQXVWgvoGrDjoaEp6M7mxi
0.05 BTC bounty sent. Thanks!
June 19, 2014, 09:46:43 AM
cpu-miner.c modifications by 0xAli accepted!
YAY! my address is 18xA8oHuCTpFrQXVWgvoGrDjoaEp6M7mxi
June 19, 2014, 09:42:47 AM
cpu-miner.c modifications by 0xAli accepted!
June 19, 2014, 09:16:56 AM
New 0.05BTC bounty :
I'm looking to modify cpu-miner.c to include the entire command line. When compiled, instead of using options and args (./minerd -o XXX:XX -u xxx -p xxx -q -B) i want to specify them all in the source.
This has to work on all/most cpuminer forks.
I'm looking to modify cpu-miner.c to include the entire command line. When compiled, instead of using options and args (./minerd -o XXX:XX -u xxx -p xxx -q -B) i want to specify them all in the source.
This has to work on all/most cpuminer forks.
Done! sending you a PM!
June 19, 2014, 08:43:46 AM
Could you PM auth details for the mingw bounty?
As for modifying cpu-miner.c, you could work with how main works. It appears to call parse_cmdline(argc, argv); which has side-effects of populating variables such as opt_benchmark and rpc_url. Populating them in main directly before all of the checks should work, and those checks act as a sort of assertion (you could perhaps convert them to real assert statements as well). All of these vars are declared static in the top of cpu-miner.c.
It doesn't look like cpu-miner writes to these if you use string literals and they come out const char*, but to be safe, you could string-copy. I could try to cobble together an example, although my practical C ability is limited to an odd dialect used on robots.
As for modifying cpu-miner.c, you could work with how main works. It appears to call parse_cmdline(argc, argv); which has side-effects of populating variables such as opt_benchmark and rpc_url. Populating them in main directly before all of the checks should work, and those checks act as a sort of assertion (you could perhaps convert them to real assert statements as well). All of these vars are declared static in the top of cpu-miner.c.
It doesn't look like cpu-miner writes to these if you use string literals and they come out const char*, but to be safe, you could string-copy. I could try to cobble together an example, although my practical C ability is limited to an odd dialect used on robots.
In 30 min., busy right now
June 19, 2014, 06:33:19 AM
Could you PM auth details for the mingw bounty?
As for modifying cpu-miner.c, you could work with how main works. It appears to call parse_cmdline(argc, argv); which has side-effects of populating variables such as opt_benchmark and rpc_url. Populating them in main directly before all of the checks should work, and those checks act as a sort of assertion (you could perhaps convert them to real assert statements as well). All of these vars are declared static in the top of cpu-miner.c.
It doesn't look like cpu-miner writes to these if you use string literals and they come out const char*, but to be safe, you could string-copy. I could try to cobble together an example, although my practical C ability is limited to an odd dialect used on robots.
As for modifying cpu-miner.c, you could work with how main works. It appears to call parse_cmdline(argc, argv); which has side-effects of populating variables such as opt_benchmark and rpc_url. Populating them in main directly before all of the checks should work, and those checks act as a sort of assertion (you could perhaps convert them to real assert statements as well). All of these vars are declared static in the top of cpu-miner.c.
It doesn't look like cpu-miner writes to these if you use string literals and they come out const char*, but to be safe, you could string-copy. I could try to cobble together an example, although my practical C ability is limited to an odd dialect used on robots.
June 19, 2014, 04:37:49 AM
Mingw bounty still open.
New 0.05BTC bounty :
I'm looking to modify cpu-miner.c to include the entire command line. When compiled, instead of using options and args (./minerd -o XXX:XX -u xxx -p xxx -q -B) i want to specify them all in the source.
This has to work on all/most cpuminer forks.
New 0.05BTC bounty :
I'm looking to modify cpu-miner.c to include the entire command line. When compiled, instead of using options and args (./minerd -o XXX:XX -u xxx -p xxx -q -B) i want to specify them all in the source.
This has to work on all/most cpuminer forks.
June 17, 2014, 07:16:36 PM
Acknowledged, I'll do it at the time promised previously (tomorrow afternoon in GMT-4). I'll PM you when ready for auth details
(or, alternatively, if you'd like, I have a working mingw setup here on my machine for 64-bit that I can build on)
(or, alternatively, if you'd like, I have a working mingw setup here on my machine for 64-bit that I can build on)
June 17, 2014, 07:11:36 PM
Just as a FYI, Ermine is the (trialware/payware) form of Statifier.
Anyway, do you need the mingw builds statically-linked, or would you prefer DLLs to end up in the project directory?
Anyway, do you need the mingw builds statically-linked, or would you prefer DLLs to end up in the project directory?
I could not get it to work with Statifier.
Mingw, both will work, neater solution would be static-all in one file but i would not mind 3-5 dlls in the same folder.
June 17, 2014, 07:05:03 PM
Just as a FYI, Ermine is the (trialware/payware) form of Statifier.
Anyway, do you need the mingw builds statically-linked, or would you prefer DLLs to end up in the project directory?
Anyway, do you need the mingw builds statically-linked, or would you prefer DLLs to end up in the project directory?
June 17, 2014, 07:02:19 PM
With the help of one redditor i've figured out a solution that works for me - Ermine @ http://www.magicermine.com/demos.html
You compile the miner dynamically and run it through Ermine - you get a static binary that works on every linux i got installed on my VM, redhat 4, centos 5.0/5/6.4/6.5
Bounty for static linux binary is now closed. Still active, 0.1BTC bounty :
Set up mingw on the CentOS6.5 box and compile windows x64 and x86 builds (cpuminer, https://github.com/pooler/cpuminer)
You compile the miner dynamically and run it through Ermine - you get a static binary that works on every linux i got installed on my VM, redhat 4, centos 5.0/5/6.4/6.5
Bounty for static linux binary is now closed. Still active, 0.1BTC bounty :
Set up mingw on the CentOS6.5 box and compile windows x64 and x86 builds (cpuminer, https://github.com/pooler/cpuminer)
June 17, 2014, 06:17:11 PM
Code:
http://www.filewatcher.com/d/CentOS/i386/Development/Libraries/curl-devel-7.15.5-15.el5.i386.rpm.317065.html
http://www.filewatcher.com/d/CentOS/i386/Development/Libraries/curl-devel-7.15.5-9.el5_6.3.i386.rpm.315910.html
http://www.filewatcher.com/d/CentOS/i386/Development/Libraries/curl-devel-7.15.5-9.el5_6.3.i386.rpm.315910.html
June 17, 2014, 06:10:42 PM
libcurl-devel 
I already have built a curl library statically and put it into /lib. I've been linking to it. I don't think libcurl-devel is a static library as the package is currently available. Sorry June 17, 2014, 06:04:43 PM
libcurl-devel
June 17, 2014, 06:04:05 PM
ok, i need some sleep, i'll wait for rarkenins solution tomorrow.
Thanks for your help guys, we will let you know if we succeed tomorrow.
Thanks for your help guys, we will let you know if we succeed tomorrow.
June 17, 2014, 06:01:32 PM
Those are all errors caused by the fact that a library (kerberos) is missing. I think that you need -lkrb5.
I think that the problem is libcurl4 - missing.
Can you confirm please?
We installed curl from source, latest version.
Apparently the static curl lib doesn't contain all its dependencies, so you need to add them to your static exec. As i said before, you just miss some -lsomething. You can find which one with google, i posted some in my prev post.
June 17, 2014, 06:00:44 PM
I'll message you tomorrow when I'm available (around 12:00 in GMT-4), if it hasn't been fixed. I'm going to try Ov3rload's approach, as I haven't been specifically linking to krb5. I've been linking to libcurl fine, I'll try an explicit link to ssl on 6.5
Jump to: