similar to: Asic-technologies.com

Asic-technologies.com 9.3-9.9 GHash/sec 6 Board (has 48 chips) - 30 BTC - $3000 USD This unit will make: Coins per 24h at these conditions 0.2965 BTC Revenue per day29.08 USD Each module board uses about 31 Watts of power. Mining board's supplied , Case, power supply , On-board heat sink , USB connectors. Ready assembled All the boards are linked together , With one main controller. Easy to

Asic-technologies.com 9.3-9.9 GHash/sec 6 Board (has 48 chips) - 30 BTC - $3000 USD This unit will make: Coins per 24h at these conditions 0.2965 BTC Revenue per day29.08 USD Each module board uses about 31 Watts of power. Mining board's supplied , Case, power supply , On-board heat sink , USB connectors. Ready assembled All the boards are linked together , With one main controller. Easy to

For those interested I have a working spec file for Bitcoin 0.12.0 https://github.com/AliceWonderMiscreations/bitcoin/blob/master/contrib/rpm/bitcoin.spec I believe the only BuildRequires that isn't in CentOS/EPEL is miniupnpc-devel but that's trivial to build as well. With Bitcoin 0.12.0 the ECC stuff that Red Hat ripped out of OpenSSL doesn't matter anymore. -=- That spec file

Alice Wonder wrote: > For those interested I have a working spec file for Bitcoin 0.12.0 > > https://github.com/AliceWonderMiscreations/bitcoin/blob/master/contrib/rpm/bitcoin.spec > > I believe the only BuildRequires that isn't in CentOS/EPEL is > miniupnpc-devel but that's trivial to build as well. > > With Bitcoin 0.12.0 the ECC stuff that Red Hat ripped out of

Alice Wonder wrote: > On 02/24/2016 06:04 AM, m.roth at 5-cent.us wrote: >> Alice Wonder wrote: >>> For those interested I have a working spec file for Bitcoin 0.12.0 >>> >>> https://github.com/AliceWonderMiscreations/bitcoin/blob/master/contrib/rpm/bitcoin.spec >>> >>> I believe the only BuildRequires that isn't in CentOS/EPEL is

On 02/24/2016 06:06 AM, Alice Wonder wrote: > On 02/24/2016 06:04 AM, m.roth at 5-cent.us wrote: >> Alice Wonder wrote: >>> For those interested I have a working spec file for Bitcoin 0.12.0 >>> >>> https://github.com/AliceWonderMiscreations/bitcoin/blob/master/contrib/rpm/bitcoin.spec >>> >>> >>> I believe the only BuildRequires that

On 02/24/2016 06:04 AM, m.roth at 5-cent.us wrote: > Alice Wonder wrote: >> For those interested I have a working spec file for Bitcoin 0.12.0 >> >> https://github.com/AliceWonderMiscreations/bitcoin/blob/master/contrib/rpm/bitcoin.spec >> >> I believe the only BuildRequires that isn't in CentOS/EPEL is >> miniupnpc-devel but that's trivial to build

I understand your point. I was just offering a bitcoin spec file for those who wanted it, no politics in that post, and was met with resistance I suppose I shouldn't have responded to. No rants about the fiat banking system in my original post. Bitcoin building on CentOS without needing an alternate TLS library installed is new, so really that is all I wanted to do was provide a well

Dear all, Considering this simple example of hexbinplot: mixdata <- data.frame(x = c(rnorm(5000), rnorm(5000,4,1.5)), y = c(rnorm(5000), rnorm(5000,2,3)), a = gl(2, 5000)) fig <- hexbinplot(y ~ x | a, mixdata) print(fig) update(fig, colramp = BTC) produces a bad (non-updated) legend. Compare it with: hexbinplot(y ~ x | a, mixdata, colramp = BTC) What

