 Show Posts
|
|
Pages: [1]
|
|
Are there no Mac bitcoin devs who read this forum? I've mailed everybody listed in build-osx.md but the only one who replied says he's out of touch with the project now and that I should ask here.
The OSX build docs for bitcoind are quite thorough but I feel more detail is needed within the readme-qt.rst file for those wanting to build bitcoin-qt on OSX.
Thanks for your suggestions re openssl tvbcof, but it doesn't address my questions re required versions of Xcode and Qt required to build bitcoin-qt, what with Xcode having nothing to do with freebsd, being OSX specific. The docs state that the Mac version of bitcoin-qt is built on 10.6 but they could potentially be using xcode 4.2 which isn't available to non-paying Apple devs, hence I'm using xcode 3.2.x. Then there is the question of what version of Qt should I be using. I presume I have to use the 4.x series but maybe I should be using 4.7.x vs 4.8.x?
|
|
|
|
I've already successfully built bitcoind for OSX but I'm having probs compiling bitcoin-qt under OSX so I'm hoping this forum could give me some tips. I used xcode for the first time today and I'm only just beginning to learn (Obj) C (++) so please excuse my noobiness! I'm doing this to learn how to build Qt apps under OSX as well as to understand bitcoin a bit better. I know I could just download an existing Mac build if I wanted. The first thing that may cause a prob for building the qt wallet is that my OSX install is still using the included openssl instead of the one I installed from homebrew. build-osx.md, included with the bitcoin source, says that I should run: brew link openssl --force but after running again, I can see I'm still defaulting to the older version of openssl. I've not yet tried just manually replacing the openssl binary or moving the older one and linking to the newer. I presume that could work but it'd be better if I could get the previous command to work or maybe there's another, cleaner way that would also work? What are the minimum or recommended versions of Xcode and Qt required to build bitcoin-qt under OSX? I'm trying to build bitcoin-qt under OSX 10.6.8 using Xcode 3.2.6, Qt 4.8.4 (downloaded from qt-project.org) and I used homebrew to build all the other deps. I don't suppose I need to build Qt from source (or homebrew) too do I? I tried installing Qt 5.2 first but I got a couple of errors during installation so maybe it doesn't support Snow Leopard any more? Xcode 3.2.6 is the latest I can get without a paid dev account, it seems. Finally, the docs say there are issues compiling bitcoin for 64bit SL. Does that mean I have to run OSX in legacy/32bit mode to get it to compile or is choosing a 32bit target under Xcode enough? I'd be creatng a universal binary ideally as thats what I compiled everything (boost, openssl, bdb, upnp) else as so far. Thanks for your help! |
|
|
|
|
That fixed it - thanks Mr Wools!
|
|
|
|
|
nwoolls:
If its the CoinChoose.com prob thats stopping me opening MM, can I switch to CoinWarz API with a command line argument or maybe by editing one of the config files? Changing it from the settings menu isn't an option as I don't get that far.
|
|
|
|
I logged into our mining server today and MM was closed. I had been running 2.3.5 so I updated to 2.4.0 but it didn't help - I got this same error message and MM does not load. I tried moving ~/.config/MultiMiner to try and reset it but still no go! MM will not open now! Could not set X locale modifiers
Newtonsoft.Json.JsonReaderException: Unexpected character encountered while parsing value: Y. Path '', line 0, position 0.
at Newtonsoft.Json.JsonTextReader.ParseValue () [0x00000] in <filename unknown>:0
at Newtonsoft.Json.JsonTextReader.ReadInternal () [0x00000] in <filename unknown>:0
at Newtonsoft.Json.JsonTextReader.Read () [0x00000] in <filename unknown>:0
at Newtonsoft.Json.Linq.JArray.Load (Newtonsoft.Json.JsonReader reader) [0x00000] in <filename unknown>:0
at Newtonsoft.Json.Linq.JArray.Parse (System.String json) [0x00000] in <filename unknown>:0
at MultiMiner.CoinChoose.Api.ApiContext.GetCoinInformation (System.String userAgent) [0x00000] in <filename unknown>:0
at MultiMiner.Win.MainForm.RefreshCoinStats () [0x00000] in <filename unknown>:0 This is when running under Debian Jessie w/ mono 3.x, btw |
|
|
|
nwoolls: I thought it would be a mono bug. Great news re your plan to port MM to Qt! I would never usually install mono under Linux as I can't think of a single good, interesting FLOSS project that uses it - except MM! I've heard GUIminer is supposed to work under Linux too as its python / wx-widgets based but I don't think that has any support for restarting zombiefied/suspect mines like MM has. mono has always faced an uphill battle trying to keep apace with .NET and its only got worse for them from what I hear. Most of the leading open source projects (KDE, KDEnlive, qtractor, VLC, k3b, mumble, Virtualbox, bitcoin...) and also a lot of non-free cross-platform apps (Maya, Skype, Google Earth) are using Qt and for many very good reasons. Not in the least being its well documented and that Qt now supports Android and iOS as of v5.2 so there could be a potential merge of MM and Mobileminer? .NET seems to one of the last vestiges of MS lock-in. We don't want or need that sort of shit any more - Qt is the future!  |
|
|
|
Hi nwoolls! Thanks for explaining that! I now have MM mining happily under Debian Jessie / KDE!  Did you look into the port editing crash with mono? I presume it'll be a bug in mono rather than MM if it doesn't happen with Windows .NET. |
|
|
|
|
I have been able to work round that crash by leaving the zero in the port entry box, entering the port then deleting the zero so there is always text in the box.
I've added the details of my Bitcoin pool to coin config and I can see my Icarus devices listed in the main window but the start button is greyed out. Why might that be?
Thanks for your help!
|
|
|
|
Hi nwoolls! With MuM 2.3.5 under Deb Jessie x64, the following gets dumped to the terminal as soon as I delete the 0 in the port input box of the coin config window: System.Exception: is not a valid value for Int32. ---> System.FormatException: Input string was not in the correct format
at System.Int32.Parse (System.String s, NumberStyles style, IFormatProvider provider) [0x00000] in <filename unknown>:0
at System.ComponentModel.Int32Converter.ConvertFromString (System.String value, System.Globalization.NumberFormatInfo format) [0x00000] in <filename unknown>:0
at System.ComponentModel.BaseNumberConverter.ConvertFrom (ITypeDescriptorContext context, System.Globalization.CultureInfo culture, System.Object value) [0x00000] in <filename unknown>:0
--- End of inner exception stack trace ---
at System.ComponentModel.BaseNumberConverter.ConvertFrom (ITypeDescriptorContext context, System.Globalization.CultureInfo culture, System.Object value) [0x00000] in <filename unknown>:0
at System.ComponentModel.TypeConverter.ConvertFrom (System.Object o) [0x00000] in <filename unknown>:0
at System.Windows.Forms.Binding.ConvertData (System.Object data, System.Type data_type) [0x00000] in <filename unknown>:0
at System.Windows.Forms.Binding.ParseData (System.Object data, System.Type data_type) [0x00000] in <filename unknown>:0
at System.Windows.Forms.Binding.SetPropertyValue (System.Object data) [0x00000] in <filename unknown>:0
at System.Windows.Forms.Binding.PullData (Boolean force) [0x00000] in <filename unknown>:0 If there is anything else you need to know to fix this, let me know please! |
|
|
|
|
Hi nwoolls!
I've not been able to get Multiminer 2.3.4 mining under Debian Jessie amd64. I've installed mono-complete (v3.0.6 I think) and bfgminer 3.8.1 from the Debian repos. I open the 'configure coins' window, add Bitcoin and then as soon as I delete '0' from the ports input box to input the port for the pool I use, MuM segfaults.
The main reason I'd like to use MuM is that it seems to support restarting of suspect mines. I have a load of Icarus block erupters attached to my mining box and, under cgminer at least, they often become zombies after a few days then I need to manually restart cgminer. I've not tried them with bfgminer yet but I presume this the sort of problem MuM's 'restart suspect mines' option is designed to get around?
Also, I've seen a screenshot of MuM where it appeared to be using cgminer instead of bfgminer. Is/was that an option or is it strictly for use with bfgminer?
Thanks for your help!
|
|
|
|
|
Hi BTCtalk forum!
I posted most of the questions below in the Newbie forum yesterday as that was the only place I was allowed to post but none of my questions got answered so I'm re-posting the here, which is where I wanted to post them originally.
I've recently set up a mine running cgminer (3.8.2) under Debian (Jessie amd64) that has 30 Icarus USB block erupters attached. Every 2 or 3 days the erupters get ZOMBIEfied and I need to manually restart cgminer, then they run fine for another couple of days or so. Not ideal!
This situation has given rise to the following questions:
1 - Is ANUBIS capable of detecting and restarting cgminer for my Icarus mines when they get zombiefied?
2 - There seems to be at least 3 different forks of ANUBIS already. Is pshep's the best?
3 - What are ANUBIS's dependency version requirements (cgminer version, PHP, Mysql etc.)
I've already filed a ticket against ANUBIS on github before I've even tried it as the README doesn't explain what ANUBIS is or what features it has. I would also like to see the OP of this thread get updated to address these questions so people don't have to read 18+ pages of posts just to find out what ANUBIS can do!
Thanks for your help!
|
|
|
|
just set a cronjob that kills of cgminer and restarts it once a day?
Not the most elegant solution that but if ANUBIS can't detect and restart (cgminer for) zombie'fied ASICs and if cgwatcher doesn't work under wine then thats prob what I'll end up doing. I'd only use cgwatcher if it could work with the Linux version of cgminer though - I wouldn't want to run the actual mining software under wine too. It usually can last a day or two before cgminer needs to be restarted but I've also seen 'the attack of the ZOMBIE ASICs' come after only a few hours too. Running a cron job to kill and restart cgminer every couple of hours seems too much. |
|
|
|
|
Hi BTCtalk forum!
I've recently set up a mining rig running cgminer (3.8.2) under Debian (Jessie amd64) that has 30 Icarus USB block erupters attached. Every 2 or 3 days the erupters get ZOMBIEfied and I need to manually restart cgminer, then they run fine for another couple of days or so. Not ideal!
This situation has given rise to my following questions:
1 - I'm still using cgminer 3.8.2 simply because its the version currently in the Jessie repos. Might 3.10.0 be more reliable for use with ASICs?
2 - I've not tried bfgminer or any other Linux mining software - might I get better results with bfgminer or something else?
3 - I'm under the impression, due to the existence of cgwatcher/ANUBIS etc, that none of these apps (cgminer, bfgminer) feature integrated failover restarting/monitoring yet? Why not? Is it planned?
4 - Whats the best mine monitoring app that helps prevent downtime that works under Linux? I've only really heard people recommend ANUBIS. Is there nothing else?
5 - Is ANUBIS capable of detecting and restarting cgminer for my Icarus mines when they get zombiefied?
6 - There seems to be at least 3 different forks of ANUBIS already. Is pshep's the best?
7 - What are ANUBIS's dependency version requirements (cgminer version, PHP, Mysql etc.)
I've already filed a ticket against ANUBIS on github before I've even tried it as the README doesn't explain what ANUBIS is or what features it has - hence my fat wad of monitoring questions!
Thanks for your help!
|
|
|
|
|
