Update Bitcoin to use OpenSSL 1.0.1c

[fanquake]

I noticed that 0.7.0 for OSX is compiled with 1.0.1c, so I thought it might be an idea to update the makefiles, readme etc. I'm assuming that theres no reason that unix and windows builds cannot use 1.0.1b.

[Diapolo]

I've been using 1.0.1c for my own Windows builds for months and have not found any problems with it.

[Diapolo]

We are at 1.50 for Windows AFAIK? Perhaps you can create another small patch for this.

[Diapolo]

Thanks :), looks good.

[BitcoinPullTester]

Automatic sanity-testing: FAILED BUILD/TEST, see http://jenkins.bluematt.me/pull-tester/b7a8802c2acd61394b63856d7ff7ca942df81a00 for binaries and test log.

This could happen for one of several reasons:

1. It chanages paths in makefile.linux-mingw or otherwise changes build scripts in a way that made them incompatible with the automated testing scripts
2. It does not build on either Linux i386 or Win32 (via MinGW cross compile)
3. The test suite fails on either Linux i386 or Win32
4. The block test-cases failed (lookup the first bNN identifier which failed in https://github.com/TheBlueMatt/test-scripts/blob/master/FullBlockTestGenerator.java)

[laanwj]

Please increase the deps version number, ie to bitcoin-deps-0.0.5.zip (both in deps-win32.yml and gitian-win32.yml)

[BitcoinPullTester]

Automatic sanity-testing: FAILED BUILD/TEST, see http://jenkins.bluematt.me/pull-tester/05c1c08e295f067a5fbd32fb7ad80fe01d2aa49d for binaries and test log.

This could happen for one of several reasons:

1. It chanages paths in makefile.linux-mingw or otherwise changes build scripts in a way that made them incompatible with the automated testing scripts
2. It does not build on either Linux i386 or Win32 (via MinGW cross compile)
3. The test suite fails on either Linux i386 or Win32
4. The block test-cases failed (lookup the first bNN identifier which failed in https://github.com/TheBlueMatt/test-scripts/blob/master/FullBlockTestGenerator.java)

[laanwj]

Ok great,

Looks like @TheBlueMatt's has to install openssl1.0.1c in /mnt/mingw/openssl-1.0.1c, before the pull tester can test this.

[sipa]

I think 1.5.0 is not the same thing as 1.50.0.

[Diapolo]

You are right, should be 1.50.0.

[fanquake]

Sorry, I'll correct that

[BitcoinPullTester]

Automatic sanity-testing: FAILED BUILD/TEST, see http://jenkins.bluematt.me/pull-tester/9cde889992e16527c99c262831292b944a2faabe for binaries and test log.

This could happen for one of several reasons:

1. It chanages paths in makefile.linux-mingw or otherwise changes build scripts in a way that made them incompatible with the automated testing scripts
2. It does not build on either Linux i386 or Win32 (via MinGW cross compile)
3. The test suite fails on either Linux i386 or Win32
4. The block test-cases failed (lookup the first bNN identifier which failed in https://github.com/TheBlueMatt/test-scripts/blob/master/FullBlockTestGenerator.java)

[fanquake]

Closing this.
Will merge all into a single commit in a new pull.

[laanwj]

You don't need to close your pull for that. You can just "rebase -i", squash the commits and push -f to the current branch.

[fanquake]

I would have. But those commits were in the master branch, instead of a separate one. I've been meaning to start using branches for pulls for a while now, so thought I might just sort myself out and do that instead.

[TheBlueMatt]

1.0.0c build for pull-tester, should test properly now.