Topic: OFFICIAL CGMINER mining software thread for linux/win/osx/mips/arm/r-pi 4.11.0 - page 825. (Read 5806004 times)
July 24, 2011, 09:23:15 PM
In your distribution's repository, not on your computer...
July 24, 2011, 09:01:21 PM
The file you're missing is:
/usr/share/aclocal/libcurl.m4
on my distro that's in:
libcurl4-openssl-dev
So, unless you need to refresh your configure after installing a new package, you need to find how to search for the libcurl.m4 file in your distribution's repository.
/usr/share/aclocal/libcurl.m4
on my distro that's in:
libcurl4-openssl-dev
So, unless you need to refresh your configure after installing a new package, you need to find how to search for the libcurl.m4 file in your distribution's repository.
July 24, 2011, 08:54:16 PM
1st up, you're missing libcurl dev
2nd, your GCC is so old it doesn't support "-march=native" so remove that
2nd, your GCC is so old it doesn't support "-march=native" so remove that
your proposal is I remove gcc?
July 24, 2011, 08:50:21 PM
1st up, you're missing libcurl dev
2nd, your GCC is so old it doesn't support "-march=native" so remove that
2nd, your GCC is so old it doesn't support "-march=native" so remove that
July 24, 2011, 08:30:39 PM
Yes, preventative... nod nod nod...
Nod furiously.
Nod furiously.
July 24, 2011, 08:28:49 PM
I wasn't trying to start a distro flamewar... I was just pointing out "Much of the world." is an exaggeration to say the least...
I was just sharing an experience. So were there flames posted and deleted already, or was that a preventative comment? I mean 
CENTOS ROCKS!!! GRRR 
July 24, 2011, 08:24:00 PM
I wasn't trying to start a distro flamewar... I was just pointing out "Much of the world." is an exaggeration to say the least...
July 24, 2011, 08:21:51 PM
I started out trying to use CentOS before switching to F15 after I decided that manually compiling every component and half of the compilers to get pretty much any of the miners working wasn't worth the hassle and was going to lead to a broken installation anyway. Fortunately, I'm not trying to do anything else with the machine I am running Linux on at the moment, but anyone who is mining on the side might have good reasons to run CentOS.
my poclbm has been running under centos for a month on three machines with no issues at all. I only use the machines to mine. I find centos rock solid.
July 24, 2011, 08:05:15 PM
I think you grossly overestimate how many people are using centos 
Anyway I've committed a fix to the git tree which prevents using just the sockopt function if the version of curl is too old. This should fix it building on older curls.
I started out trying to use CentOS before switching to F15 after I decided that manually compiling every component and half of the compilers to get pretty much any of the miners working wasn't worth the hassle and was going to lead to a broken installation anyway. Fortunately, I'm not trying to do anything else with the machine I am running Linux on at the moment, but anyone who is mining on the side might have good reasons to run CentOS. Anyway I've committed a fix to the git tree which prevents using just the sockopt function if the version of curl is too old. This should fix it building on older curls.
July 24, 2011, 08:00:44 PM
but I don't really understand if anyone is interested in RHEL5 builds other than me.
Much of the world. If this doesn't work on Centos, it's worthless. Kinda like coming up
with windows only mining software
To the author, this is what was required to build poclbm under centos:
http://forum.bitcoin.org/?topic=7534.0
RedHat and Centos uses older (proven stable) versions of their software.
Unfortunatly I, like zaytsev, am stuck using poclbm atm.
* Viceroy sadly drops his head and walks away
Anyway I've committed a fix to the git tree which prevents using just the sockopt function if the version of curl is too old. This should fix it building on older curls.
July 24, 2011, 04:44:54 PM
wellp,
I done did downloaded centos 6, so I guess it's about time to install it I reckon.
yeaaaap
I done did downloaded centos 6, so I guess it's about time to install it I reckon.
yeaaaap
* Viceroy chews some hay
July 24, 2011, 03:26:21 PM
what's the fix?
There is no fix, I just compile it statically against the curl from RHEL6.
I ain't pickin up your precompiled code
I am making the SRPM available, feel free to rebuild it yourself if you want.
July 24, 2011, 03:13:05 PM
what's the fix?
I ain't pickin up your precompiled code
* Viceroy picks his head up and starts to listen again
I ain't pickin up your precompiled code
July 24, 2011, 02:23:30 PM
The problem with this idea is that network-using static libraries are not supported by glibc.
Errr... what?
Adding a --with-libcurl=/usr/local/src/newcurl option to configure is reasonably simple.
This isn't even needed, because curl gets picked up by pkgconfig (which actually doesn't seem to work, it's rather curl-config that does the trick).
Viceroy, I have tried my static curl twist and it worked, updated RPMs here. You know which way to throw your coins ;-)
July 24, 2011, 01:41:28 PM
With version 1.4.0 and 1.4.1, I have some trouble connecting to the rpc server.
cgminer exists with code:
I tried it several times with the same starting parameters:
./cgminer -o http://uswest.btcguild.com:8332 -u myusername -p mypassword -w 256 -I 8 --verbose
and got only 1 connect where only the first gpu was starting to work.
I tested 1.4.0 and 1.4.1 precompiled version for ubuntu with the same behavior.
Version 1.3.1 is working fine.
Got 14.42 shares per minute
with
2 * 5850 @ 900,300
1 * 5850 @ 820,300
cgminer exists with code:
Code:
No pools active! Exiting.
I tried it several times with the same starting parameters:
./cgminer -o http://uswest.btcguild.com:8332 -u myusername -p mypassword -w 256 -I 8 --verbose
and got only 1 connect where only the first gpu was starting to work.
I tested 1.4.0 and 1.4.1 precompiled version for ubuntu with the same behavior.
Version 1.3.1 is working fine.
Got 14.42 shares per minute
with
2 * 5850 @ 900,300
1 * 5850 @ 820,300
July 24, 2011, 01:35:52 PM
Well, that's not a fix as it won't make it work on RHEL5, that's just making the failure message more informative.
Good thing IMHO. configure.ac is supposed to test for minimum features, after all.Quote
I guess I can try compiling static builds against newer curl, but I don't really understand if anyone is interested in RHEL5 builds other than me.
The problem with this idea is that network-using static libraries are not supported by glibc.You should be able to build your own version of "new" libcurl and compile+link against that.
Adding a --with-libcurl=/usr/local/src/newcurl option to configure is reasonably simple.
July 24, 2011, 12:46:13 PM
but I don't really understand if anyone is interested in RHEL5 builds other than me.
Much of the world. If this doesn't work on Centos, it's worthless. Kinda like coming up
with windows only mining software
To the author, this is what was required to build poclbm under centos:
http://forum.bitcoin.org/?topic=7534.0
RedHat and Centos uses older (proven stable) versions of their software.
Unfortunatly I, like zaytsev, am stuck using poclbm atm.
* Viceroy sadly drops his head and walks away
July 24, 2011, 12:25:16 PM
Should be straightforward to implement.
Well, that's not a fix as it won't make it work on RHEL5, that's just making the failure message more informative. I guess I can try compiling static builds against newer curl, but I don't really understand if anyone is interested in RHEL5 builds other than me.
July 24, 2011, 12:14:18 PM
As I said the curl version is too old, there is no fix unless ck makes longpoll optional / figures out how to implement this functionality only using old curl's features.
The fix is to add a check to configure.ac, for "new curl" (i.e. version and/or data type and/or library call) and to refuse to continue if that's not present.Should be straightforward to implement.
July 24, 2011, 12:08:31 PM
Version 1.4.1 will not compile on CENTOS, same error as below. What is the fix???
As I said the curl version is too old, there is no fix unless ck makes longpoll optional / figures out how to implement this functionality only using old curl's features.
Jump to: