Updated Windows build doc for WSL/Xenial workaround #11438

pull sipsorcery wants to merge 2 commits into bitcoin:master from sipsorcery:wslbuilddoc changing 1 files +57 −17
  1. sipsorcery commented at 8:46 PM on October 2, 2017: member

    An update to the Windows build document that provides workarounds for the broken 64 bit mingw32 cross compiler on WSL/Xenial.

    This update is an alternative to pull request #11437. While that pull request takes a valid approach by stating building on WSL should be avoided I think it is more useful to give Windows developers a workaround option.

    The instructions have been tested on:

    • Ubuntu 14.04 and 64 bit mingw32 tool chain
    • Ubuntu 16.04 and 64 bit mingw32 tool chain
    • Ubuntu 17.04 and 64 bit mingw32 tool chain
    • Windows Subsystem for Linux (Windows 10 OS Build 15063.608) and 32 bit mingw32 tool chain
    • Windows Subsystem for Linux (Windows 10 OS Build 15063.608) and 64 bit mingw32 tool chain

    Related items:

    • Serious incompatibility problems w/ newer mingw-64 on Ubuntu #8653
    • -fstack-protector-all triggers crashes in mingw-w64 5.3.1 #8732
    • Windows build appears broken on WSL (buntu okay) #10269
    • Compilation error for windows target #11437
  2. fanquake added the label Docs and Output on Oct 2, 2017
  3. fanquake added the label Windows on Oct 2, 2017
  4. in doc/build-windows.md:79 in 1777a44306 outdated 
      75 | +
  76 | +Ubuntu Trusty 14.04:
  77 | +
  78 | +	sudo apt-get install g++-mingw-w64-x86-64 mingw-w64-x86-64-dev
  79 | +
  80 | +Ubuntu Xenial 16.04 and Windows Subsystem for Linux (*)(**):
    meshcollider commented at 2:13 AM on October 3, 2017:

    Use footnotes ([^1]) rather than * because * is used for formatting. (Same in other places).

  5. in doc/build-windows.md:12 in 1777a44306 outdated 
       5 | @@ -6,8 +6,11 @@ Below are some notes on how to build Bitcoin Core for Windows.
   6 |  Most developers use cross-compilation from Ubuntu to build executables for
   7 |  Windows. This is also used to build the release binaries.
   8 |  
   9 | -Currently only building on Ubuntu Trusty 14.04 is supported.
  10 | -Other versions are unsupported or known to be broken (e.g. Ubuntu Xenial 16.04).
  11 | +Building on Ubuntu Trusty 14.04 is recommended.
  12 | +It is possible to build on Ubuntu Xenial 16.04. Follow the Windows Subsystem for Linux
  13 | +steps since it uses the same Ubuntu version.
  14 | +Building on Ubuntu Zesty 17.04 has been verified to work using the same stesp as for
    meshcollider commented at 2:14 AM on October 3, 2017:

    stesp -> steps

  6. in doc/build-windows.md:142 in 9030afeac8 outdated 
     134 | @@ -107,3 +135,20 @@ as they appear in the release `.zip` archive. This can be done in the following
 135 |  way. This will install to `c:\workspace\bitcoin`, for example:
 136 |  
 137 |      make install DESTDIR=/mnt/c/workspace/bitcoin
 138 | +
 139 | +Footnotes
 140 | +---------
 141 | +
 142 | +[^1] There is currently a bug in the 64 bit mingw-w64 cross compiler packaged for WSL/Ubuntu Xenial 16.04 that
    meshcollider commented at 3:39 AM on October 3, 2017:

    Colon after [^1] :)

  7. in doc/build-windows.md:86 in 9030afeac8 outdated 
      82 | +    sudo apt install software-properties-common
  83 | +    sudo add-apt-repository "deb http://archive.ubuntu.com/ubuntu zesty universe"
  84 | +    sudo apt update
  85 | +    sudo apt upgrade
  86 | +    sudo wget http://archive.ubuntu.com/ubuntu/pool/main/b/binutils/binutils_2.28-3ubuntu1_amd64.deb
  87 | +    sduo dpkg -i binutils_2.28-3ubuntu1_amd64.deb
    meshcollider commented at 3:49 AM on October 3, 2017:

    Sudo

  8. in doc/build-windows.md:109 in a1e32a0d5a outdated 
     105 | @@ -83,10 +106,15 @@ Then build using:
 106 |  
 107 |  To build executables for Windows 32-bit, install the following dependencies:
 108 |  
 109 | -    sudo apt-get install g++-mingw-w64-i686 mingw-w64-i686-dev 
 110 | +    sudo apt install g++-mingw-w64-i686 mingw-w64-i686-dev
    meshcollider commented at 4:24 AM on October 3, 2017:

    The trailing whitespace failure is the end of this line I think. Sorry for so many little reviews :) Remember to squash all your commits at the end

  9. sipsorcery force-pushed on Oct 3, 2017
  10. meshcollider commented at 5:55 AM on October 3, 2017: contributor

    Gentle utACK https://github.com/bitcoin/bitcoin/commit/5e31c532e2fa1f2261ed0f94739a57cf8d5ee7e9 Will hopefully have some time to test this soon, and compare with #11437 properly

  11. NicolasDorier commented at 5:58 AM on October 3, 2017: contributor

    Concept ACK. thank you, this will save me so much time! Trying this.

  12. molxyz commented at 6:04 AM on October 3, 2017: none

    There's a misspelled word: sduo dpkg -i binutils_2.28-3ubuntu1_amd64.deb

  13. sipsorcery commented at 6:13 AM on October 3, 2017: member

    @molxyz have you got the latest version? That typo was fixed.

  14. molxyz commented at 7:11 AM on October 3, 2017: none

    @sipsorcery Ah yes.. sorry I forgot to refresh the page, got it now. This is great, thank you.

  15. NicolasDorier commented at 8:01 AM on October 3, 2017: contributor

    Still another problem on my WSL, probably unrelated though.

    configure: error: No working boost sleep implementation found.

    I think I give up with WSL, keeping my docker :/

  16. sipsorcery commented at 9:33 AM on October 3, 2017: member

    @NicolasDorier I did see that error once or twice and I believe it was around the same time as I was getting the error about the std::mutex header missing. I haven't seen it for a while though and I'd estimate I've re-installed and built bitcoin on WSL at least half a dozen times in the last week. My suggestion would be to either completely uninstall WSL using lxrun /uninstall /full and then reinstall or at the very least clean the dependencies, including boost, from your bitcoin source tree with git clean -x -f -d.

  17. in doc/build-windows.md:10 in 6e4fa60f33 outdated 
       5 | @@ -6,8 +6,11 @@ Below are some notes on how to build Bitcoin Core for Windows.
   6 |  Most developers use cross-compilation from Ubuntu to build executables for
   7 |  Windows. This is also used to build the release binaries.
   8 |  
   9 | -Currently only building on Ubuntu Trusty 14.04 is supported.
  10 | -Other versions are unsupported or known to be broken (e.g. Ubuntu Xenial 16.04).
  11 | +Building on Ubuntu Trusty 14.04 is recommended.
  12 | +It is possible to build on Ubuntu Xenial 16.04. Follow the Windows Subsystem for Linux
    laanwj commented at 1:57 PM on October 4, 2017:

    Should mention early that 16.04 produces incorrect code, so that people don't get started with it and come to the conclusion later that it's broken.

    sipsorcery commented at 9:09 PM on October 4, 2017:

    There is no bad code, provided the mingw32 x-compiler on wsl/xenial is updated as per the instructions in the doc.

  18. in doc/build-windows.md:11 in 6e4fa60f33 outdated 
       5 | @@ -6,8 +6,11 @@ Below are some notes on how to build Bitcoin Core for Windows.
   6 |  Most developers use cross-compilation from Ubuntu to build executables for
   7 |  Windows. This is also used to build the release binaries.
   8 |  
   9 | -Currently only building on Ubuntu Trusty 14.04 is supported.
  10 | -Other versions are unsupported or known to be broken (e.g. Ubuntu Xenial 16.04).
  11 | +Building on Ubuntu Trusty 14.04 is recommended.
  12 | +It is possible to build on Ubuntu Xenial 16.04. Follow the Windows Subsystem for Linux
  13 | +steps since it uses the same Ubuntu version.
    MarcoFalke commented at 7:32 AM on October 5, 2017:

    This should probably mention that building on WSL currently is by following the building on Xenial notes. (not the other way round)

  19. in doc/build-windows.md:13 in 6e4fa60f33 outdated 
      10 | -Other versions are unsupported or known to be broken (e.g. Ubuntu Xenial 16.04).
  11 | +Building on Ubuntu Trusty 14.04 is recommended.
  12 | +It is possible to build on Ubuntu Xenial 16.04. Follow the Windows Subsystem for Linux
  13 | +steps since it uses the same Ubuntu version.
  14 | +Building on Ubuntu Zesty 17.04 has been verified to work using the same steps as for
  15 | +Ubuntu Trusty 14.04.
    MarcoFalke commented at 7:32 AM on October 5, 2017:

    I don't think this is true, given that there are two different sections. One for trusty, one for zesty.

  20. in doc/build-windows.md:12 in 6e4fa60f33 outdated 
       5 | @@ -6,8 +6,11 @@ Below are some notes on how to build Bitcoin Core for Windows.
   6 |  Most developers use cross-compilation from Ubuntu to build executables for
   7 |  Windows. This is also used to build the release binaries.
   8 |  
   9 | -Currently only building on Ubuntu Trusty 14.04 is supported.
  10 | -Other versions are unsupported or known to be broken (e.g. Ubuntu Xenial 16.04).
  11 | +Building on Ubuntu Trusty 14.04 is recommended.
  12 | +It is possible to build on Ubuntu Xenial 16.04. Follow the Windows Subsystem for Linux
  13 | +steps since it uses the same Ubuntu version.
  14 | +Building on Ubuntu Zesty 17.04 has been verified to work using the same steps as for
    MarcoFalke commented at 7:33 AM on October 5, 2017:

    I think you can write "17.04 or later", since 17.10 seems to work as well with the same steps.

  21. in doc/build-windows.md:79 in 6e4fa60f33 outdated 
      76 | +Ubuntu Trusty 14.04:
  77 |  
  78 |      sudo apt-get install g++-mingw-w64-x86-64 mingw-w64-x86-64-dev
  79 |  
  80 | -Then build using:
  81 | +Ubuntu Xenial 16.04 and Windows Subsystem for Linux ([^1][^2]):
    MarcoFalke commented at 7:35 AM on October 5, 2017:

    Might want to remove WSL here, since it will no longer be true when the user runs a different ubuntu version than xenial in their WSL.

    sipsorcery commented at 8:28 AM on October 5, 2017:

    Wouldn't it be better to leave it there and update the doc when WSL gets updated? I suspect the majority of devs reading this doc will be looking for WSL instructions.

  22. in doc/build-windows.md:89 in 6e4fa60f33 outdated 
      86 | +    sudo apt upgrade
  87 | +    sudo update-alternatives --config x86_64-w64-mingw32-g++ # Set the default mingw32 g++ compiler option to posix.
  88 | +
  89 | +Ubuntu Zesty 17.04 ([^2]):
  90 | +
  91 | +    sudo apt-get install g++-mingw-w64-x86-64 mingw-w64-x86-64-dev
    MarcoFalke commented at 7:37 AM on October 5, 2017:

    µnit: This installation step is the same for all three version. Might as well mention it only once, mention that no further steps are needed on trusty and that other versions require some workarounds: ...

  23. in doc/build-windows.md:140 in 6e4fa60f33 outdated 
     131 | @@ -107,3 +132,20 @@ as they appear in the release `.zip` archive. This can be done in the following
 132 |  way. This will install to `c:\workspace\bitcoin`, for example:
 133 |  
 134 |      make install DESTDIR=/mnt/c/workspace/bitcoin
 135 | +
 136 | +Footnotes
    MarcoFalke commented at 7:38 AM on October 5, 2017:

    Maybe ot: For some reason GitHub doesn't insert links to the footnotes for me.

    sipsorcery commented at 9:00 AM on October 5, 2017:

    Looks like that footnote is not supported on github. According to a comment on this SO answer that format is used on GitLab. I'll use the alternative suggestion of anchor links.

    molxyz commented at 1:35 PM on October 6, 2017:

    This is great. I have tested on my WSL Ubuntu Xenial 16.04 several times and it works, but I have a question regarding this part:

    sudo update-alternatives --config x86_64-w64-mingw32-g++

    There are 2 choices for the alternative x86_64-w64-mingw32-g++ (providing /usr/bin/x86_64-w64-mingw32-g++).

    Selection Path Priority Status

    0 /usr/bin/x86_64-w64-mingw32-g++-win32 60 auto mode 1 /usr/bin/x86_64-w64-mingw32-g++-posix 30 manual mode 2 /usr/bin/x86_64-w64-mingw32-g++-win32 60 manual mode

    The only choice is "1" to get bitcoin compiled successfully, the other choices cause errors in "make". Is there a reason to leave 3 choices? Sorry, I'm still new to this and the choices made me confused at first until I tried them all.
    Thank you for doing this, I'm thrilled to be able to compile bitcoin on WSL again! :D

    MarcoFalke commented at 3:19 PM on October 6, 2017:

    Note that "0" is the default and the options are 1 (posix) and 2 (win32).

  24. MarcoFalke commented at 7:39 AM on October 5, 2017: member

    Concept ACK. Some feedback and a nit.

  25. in doc/build-windows.md:86 in 8aebdc1216 outdated 
      83 | +
  84 | +    No further steps required
  85 | +
  86 | +Ubuntu Xenial 16.04 and Windows Subsystem for Linux <sup>[1](#footnote1),[2](#footnote2)</sup>:
  87 | +
  88 | +    sudo apt-get install g++-mingw-w64-x86-64 mingw-w64-x86-64-dev software-properties-common
    MarcoFalke commented at 11:19 AM on October 5, 2017:

    µnit: Can remove the "g++-mingw-w64-x86-64 mingw-w64-x86-64-dev"

  26. in doc/build-windows.md:94 in 8aebdc1216 outdated 
      91 | +    sudo apt upgrade
  92 | +    sudo update-alternatives --config x86_64-w64-mingw32-g++ # Set the default mingw32 g++ compiler option to posix.
  93 | +
  94 | +Ubuntu Zesty 17.04 <sup>[2](#footnote2)</sup>:
  95 |  
  96 | +    sudo apt-get install g++-mingw-w64-x86-64 mingw-w64-x86-64-dev
    MarcoFalke commented at 11:19 AM on October 5, 2017:

    µnit: Can remove this line.

  27. MarcoFalke commented at 5:03 PM on October 5, 2017: member

    Please squash your commits according to https://github.com/bitcoin/bitcoin/blob/master/CONTRIBUTING.md#squashing-commits

  28. sipsorcery force-pushed on Oct 5, 2017
  29. laanwj commented at 9:49 AM on October 11, 2017: member

    Needs rebase for #11437.

  30. sipsorcery commented at 12:05 PM on October 11, 2017: member

    #11437 is largely mutually exclusive to this update. It steers devs away from using WSL or Ubuntu 16 due to the non-standard build steps required. This pull request provides those non-standard build steps.

  31. NicolasDorier commented at 1:13 PM on October 13, 2017: contributor

    I made a fresh ubuntu WSL 16.04, was unable to install boost, I tried all sort of incantation without success...

    libboost-all-dev : Depends: libboost-tools-dev but it is not going to be installed
                    Depends: libboost-atomic-dev but it is not going to be installed
                    Depends: libboost-chrono-dev but it is not going to be installed
                    Depends: libboost-context-dev but it is not going to be installed
                    Depends: libboost-coroutine-dev but it is not going to be installed
                    Depends: libboost-date-time-dev but it is not going to be installed
                    Depends: libboost-exception-dev but it is not going to be installed
                    Depends: libboost-fiber-dev but it is not going to be installed
                    Depends: libboost-graph-dev but it is not going to be installed
                    Depends: libboost-graph-parallel-dev but it is not going to be installed
                    Depends: libboost-iostreams-dev but it is not going to be installed
                    Depends: libboost-locale-dev but it is not going to be installed
                    Depends: libboost-log-dev but it is not going to be installed
                    Depends: libboost-math-dev but it is not going to be installed
                    Depends: libboost-mpi-dev but it is not going to be installed
                    Depends: libboost-mpi-python-dev but it is not going to be installed
                    Depends: libboost-python-dev but it is not going to be installed
                    Depends: libboost-random-dev but it is not going to be installed
                    Depends: libboost-regex-dev but it is not going to be installed
                    Depends: libboost-serialization-dev but it is not going to be installed
                    Depends: libboost-signals-dev but it is not going to be installed
                    Depends: libboost-test-dev but it is not going to be installed
                    Depends: libboost-timer-dev but it is not going to be installed
                    Depends: libboost-type-erasure-dev but it is not going to be installed
                    Depends: libboost-wave-dev but it is not going to be installed

    Not sure if related with this PR, but the instructions did not seem enough.

  32. sipsorcery commented at 3:26 AM on October 14, 2017: member

    @NicolasDorier what type of VM, Ubuntu 16 version and platform (x86 or x64)?

    I have run the install steps using the latest source form the bitcoin git repo on VMWare Workstation with Ubuntu 16.04.3 Server x64 without any problems and resulting in working Windows executables.

    I'm happy to check other permutations if you let me know what your configuration is.

  33. NicolasDorier commented at 7:18 AM on October 15, 2017: contributor

    This is x64.

    DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=16.04
DISTRIB_CODENAME=xenial
DISTRIB_DESCRIPTION="Ubuntu 16.04.3 LTS"

    Problems are on boost... I can't seems to be able to fetch boost for some reason.

  34. MarcoFalke commented at 8:17 AM on October 15, 2017: member

    Needs rebase on current master to solve merge conflicts.

  35. sipsorcery commented at 8:25 AM on October 15, 2017: member

    @MarcoFalke merge conflict is from #11437 which is largely mutually exclusive to this update.

    It's a question of whether to steers devs away from building on WSL/ Ubuntu 16 using non-standard build steps required or only recommend Ubuntu 14 & 17 as per #11437.

  36. MarcoFalke commented at 8:48 AM on October 15, 2017: member

    @sipsorcery Agree. Though, we can not merge your pull if there are merge conflicts (even if only minor).

    I don't have WSL, so I can't help with testing and recommendations. How you solve the merge conflict is pretty much up to you. It doesn't matter if you use -Xtheirs or -Xours or solve it manually ...

  37. Updated Windows build doc for WSL/Xenial workarounds. e0fc4a7356
  38. sipsorcery force-pushed on Oct 15, 2017
  39. sipsorcery commented at 11:59 AM on October 15, 2017: member

    @MarcoFalke no worries, I've removed the conflict by pushing my change to the build-windows.md file on top of trunk.

  40. meshcollider commented at 10:10 PM on October 15, 2017: contributor

    Just want to point out that your commit isn't associated with your GitHub account currently, you might have used a different email address? You might want to commit with the same email address so your account gets the credit :)

  41. sipsorcery commented at 6:15 AM on October 16, 2017: member

    @NicolasDorier is there any reason you're attempting to install boost packages with apt?

    If you only need boost for a bitcoin build the required includes and libraries get installed as part of the build steps that download and compile all the required dependencies.

    cd depends make HOST=x86_64-w64-mingw32

  42. NicolasDorier commented at 6:56 AM on October 16, 2017: contributor

    yes, I need it because I need to run python tests on WSL.

  43. sipa commented at 6:58 AM on October 16, 2017: member

    The python tests don't need boost?

  44. NicolasDorier commented at 8:46 AM on October 16, 2017: contributor

    They don't but I need to compile bitcoind as a linux binary, which need boost.

  45. sipa commented at 8:50 AM on October 16, 2017: member

    @NicolasDorier Using the depends build will do all that.

  46. sipsorcery commented at 9:12 AM on October 16, 2017: member

    On a related note the Windows 10 Fall Creators Update gets released tomorrow (17 Oct 2017) and contains a major update to WSL. The main update is that WSL will now be deployed as a Windows Store App and users will need to choose from different Linux distros; currently Ubuntu (Xenial), openSUSE and SUSE Linux Enterprise Server.

    Update: I've verified that the Windows bitcoin build on the Fall Creators Update & Ubuntu Windows Store App works successfully. The Ubuntu version hasn't changed from 16.04.3.

  47. NicolasDorier commented at 9:36 AM on October 16, 2017: contributor

    my understanding was that

    cd depends
make HOST=x86_64-w64-mingw32

    will just install the deps for making a windows binary. I was unaware it was also adding the libboost dependencies for linux build. Trying that now.

  48. sipa commented at 9:41 AM on October 16, 2017: member

    make HOST=x86_64-unknown-linux-gnu will do a build of dependencies for Linux build on x86_64.

  49. NicolasDorier commented at 9:44 AM on October 16, 2017: contributor

    Trying. Maybe this is something to add as exception of Xenial in the doc, since installing package with apt-get is not available?

  50. NicolasDorier commented at 1:16 PM on October 16, 2017: contributor

    Ok now

    WARNING: 'automake-1.14' is missing on your system.

    So make HOST=x86_64-unknown-linux-gnu does not run, I ran apt-get of autotools.

    autotools-dev is already the newest version (20150820.1).

    I think I will provide an easy to build image on docker hub based on trusty and document it. Would, requires Hyper-V for windows (windows 10 Enterprise edition) though.

  51. sipsorcery commented at 2:53 AM on October 17, 2017: member

    @NicolasDorier the automake error seems to be generated in the protobuf dependency build. The same error was mentioned in #10269. I'm guessing it's triggered when the apt packages line up in a certain way.

    The suggested workaround, which also worked for me in the past, is:

    make HOST=x86_64-unknown-linux-gnu AUTOMAKE=:

    Edit: Also #11282.

  52. Updated instructions for Windows 10 Fall Creators Update. 7383d77264
  53. NicolasDorier commented at 7:34 AM on October 18, 2017: contributor 
    autoreconf: running: : --add-missing --copy
Can't exec ":": No such file or directory at /usr/share/autoconf/Autom4te/FileUtils.pm line 326, <GEN2> line 5.
autoreconf: failed to run :: No such file or directory
funcs.mk:242: recipe for target '/mnt/c/Users/NicolasDorier/Documents/Sources/bitcoin-docker/bitcoin/depends/work/build/x86_64-unknown-linux-gnu/libevent/2.1.8-stable-b014fbf5633/.stamp_preprocessed' failed
make: *** [/mnt/c/Users/NicolasDorier/Documents/Sources/bitcoin-docker/bitcoin/depends/work/build/x86_64-unknown-linux-gnu/libevent/2.1.8-stable-b014fbf5633/.stamp_preprocessed] Error 1

    Ha might be because too long path... I don't know. :(

    I think this PR is definitively a way to the right direction, I hope other people can try it, my environment appear to be seriously fucked up.

  54. rebroad commented at 4:54 PM on November 12, 2017: contributor

    tested ACK

  55. laanwj commented at 11:48 AM on November 13, 2017: member

    @rebroad Thanks for testing

  56. laanwj merged this on Nov 13, 2017
  57. laanwj closed this on Nov 13, 2017
  58. laanwj referenced this in commit 7fbf3c638f on Nov 13, 2017
  59. jky7 commented at 6:03 PM on November 13, 2017: none

    @NicolasDorier I had the same issue, what ended up working was the following: make HOST=x86_64-w64-mingw32 AUTOCONF=: AUTOHEADER=: AUTOMAKE=: ACLOCAL=:

    also I have found that downloading the repo natively from inside WSL was less likely to break things in the build than downloading it in Windows and then working on it from WSL

  60. meshcollider commented at 9:43 AM on November 15, 2017: contributor

    Post-merge tested ACK on clean install of 64-bit Win10 Home 1709 build 16299.64

  61. NicolasDorier commented at 4:56 AM on November 21, 2017: contributor

    @josephky ha yes. There are some git config magic to do so git on Windows does not convert LF to CRLF on checkout. And that it convert CRLF to LF on check-in. I did that long time ago, now it works fine.

    It was only core.autocrlf=input if I remember...

  62. sipsorcery deleted the branch on Nov 21, 2017
  63. eugene-sy referenced this in commit ce593ae361 on Jan 6, 2018
  64. DrahtBot locked this on Sep 8, 2021
Contributors
sipsorcerymeshcolliderNicolasDoriermolxyzlaanwjMarcoFalkesiparebroadjky7
Labels
DocsWindows
Linked (view graph)
#8653 Serious incompatibility problems w/ newer mingw-64 on Ubuntu#8732 `-fstack-protector-all` triggers crashes in mingw-w64 5.3.1#10269 Windows build appears broken on WSL (buntu okay)#11437 [Docs] Update Windows build instructions for using WSL and Ubuntu 17.04#11659 Contradictory Windows build instructions
github-metadata-mirror

This is a metadata mirror of the GitHub repository bitcoin/bitcoin. This site is not affiliated with GitHub. Content is generated from a GitHub metadata backup.
generated: 2026-04-19 09:15 UTC
This site is hosted by @0xB10C
More mirrored repositories can be found on mirror.b10c.me