MineForeman.com
Legendary
Offline
Activity: 896
Merit: 1000
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
March 08, 2014, 02:18:17 AM Last edit: March 08, 2014, 03:49:51 AM by MineForeman.com |
|
Hi All and Luke, I am having an issue with the API, in particular I am having problems with switchpool (though changing MHS5s to MHS20s in the device output caught me a bit unaware). When you use switchpool the first time it works fine, the second time you use it though it does nothing, unfortunately it does not return anything either to (via the api or miner screen). It seems to just silently fail. To make it worse I just introduced pool switching to the MinePeon status screen. Is anyone else seeing the same? Neil EDIT: Hold off, I think another person might have spotted the problem with switchpool, I will be back ![Wink](https://bitcointalk.org/Smileys/default/wink.gif) .
|
|
|
|
nwoolls
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
March 08, 2014, 03:27:49 AM |
|
I am having an issue with the API, in particular I am having problems with switchpool (though changing MHS5s to MHS20s in the device output caught me a bit unaware).
That change caught me by surprise too. The good news is you can pass in --log XY and then you can always count on the key for current hashrate being constant. While I understand why --log changes the way current hashrate is measured, I'm not sure why that should change its key an an API.
|
MultiMiner: Any Miner, Any Where, on Any Device | Xgminer: Mine with popular miners on Mac OS X
|
|
|
Luke-Jr (OP)
Legendary
Offline
Activity: 2576
Merit: 1186
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
March 08, 2014, 04:03:33 AM |
|
I am having an issue with the API, in particular I am having problems with switchpool (though changing MHS5s to MHS20s in the device output caught me a bit unaware).
That change caught me by surprise too. The good news is you can pass in --log XY and then you can always count on the key for current hashrate being constant. While I understand why --log changes the way current hashrate is measured, I'm not sure why that should change its key an an API. It's one of those things kept for cgminer compatibility (yes, it changes with --log there, too). Perhaps we should mirror it to another constant-named key?
|
|
|
|
nwoolls
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
March 08, 2014, 04:09:55 AM |
|
It's one of those things kept for cgminer compatibility (yes, it changes with --log there, too). Perhaps we should mirror it to another constant-named key?
Ya that's what I assumed - I think having a constant key in there for current hashrate would be a good idea for forward compatibility with this left in there for backwards compatibility.
|
MultiMiner: Any Miner, Any Where, on Any Device | Xgminer: Mine with popular miners on Mac OS X
|
|
|
OleOle
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
March 08, 2014, 04:11:30 PM |
|
Hats off to all you guys who keep BFG at the forefront of development with all the new mining hardware that keeps being introduced ![Smiley](https://bitcointalk.org/Smileys/default/smiley.gif) I remember receiving some Blue Furies a few months back and thinking, "The BFG guys will have something worked out soon," and sure enough within a few days native support in BFG was available - what old schoolers know as 'just in time'. I know you're busy working on a number of projects, one of which is the DualMiner compatibility project, so just wanted to share my appreciation for all your hard work and hoping that I haven't missed anything in the thread as I've a number of DualMiner units sitting on the desk here awaiting BFG compatibility. I hear there's some sort of CGMiner workable solution to get them mining but to be honest I'm not really interested in CGMiner, I run all my miners using BFG and would rather wait a few weeks and have another instance or two of BFG working alongside the BFG instances I have open for my various usb miners already than deal with other mining programs, which in my experience, have been less than suitable for my needs and tended to be far more trouble than they are worth. I've heard some rumour that there's a Multiminer workaround for DualMiner but I'm kinda over the tweak, re-tweak, tweak-ad-nausuem, so I'd prefer to wait until there was more formalised BFG support as it's just not worth the aggravation to me to have any different miners or untested workarounds play havoc with my rig. If I see the lights flashing on my rig and check the hash speed at the pool and all is well, then that's confirmation why I use BFG in the first place. So please let me know if I've missed anything. Thanks folks. ![Smiley](https://bitcointalk.org/Smileys/default/smiley.gif)
|
|
|
|
nwoolls
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
March 08, 2014, 05:44:45 PM |
|
I know you're busy working on a number of projects, one of which is the DualMiner compatibility project, so just wanted to share my appreciation for all your hard work and hoping that I haven't missed anything in the thread as I've a number of DualMiner units sitting on the desk here awaiting BFG compatibility.
Check out this post here: https://bitcointalk.org/index.php?topic=168174.msg5572568#msg5572568That is the DualMiner branch for BFGMiner and is just waiting on another code review before being merged. Should be both feature-complete and stable. I've heard some rumour that there's a Multiminer workaround for DualMiner but I'm kinda over the tweak, re-tweak, tweak-ad-nausuem, so I'd prefer to wait until there was more formalised BFG support as it's just not worth the aggravation to me to have any different miners or untested workarounds play havoc with my rig.
The current version of MultiMiner has DualMiner support. You just need a version of BFGMiner with DualMiner support installed. I'm not sure what the timeline looks like for 4.0. Fairly certain it should be soon. It just got delayed by Luke speaking at a Bitcoin conference and me having some hardware issues at the same time.
|
MultiMiner: Any Miner, Any Where, on Any Device | Xgminer: Mine with popular miners on Mac OS X
|
|
|
demonmaestro
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
March 09, 2014, 02:08:57 AM |
|
I've gotten my hands on some AntMiner U2s but bfgminer is not seeing them. This is on a Raspi. ./bfgminer-3.10.0/bfgminer -S antminer:all -o stratum.myfuckingpool.com:3333 -u demonmaestro_usb -p 1
|
Feel Like Donating? bc1q0v5nfdejapffewu67gft7zw7zsmnfmmkt3lf02 Buy/Sell BitCoin & LiteCoin Click here! | Looking for a great exchange? CoinBase Has you covered.
|
|
|
OleOle
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
March 09, 2014, 03:55:40 AM |
|
I know you're busy working on a number of projects, one of which is the DualMiner compatibility project, so just wanted to share my appreciation for all your hard work and hoping that I haven't missed anything in the thread as I've a number of DualMiner units sitting on the desk here awaiting BFG compatibility.
Check out this post here: https://bitcointalk.org/index.php?topic=168174.msg5572568#msg5572568That is the DualMiner branch for BFGMiner and is just waiting on another code review before being merged. Should be both feature-complete and stable. I've heard some rumour that there's a Multiminer workaround for DualMiner but I'm kinda over the tweak, re-tweak, tweak-ad-nausuem, so I'd prefer to wait until there was more formalised BFG support as it's just not worth the aggravation to me to have any different miners or untested workarounds play havoc with my rig.
The current version of MultiMiner has DualMiner support. You just need a version of BFGMiner with DualMiner support installed. I'm not sure what the timeline looks like for 4.0. Fairly certain it should be soon. It just got delayed by Luke speaking at a Bitcoin conference and me having some hardware issues at the same time. Thanks very much nwools, that's great news, I really appreciate all your help! ![Smiley](https://bitcointalk.org/Smileys/default/smiley.gif)
|
|
|
|
nwoolls
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
March 09, 2014, 07:25:22 AM |
|
The previous driver I linked is for the GridSeed 1-chip device, so far resold by DualMiner. For support for the GridSeed 5-chip devices, if you are feeling crazy you can try this out (Scrypt-only currently): https://github.com/nwoolls/bfgminer/commits/feature/gridseed-supportI give it the It Works For Me(tm) stamp of approval. Run it with -S gridseed:all and specify frequency with --set-device gridseed:clock=freq, e.g. 850 (default is 600). ![](https://ip.bitcointalk.org/?u=http%3A%2F%2Fwww.nwoolls.com%2Fothercontent%2FBFGMiner%2520-%2520GridSeed%25205-Chip.png&t=665&c=4gsoHY4ScIycKw) For OS X users, these should be loaded automatically but in case they aren't: sudo kextload -b com.apple.driver.AppleUSBCDC sudo kextload -b com.apple.driver.AppleUSBCDCACMData SHA2 support will be next followed by dual-algorithm support. If you have some of these and are feeling froggy, feedback is welcome.
|
MultiMiner: Any Miner, Any Where, on Any Device | Xgminer: Mine with popular miners on Mac OS X
|
|
|
lajz99
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
March 09, 2014, 07:32:30 AM |
|
^^ Need a windows compiled version, but I could give it a shot with 5 x 5 chip units. ![Grin](https://bitcointalk.org/Smileys/default/grin.gif)
|
|
|
|
|
lajz99
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
March 09, 2014, 10:31:32 PM |
|
Works for me, any way I can specify COM ports to be used and others to be ignored? Also how to ignore my GPU's? OCL0, OCL1, OCL2
|
|
|
|
nwoolls
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
March 09, 2014, 10:45:31 PM |
|
Works for me, any way I can specify COM ports to be used and others to be ignored? Also how to ignore my GPU's? OCL0, OCL1, OCL2
Awesome - that's great news! Haven't had a chance to play on Windows just yet. To ignore GPUs, pass in: That will prevent any auto-detection. To specify the devices, instead of: use: -S gridseed:/dev/cu.usbmodem3a21 where the bit after the colon is the COM port or path to the device.
|
MultiMiner: Any Miner, Any Where, on Any Device | Xgminer: Mine with popular miners on Mac OS X
|
|
|
lajz99
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
March 09, 2014, 10:51:37 PM |
|
Awesome, works like a charm!
|
|
|
|
darkfriend77
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
March 09, 2014, 11:27:36 PM |
|
Works for me, any way I can specify COM ports to be used and others to be ignored? Also how to ignore my GPU's? OCL0, OCL1, OCL2
Awesome - that's great news! Haven't had a chance to play on Windows just yet. To ignore GPUs, pass in: That will prevent any auto-detection. To specify the devices, instead of: use: -S gridseed:/dev/cu.usbmodem3a21 where the bit after the colon is the COM port or path to the device. Any way to set clock speed of the 5chip gridseed miners? the windows binary looks fine ... except of the clocking ...
|
|
|
|
nwoolls
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
March 09, 2014, 11:31:34 PM |
|
Any way to set clock speed of the 5chip gridseed miners?
the windows binary looks fine ... except of the clocking ...
Run it with -S gridseed:all and specify frequency with --set-device gridseed:clock=freq, e.g. 850 (default is 600).
|
MultiMiner: Any Miner, Any Where, on Any Device | Xgminer: Mine with popular miners on Mac OS X
|
|
|
gigica viteazu`
Sr. Member
![*](https://bitcointalk.org/Themes/custom1/images/star.gif) ![*](https://bitcointalk.org/Themes/custom1/images/star.gif) ![*](https://bitcointalk.org/Themes/custom1/images/star.gif)
Offline
Activity: 458
Merit: 250
beast at work
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
March 10, 2014, 01:17:49 AM |
|
For support for the GridSeed 5-chip devices, if you are feeling crazy you can try this out (Scrypt-only currently): https://github.com/nwoolls/bfgminer/commits/feature/gridseed-supportI give it the It Works For Me(tm) stamp of approval. Run it with -S gridseed:all and specify frequency with --set-device gridseed:clock=freq, e.g. 850 (default is 600). any tips to get this build for arch linux on raspberry pi
|
|
|
|
nwoolls
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
March 10, 2014, 01:31:40 AM |
|
any tips to get this build for arch linux on raspberry pi
Follow the normal Linux instructions for cloning and building. It shouldn't take anything special other than making sure you use my repo and branch: https://github.com/nwoolls/bfgminer/tree/feature/gridseed-supportLet me know if you run into any issues. Would love to hear if it works under the Pi (it should). Haven't had a chance to test that yet.
|
MultiMiner: Any Miner, Any Where, on Any Device | Xgminer: Mine with popular miners on Mac OS X
|
|
|
Cassey
Sr. Member
![*](https://bitcointalk.org/Themes/custom1/images/star.gif) ![*](https://bitcointalk.org/Themes/custom1/images/star.gif) ![*](https://bitcointalk.org/Themes/custom1/images/star.gif)
Offline
Activity: 470
Merit: 250
Better to have 100 friends than 100 rubles
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
March 10, 2014, 03:18:07 AM |
|
I recently have started having some shutdown errors. Program works fine, just generates stuff like what is below when I shutdown via q.
*** Error in `./bfgminer': double free or corruption (out): 0x00000000027a7850 *** ======= Backtrace: ========= /lib64/libc.so.6(+0x7e916)[0x7f2d9c732916] /lib64/libc.so.6(+0x7f6b3)[0x7f2d9c7336b3] ./bfgminer[0x451492] ./bfgminer[0x41644e] ./bfgminer[0x422e99] ./bfgminer[0x4267eb] /lib64/libpthread.so.0(+0x10b10)[0x7f2d9da3fb10] /lib64/libpthread.so.0(pthread_cond_wait+0xcc)[0x7f2d9da3bcfc] ./bfgminer[0x40c3e3] /lib64/libc.so.6(__libc_start_main+0xf5)[0x7f2d9c6d8bf5] ./bfgminer[0x40d4b5] ======= Memory map: ======== 00400000-004b4000 r-xp 00000000 fd:03 2448 /home/litecoin/bfgminer/bfgminer 006b4000-006b5000 r--p 000b4000 fd:03 2448 /home/litecoin/bfgminer/bfgminer 006b5000-006bb000 rw-p 000b5000 fd:03 2448 /home/litecoin/bfgminer/bfgminer 006bb000-006c5000 rw-p 00000000 00:00 0 01d46000-040c7000 rw-p 00000000 00:00 0 [heap] 7f2d58000000-7f2d58021000 rw-p 00000000 00:00 0 7f2d58021000-7f2d5c000000 ---p 00000000 00:00 0 7f2d5c000000-7f2d5c021000 rw-p 00000000 00:00 0 7f2d5c021000-7f2d60000000 ---p 00000000 00:00 0 7f2d60000000-7f2d60021000 rw-p 00000000 00:00 0 7f2d60021000-7f2d64000000 ---p 00000000 00:00 0 7f2d68000000-7f2d68021000 rw-p 00000000 00:00 0 7f2d68021000-7f2d6c000000 ---p 00000000 00:00 0 7f2d6d7fb000-7f2d6d7fc000 ---p 00000000 00:00 0 7f2d6d7fc000-7f2d6dffc000 rw-p 00000000 00:00 0 [stack:9883] 7f2d6dffc000-7f2d6dffd000 ---p 00000000 00:00 0 7f2d6dffd000-7f2d6e7fd000 rw-p 00000000 00:00 0 7f2d6e7fd000-7f2d6e7fe000 ---p 00000000 00:00 0 7f2d6e7fe000-7f2d6effe000 rw-p 00000000 00:00 0 [stack:9881] 7f2d6effe000-7f2d6efff000 ---p 00000000 00:00 0 7f2d6efff000-7f2d6f7ff000 rw-p 00000000 00:00 0 7f2d6f7ff000-7f2d6f800000 ---p 00000000 00:00 0 7f2d6f800000-7f2d70000000 rw-p 00000000 00:00 0 7f2d70000000-7f2d70021000 rw-p 00000000 00:00 0 7f2d70021000-7f2d74000000 ---p 00000000 00:00 0 7f2d74000000-7f2d744ec000 rw-p 00000000 00:00 0 7f2d744ec000-7f2d78000000 ---p 00000000 00:00 0 7f2d78000000-7f2d78021000 rw-p 00000000 00:00 0 7f2d78021000-7f2d7c000000 ---p 00000000 00:00 0 7f2d7c000000-7f2d7c65a000 rw-p 00000000 00:00 0 7f2d7c65a000-7f2d80000000 ---p 00000000 00:00 0 7f2d80000000-7f2d8065a000 rw-p 00000000 00:00 0 7f2d8065a000-7f2d84000000 ---p 00000000 00:00 0 7f2d84387000-7f2d84388000 ---p 00000000 00:00 0 7f2d84388000-7f2d84b88000 rw-p 00000000 00:00 0 7f2d84b88000-7f2d84b89000 ---p 00000000 00:00 0 7f2d84b89000-7f2d85389000 rw-p 00000000 00:00 0 [stack:9877] 7f2d85389000-7f2d8539a000 rw-s 0bf82000 00:05 7538 /dev/ati/card0 7f2d8539a000-7f2d853ab000 rw-s 0bf81000 00:05 7538 /dev/ati/card0 7f2d853ab000-7f2d853bc000 rw-s 0bf80000 00:05 7538 /dev/ati/card0 7f2d853bc000-7f2d853cd000 rw-s 0bf7e000 00:05 7538 /dev/ati/card0 7f2d853cd000-7f2d853de000 rw-s 0bf7d000 00:05 7538 /dev/ati/card0 7f2d853de000-7f2d853df000 ---p 00000000 00:00 0 7f2d853df000-7f2d85bdf000 rw-p 00000000 00:00 0 7f2d85bdf000-7f2d85be0000 ---p 00000000 00:00 0 7f2d85be0000-7f2d863e0000 rw-p 00000000 00:00 0 7f2d863e0000-7f2d863e1000 ---p 00000000 00:00 0 7f2d863e1000-7f2d86be1000 rw-p 00000000 00:00 0 [stack:9871] 7f2d86be1000-7f2d86be2000 ---p 00000000 00:00 0 7f2d86be2000-7f2d873e2000 rw-p 00000000 00:00 0 [stack:9870] 7f2d873e2000-7f2d873e3000 ---p 00000000 00:00 0 7f2d873e3000-7f2d87be3000 rw-p 00000000 00:00 0 [stack:9869] 7f2d87be3000-7f2d87bf6000 r-xp 00000000 08:03 20764 /lib64/libresolv-2.17.so 7f2d87bf6000-7f2d87df6000 ---p 00013000 08:03 20764 /lib64/libresolv-2.17.so 7f2d87df6000-7f2d87df7000 r--p 00013000 08:03 20764 /lib64/libresolv-2.17.so 7f2d87df7000-7f2d87df8000 rw-p 00014000 08:03 20764 /lib64/libresolv-2.17.so 7f2d87df8000-7f2d87dfa000 rw-p 00000000 00:00 0 7f2d87dfa000-7f2d87dff000 r-xp 00000000 08:03 20755 /lib64/libnss_dns-2.17.so 7f2d87dff000-7f2d87ffe000 ---p 00005000 08:03 20755 /lib64/libnss_dns-2.17.so 7f2d87ffe000-7f2d87fff000 r--p 00004000 08:03 20755 /lib64/libnss_dns-2.17.so 7f2d87fff000-7f2d88000000 rw-p 00005000 08:03 20755 /lib64/libnss_dns-2.17.so 7f2d88000000-7f2d8802a000 rw-p 00000000 00:00 0 7f2d8802a000-7f2d8c000000 ---p 00000000 00:00 0 7f2d8c000000-7f2d8c02a000 rw-p 00000000 00:00 0 7f2d8c02a000-7f2d90000000 ---p 00000000 00:00 0 7f2d90000000-7f2d9002a000 rw-p 00000000 00:00 0 7f2d9002a000-7f2d94000000 ---p 00000000 00:00 0 7f2d94008000-7f2d94019000 rw-s 0bf7c000 00:05 7538 /dev/ati/card0 7f2d94019000-7f2d9401a000 ---p 00000000 00:00 0 7f2d9401a000-7f2d9405a000 rw-p 00000000 00:00 0 [stack:9876] 7f2d9408a000-7f2d9409a000 rw-s 0bf72000 00:05 1642 /dev/ati/card2 7f2d9409a000-7f2d940aa000 rw-s 0bf71000 00:05 1642 /dev/ati/card2 7f2d940aa000-7f2d940ac000 rw-s 0bf70000 00:05 1642 /dev/ati/card2
|
Cassey
|
|
|
gigica viteazu`
Sr. Member
![*](https://bitcointalk.org/Themes/custom1/images/star.gif) ![*](https://bitcointalk.org/Themes/custom1/images/star.gif) ![*](https://bitcointalk.org/Themes/custom1/images/star.gif)
Offline
Activity: 458
Merit: 250
beast at work
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
March 10, 2014, 05:33:46 AM |
|
Let me know if you run into any issues. Would love to hear if it works under the Pi (it should). Haven't had a chance to test that yet.
minepeon@minepeon ~/_tmp/bfgminer-feature-gridseed-support $ ./autogen.sh Getting submodules... Running autoreconf -if... configure.ac:42: installing './compile' configure.ac:29: installing './config.guess' configure.ac:29: installing './config.sub' configure.ac:40: installing './install-sh' configure.ac:40: installing './missing' Makefile.am:39: warning: 'INCLUDES' is the old name for 'AM_CPPFLAGS' (or '*_CPPFLAGS') Makefile.am: installing './depcomp'
minepeon@minepeon ~/_tmp/bfgminer-feature-gridseed-support $ ./configure --enable-scrypt checking build system type... armv6l-unknown-linux-gnueabihf checking host system type... armv6l-unknown-linux-gnueabihf checking target system type... armv6l-unknown-linux-gnueabihf checking for a BSD-compatible install... /usr/bin/install -c checking whether build environment is sane... yes checking for a thread-safe mkdir -p... /usr/bin/mkdir -p checking for gawk... gawk checking whether make sets $(MAKE)... yes checking whether make supports nested variables... yes checking whether make supports nested variables... (cached) yes checking for style of include used by make... GNU checking for gcc... gcc checking whether the C compiler works... yes checking for C compiler default output file name... a.out checking for suffix of executables... checking whether we are cross compiling... no checking for suffix of object files... o checking whether we are using the GNU C compiler... yes checking whether gcc accepts -g... yes checking for gcc option to accept ISO C89... none needed checking whether gcc understands -c and -o together... yes checking dependency style of gcc... gcc3 checking how to run the C preprocessor... gcc -E checking for grep that handles long lines and -e... /usr/bin/grep checking for egrep... /usr/bin/grep -E checking for ANSI C header files... yes checking for sys/types.h... yes checking for sys/stat.h... yes checking for stdlib.h... yes checking for string.h... yes checking for memory.h... yes checking for strings.h... yes checking for inttypes.h... yes checking for stdint.h... yes checking for unistd.h... yes checking minix/config.h usability... no checking minix/config.h presence... no checking for minix/config.h... no checking whether it is safe to define __EXTENSIONS__... yes checking whether to enable maintainer-specific portions of Makefiles... yes checking for gcc option to accept ISO C99... -std=gnu99 checking for ranlib... ranlib checking whether gcc -std=gnu99 needs -traditional... no checking for ranlib... (cached) ranlib checking how to run the C preprocessor... gcc -E checking sys/mman.h usability... yes checking sys/mman.h presence... yes checking for sys/mman.h... yes checking wchar.h usability... yes checking wchar.h presence... yes checking for wchar.h... yes checking for stdint.h... (cached) yes checking for mprotect... yes checking for sigaction... yes checking for sigaltstack... yes checking for siginterrupt... yes checking for mmap... yes checking for MAP_ANONYMOUS... yes checking whether memchr works... yes checking whether memmem is declared... yes checking for memmem... yes checking whether memmem works... yes checking for C/C++ restrict keyword... __restrict checking for uid_t in sys/types.h... yes checking for inline... inline checking whether the preprocessor supports include_next... yes checking whether system header files limit the line length... no checking for wchar_t... yes checking for unsigned long long int... yes checking for long long int... yes checking whether stdint.h conforms to C99... yes checking whether memmem is declared without a macro... yes checking whether mempcpy is declared without a macro... yes checking whether memrchr is declared without a macro... yes checking whether rawmemchr is declared without a macro... yes checking whether stpcpy is declared without a macro... yes checking whether stpncpy is declared without a macro... yes checking whether strchrnul is declared without a macro... yes checking whether strdup is declared without a macro... yes checking whether strncat is declared without a macro... yes checking whether strndup is declared without a macro... yes checking whether strnlen is declared without a macro... yes checking whether strpbrk is declared without a macro... yes checking whether strsep is declared without a macro... yes checking whether strcasestr is declared without a macro... yes checking whether strtok_r is declared without a macro... yes checking whether strerror_r is declared without a macro... yes checking whether strsignal is declared without a macro... yes checking whether strverscmp is declared without a macro... yes checking whether strtok_r is declared... (cached) yes checking whether memmem works in linear time... yes checking for memmem... (cached) yes checking whether memmem works... (cached) yes checking for struct sigaction.sa_sigaction... yes checking for volatile sig_atomic_t... yes checking for sighandler_t... yes checking whether sigaction is declared without a macro... yes checking whether sigaddset is declared without a macro... yes checking whether sigdelset is declared without a macro... yes checking whether sigemptyset is declared without a macro... yes checking whether sigfillset is declared without a macro... yes checking whether sigismember is declared without a macro... yes checking whether sigpending is declared without a macro... yes checking whether sigprocmask is declared without a macro... yes checking for sigprocmask... yes checking whether NULL can be used in arbitrary expressions... yes checking for strtok_r... yes checking whether strtok_r works... yes checking for special C compiler options needed for large files... no checking for _FILE_OFFSET_BITS value needed for large files... 64 checking for ANSI C header files... (cached) yes checking syslog.h usability... yes checking syslog.h presence... yes checking for syslog.h... yes checking sys/epoll.h usability... yes checking sys/epoll.h presence... yes checking for sys/epoll.h... yes checking for sys/mman.h... (cached) yes checking sys/prctl.h usability... yes checking sys/prctl.h presence... yes checking for sys/prctl.h... yes checking sys/file.h usability... yes checking sys/file.h presence... yes checking for sys/file.h... yes checking sys/termios.h usability... yes checking sys/termios.h presence... yes checking for sys/termios.h... yes checking linux/spi/spidev.h usability... yes checking linux/spi/spidev.h presence... yes checking for linux/spi/spidev.h... yes checking for struct i2c_msg.buf... no checking for struct i2c_msg.len... yes checking pwd.h usability... yes checking pwd.h presence... yes checking for pwd.h... yes checking for chroot... yes checking for sleep... yes checking for size_t... yes checking for working alloca.h... yes checking for alloca... yes checking whether HASH_ITER is declared... yes checking whether DL_CONCAT is declared... yes checking linux/vfio.h usability... yes checking linux/vfio.h presence... yes checking for linux/vfio.h... yes checking for pthread_cancel... with -pthread -lpthread checking for nanosleep... yes checking for pkg-config... /usr/bin/pkg-config checking pkg-config is at least version 0.9.0... yes checking for JANSSON... yes checking for libmicrohttpd... yes checking for libevent... yes checking for pkg-config... (cached) /usr/bin/pkg-config checking pkg-config is at least version 0.9.0... yes checking for LIBUSB... yes checking for hidapi... no checking for hidapi... no checking for hidapi... no checking whether libusb_error_name is declared... yes checking what baud rates your system supports... done checking for best native curses library... ncursesw5 checking whether curses library supports wide characters... yes checking whether the linker recognizes the -zorigin option... yes checking for armv6l-unknown-linux-gnueabihf-ldconfig... no checking for ldconfig... ldconfig checking libudev.h usability... yes checking libudev.h presence... yes checking for libudev.h... yes checking for LIBCURL... yes checking for setrlimit... yes checking for bswap_* functions... found in byteswap.h checking if bswap_16 is already a macro... yes checking for platform endian... little endian (endian.h) checking if good static asserts compile... yes checking if GNU format attribute compiles... yes checking for clock_gettime(CLOCK_MONOTONIC)... yes checking for library containing clock_gettime... none required checking for clock_nanosleep... yes checking for clock_gettime(CLOCK_MONOTONIC_RAW)... yes checking for log2... yes checking that generated files are newer than configure... done configure: creating ./config.status config.status: creating Makefile config.status: creating x86_64/Makefile config.status: creating x86_32/Makefile config.status: creating ccan.bfg/Makefile config.status: creating lib/Makefile config.status: creating 70-bfgminer.rules config.status: creating config.h config.status: executing depfiles commands === configuring in libblkmaker (/home/minepeon/_tmp/bfgminer-feature-gridseed-support/libblkmaker) configure: WARNING: no configuration information is in libblkmaker
------------------------------------------------------------------------ bfgminer 3.10.0 configuration options summary ------------------------------------------------------------------------
CFLAGS...............: -pthread -g -O2 -I/usr/include/libusb-1.0 -pthread -Ilibblkmaker LDFLAGS..............: -pthread -Llibblkmaker/.libs -Wl,-rpath,\$$ORIGIN/libblkmaker/.libs,-zorigin -lpthread -lcurl -ljansson -L/usr/lib -lncursesw -lm -ludev -lusb-1.0 -lblkmaker_jansson-0.1 -lblkmaker-0.1 Installation.prefix..: /usr/local
Enabled..Lowlevel....: pci pci:uio pci:vfio usb vcom Disabled.Lowlevel....: hid Enabled..Drivers.....: antminer avalon bifury bigpic bitforce bitforce:uio bitfury_gpio cairnsmore drillbit erupter gridseed hashbusteravalon hashbusterusb hashfast icarus klondike littlefury modminer proxy proxy:getwork proxy:stratum twinfury x6500 ztex Disabled.Drivers.....: bfsb cpu hashbuster knc metabank nanofury opencl To enable nanofury, install hidapi To enable hashbuster, install hidapi Enabled..Algorithms..: SHA256d scrypt Disabled.Algorithms..: Enabled..Options.....: libusb ncursesw5 Disabled.Options.....:
minepeon@minepeon ~/_tmp/bfgminer-feature-gridseed-support $ make make all-recursive make[1]: Entering directory '/home/minepeon/_tmp/bfgminer-feature-gridseed-support' Making all in lib make[2]: Entering directory '/home/minepeon/_tmp/bfgminer-feature-gridseed-support/lib' GEN arg-nonnull.h GEN c++defs.h GEN warn-on-use.h GEN signal.h GEN string.h make all-recursive make[3]: Entering directory '/home/minepeon/_tmp/bfgminer-feature-gridseed-support/lib' make[4]: Entering directory '/home/minepeon/_tmp/bfgminer-feature-gridseed-support/lib' CC dummy.o AR libgnu.a make[4]: Leaving directory '/home/minepeon/_tmp/bfgminer-feature-gridseed-support/lib' make[3]: Leaving directory '/home/minepeon/_tmp/bfgminer-feature-gridseed-support/lib' make[2]: Leaving directory '/home/minepeon/_tmp/bfgminer-feature-gridseed-support/lib' Making all in ccan.bfg make[2]: Entering directory '/home/minepeon/_tmp/bfgminer-feature-gridseed-support/ccan.bfg' make[2]: *** No rule to make target '../ccan-upstream/ccan/opt/helpers.c', needed by '../ccan-upstream/ccan/opt/libccan_a-helpers.o'. Stop. make[2]: Leaving directory '/home/minepeon/_tmp/bfgminer-feature-gridseed-support/ccan.bfg' Makefile:2035: recipe for target 'all-recursive' failed make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory '/home/minepeon/_tmp/bfgminer-feature-gridseed-support' Makefile:826: recipe for target 'all' failed make: *** [all] Error 2
|
|
|
|
|