Building Old Code
Here's the basic process
- Create a Win2012 VM in VirtualBox
- Install Win2012 in the VM
- Disable HyperV on the Guest
- Add shared-folders
- Port forward RDP (3389) and WinRM (5985)
- Punch through firewall for RDP
- Run the powershell script (bitcoin-?.?.?.ps1)
- Run the batch script (buildAll.cmd)
- Turn off network due to old protocol
- Test the build (bitcoin-?.?.?\dist\bitcoin.exe)
- Try it under Windows 2000 (NT50) (requires rsync)
- Try it under XP (NT51)
- Try it under Vista (NT60) using Powershell 2.0
- Try it under Windows 7 (NT61) using Powershell 2.0 or 3.0
- Try it under Windows 2012 (NT62) using Powershell 3.0
- Build v0.1.0
- Build v0.1.3
- Build v0.1.5
- Build v0.2.0
- Build v0.3.0
- Build v0.3.13 last build before moving to TDM
- Debug hang on v0.1.0
- Debug hang on v0.2.0
- Cut binary releases of builds v0.1.0, v0.1.3 etc..
- Windows Vista RC2 (Longhorn; NT60) released October0 6, 2006
- Find a copy of Windows 7 (NT61) released July 22, 2009
- Windows 2012 (NT62) HV released September 4, 2012
- Windows 2012 R2 (NT63) HV released October 17, 2013
- Windows 2016 (NT100) HV released October 12, 2016
- Windows 2019 (NT100) HV released November 13, 2018
- 0.1.0 Jan 10, 2009
- 0.1.2
- 0.1.3 Jan 12, 2009
- 0.1.5 Feb 04, 2009
- 0.1.5_plus
- 0.2.0 Dec 13, 2009
- 0.3.0 Jul 04, 2010
- 0.3.1
- 0.3.2
- 0.3.3
- 0.3.6
- 0.3.7
- 0.3.8
- 0.3.10
- 0.3.11
- 0.3.12
- 0.3.13
- 0.3.14
- 0.3.15
- 0.3.17
- 0.3.18
- 0.3.19
- 0.3.20 Feb 18, 2011 Code transitioned to github
- 0.3.21
- 0.3.22
- 0.3.23
- 0.3.24
- 0.4.0
- 0.4.1
- 0.5.0
- 0.5.1
- 0.5.2
- 0.5.3
- 0.5.4
- 0.5.7
- 0.6.0
- 0.6.1
- 0.6.2 (archive)
- 0.6.3
- 0.7.0
- 0.7.1
- 0.7.2 (archive)
- 0.8.0 (archive)
- 0.8.1 (archive)
- 0.8.2
- 0.8.3
- 0.8.4
- 0.8.5
- 0.8.6 (live)
- 0.9.0 (live)
As I mentioned in my other post, As a learning endeavor, I've been working on building the first 3 versions of bitcoin.exe. Namely version 0.1.0, 0.1.3 and 0.1.5. To try to be true to the original, I'm working on building up an environment as close to the original one used in October 2009. Harder than it might seem.
Although it isn't known (by me), The two major versions of Windows that were available at this time Windows Vista (Longhorn) and Windows 7. Not really wanting to buy a license for either of these, my choices are to use either archived beta's or jump a bit ahead or behind. I decided to jump ahead to Windows 8 (2012) and use that as by build base. Since I'm using the "Server Core" edition, it may be a bit foreign to most, but I find it works quite well.
Since I'm using an old OS, its best to run it in a virtual machine just to reduce the heartache of trying to find HW that will run the old SW. I'm use VirtualBox which is available in many different host formats.
Once I get the OS up and running I install Perl (strawberry), GCC (MinGW) and Bash (MSYS). From there it's pretty much just paint by numbers, though I'm still having trouble in the very last step. Here's, hopefully, a very brief rundown of how to get it working
At the end of this article I have the links to all the files and their MD5 checksum. They are all archives of one kind or another that have their own checksums baked in. This is just so you can sanity check your downloads. Files not OS or VM related will be pushed to the VM once we get it up and running.
I used the default Windows 2012 settings for VirtualBox. Though I did enable port forwarding for RDP (3389) and remote shell (5985). I'd suggest also enabling shared folders to push over the downloads. You will need to take care. I'm running Hyper-V as my guest OS (yes inside a VM) since it's free. To pull this off you have to disable the Hyper-V feature halfway through the install.
OpenSSL was the build that originally tripped me up. Turns out it was a bad version of Perl I was using. I switched to Strawberry Perl and everything cleared up. I did have to give up on the optimizations Satoshi outlined in his original code, and just did a plain vanilla build of OpenSSL (disabling the assembler since I don't own one)
set home=C:\msys\1.0\src\bitcoin-0.1.5
set path=C:\MinGW\mingw32\bin;C:\MinGW\bin;C:\Perl58\bin;%path%
set tee=C:\msys\1.0\bin\tee.exe
cd /d %home%\OpenSSL
call ms\mingw32.bat no-asm 2>&1 | %tee% '%home%\OpenSSL.log'
This looks a bit more tortured than it needs to be. Basically I just need to launch a BASH shell to run the configure script. That bit of extra Kung-Fu is just restoring the PWD.
set home=C:\msys\1.0\src\bitcoin-0.1.5
set path=C:\MinGW\mingw32\bin;C:\MinGW\bin;C:\msys\1.0\bin;%path%
cd /d %home%\DB\build_unix
sh --login -c "cd '%cd%';../dist/configure --enable-mingw --enable-cxx" 2>&1 | tee '%home%\DB.log'
make.exe 2>&1 | tee -a '%home%\DB.log'
It's about as simple as you can get... which is why I'm perplexed that this build seems to have been the root of my current issue. Hopefully I'll find root cause soon.
set home=C:\msys\1.0\src\bitcoin-0.1.5
set path=C:\MinGW\mingw32\bin;C:\MinGW\bin;C:\Perl58\bin;%path%
set tee=C:\msys\1.0\bin\tee.exe
cd /d %home%\wxWidgets\build\msw
mingw32-make -f makefile.gcc 2>&1 | %tee% '%home%\wxWidgets.log'
Buckle up. Boost takes about two hours to build on my VM. The build isn't perfect either. Attempted about 4000 targets, skipped 56, and failed 96 of them. Some of those targets were due to the fact that I didn't install a 64-bit cross-compiler, so I assumed they are expected. The build requires bjam which is in my download list, but it is easy to miss.
set home=C:\msys\1.0\src\bitcoin-0.1.5
set path=C:\MinGW\mingw32\bin;C:\MinGW\bin;C:\Perl58\bin;%path%
set tee=C:\msys\1.0\bin\tee.exe
cd /d %home%\Boost
bjam\bjam toolset=gcc --build-type=complete stage 2>&1 | %tee% '%home%\Boost.log'
Again... looks a bit complicated, but the shuffling of the subst command is analogous to a chroot command in linux. It simply changes where the root directory is. The bitcoin make file looks for the dependencies in the root directory. This is just a way for me to keep them in a subfolder until it is time to build. I doubt this is the cause of my failures, but I can move things around later I suppose.
Found two errors in Makefile that I can workaround with the two robocopy commands now included.
set home=C:\msys\1.0\src\bitcoin-0.1.5
set path=C:\MinGW\mingw32\bin;C:\MinGW\bin;C:\Perl58\bin;%path%
set tee=C:\msys\1.0\bin\tee.exe
if exist s:\ subst s: /d
subst s: %home%
cd /d s:\
robocopy /s /OpenSSL/outinc /OpenSSL/include
robocopy /s /wxWidgets/lib/gcc_lib/mswd /wxWidgets/lib/vc_lib/mswd
if not exist \obj mkdir \obj
if not exist \out mkdir \out
mingw32-make bitcoin.exe -f makefile 2>&1 | %tee% '%home%\bitcoin.log'
copy \bitcoin.exe \out
copy \OpenSSL\libeay32.dll \out
copy C:\MinGW\bin\mingwm10.dll \out
subst s: /d
Found two errors in Makefile that I can workaround with the two robocopy commands now included. No more failures, the vintage bitcoin.exe is up and running.
Although I'm able to get all the dependencies to build, bitcoin.exe is still failing. It starts with some errors on /wxWidgets, and just cascades from there.
g++ -c -mthreads -O0 -w -Wno-invalid-offsetof -Wformat -g -D__WXDEBUG__ -DWIN32 -D__WXMSW__ -D_WINDOWS -DNOPCH -I"/boost" -I"/DB/build_unix" -I"/OpenSSL/include" -I"/wxWidgets/lib/vc_lib/mswd" -I"/wxWidgets/include" -o headers.h.gch headers.h
In file included from /wxWidgets/include/wx/defs.h:21,
from /wxWidgets/include/wx/wx.h:15,
from headers.h:15:
/wxWidgets/include/wx/platform.h:196:22: wx/setup.h: No such file or directory
In file included from /wxWidgets/include/wx/platform.h:293,
from /wxWidgets/include/wx/defs.h:21,
from /wxWidgets/include/wx/wx.h:15,
from headers.h:15:
/wxWidgets/include/wx/chkconf.h:103:9: #error "wxUSE_DYNLIB_CLASS must be defined."
/wxWidgets/include/wx/chkconf.h:111:9: #error "wxUSE_EXCEPTIONS must be defined."
/wxWidgets/include/wx/chkconf.h:119:9: #error "wxUSE_FILESYSTEM must be defined."
/wxWidgets/include/wx/chkconf.h:127:9: #error "wxUSE_FS_ARCHIVE must be defined."
I do have the following archived, but you should do the same. You never know when the maintainer will take the old copies down. This happened with perl (ActivePerl) which now requires a membership to access old releases