Hello to everybody,   I seem to be in struggle with the websockets in R. I wanted to download the streaming data from the BitCoin exchange MtGox directly to R, but R cannot establish the connection. The websocket specs are defined as: * Host: websocket.mtgox.com or socketio.mtgox.com * Port: 80 or 443 ( ssl ) * Namespace: /mtgox (Including beginning slash) url for more

On Fri, Jan 19, 2018 at 12:30 PM Andrew Kelley <superjoe30 at gmail.com> wrote: > Zachary, > > Do you generally recommend using -mllvm -emit-codeview-ghash-section and > /DEBUG:GHASH when linking for Windows? > I definitely want you to try it out and let me know how it goes :) It's behind the undocumented -emit-codeview-ghash-section for now until we have some more

With this post, I run the risk of causing more of the thing that I speak against. I still think it's important to say it. CentOS mailing list is a technical forum. It is not a political forum. Just reading a thread on bitcoins and the entire thread quickly turned into a political thread with people bitching about everything from Chase Bank to the Russians, and that's just crap.

Zachary, Do you generally recommend using -mllvm -emit-codeview-ghash-section and /DEBUG:GHASH when linking for Windows? On Fri, Jan 19, 2018 at 3:17 PM, Zachary Turner via llvm-dev < llvm-dev at lists.llvm.org> wrote: > -lldb-dev, +llvm-dev > > lldb-dev is specifically for the llvm debugger, and llvm-dev is for > everything else (including lld) > > Did you compile the

Hi, I'm having lots of difficulties with BCM5719, which is the default network card of HP Proliant DL 360 G8 servers. I can get a few ping replies before I get a couple of these: bge0: watchdog timeout -- resetting bge0: watchdog timeout -- resetting Then everything hangs. Can not log in using ssh.

Ok I went for kind of middle ground solution, I patch in the obj files, but as adding a new section didn't seem to work, I add a "shadow" section, by editing the pointer to line number and the virtual size on the .debug$T section. Although technically broken, both link.exe and lld-link.exe don't seem to mind the alterations and as the shadow .debug$H is not really a section

This part is only for objects with /Z7 debug information in them right? I think most of the third parties are either: .lib/obj without debug information, the same with information on pdb files. Rewriting all .lib/.obj with /Z7 information seems doable with a small python script, the pdb one is going to be more work, but I always wanted to know how a pdb file is structured so "fun" times

Hmm, ok. In that case let me try again without my local changes. Maybe they are getting in the way :-/ On Fri, Jan 26, 2018 at 9:51 AM Leonardo Santagada <santagada at gmail.com> wrote: > it is identical to me... wierd. > > On Fri, Jan 26, 2018 at 6:49 PM, Zachary Turner <zturner at google.com> > wrote: > >> (Ignore the fact that my hashes are 8 byte in the

Hello everyone -- I am stumped on this issue, mostly because I'm not quite sure if it's behaving correctly or not. I believe this used to work and right now I'm not quite sure why it's no longer doing so and how to fix it (if possible). I suspect it is because of my recent update of the OS and Samba version. When users are trying to follow a symlink that goes to a different

I cleaned up my tests and figured that the obj file generated with problems was only with msvc 2015, so trying again with msvc 2017 I get: lld-link: 4s lld-link /debug: 1m30s and ~20gb of ram lld-link /debug:ghash: 59s and ~20gb of ram link: 13s link /debug:fastlink: 43s and 1gb of ram link specialpdb: 1m10s and 4gb of ram link /debug: 9m16s min and >14gb of ram link incremental: 8s when it

Look for this code in lld/coff/pdb.cpp if (Config->DebugGHashes) { ArrayRef<GloballyHashedType> Hashes; std::vector<GloballyHashedType> OwnedHashes; if (Optional<ArrayRef<uint8_t>> DebugH = getDebugH(File)) Hashes = getHashesFromDebugH(*DebugH); else { OwnedHashes = GloballyHashedType::hashTypes(Types); Hashes = OwnedHashes; } In the else block there, add a log