gitian: add statically built variant of bitcoind/bitcoin-cli for linux build

laanwj commented at 11:09 am on March 20, 2014: member

This increases compatibility with older linux distributions.

 0  2943584 Mar 20 11:43 32/bitcoin-cli
 1  4376728 Mar 20 11:43 32/bitcoin-cli.static
 2  7748512 Mar 20 11:43 32/bitcoind
 3  9140856 Mar 20 11:43 32/bitcoind.static
 4 12164000 Mar 20 11:43 32/bitcoin-qt
 5  9740608 Mar 20 11:43 32/test_bitcoin
 6  8420256 Mar 20 11:43 32/test_bitcoin-qt
 7  3103728 Mar 20 11:53 64/bitcoin-cli
 8  4355112 Mar 20 11:53 64/bitcoin-cli.static
 9  7773680 Mar 20 11:53 64/bitcoind
10  8890088 Mar 20 11:53 64/bitcoind.static
11 12226032 Mar 20 11:53 64/bitcoin-qt
12  9860528 Mar 20 11:53 64/test_bitcoin
13  8457776 Mar 20 11:53 64/test_bitcoin-qt

A warning shown during build is:

0 warning: Using 'getaddrinfo' in statically linked applications requires at runtime the shared libraries from the glibc version used for linking

Note I have not explicitly disabled hardening/-pie in this build. This makes that the 32-bit version still has a dependency on dynamic libc.so even though it is statically linked:

0$ ldd 32/bitcoind.static
1    statically linked
2$ readelf -a 32/bitcoind.static |grep interpreter
3      [Requesting program interpreter: /usr/lib/libc.so.1]

~~Not sure how much of an issue this is on true 32-bit systems. It needs to be tested. This is not the case for the 64-bit build:~~

0$ ldd 64/bitcoind.static                                                       
1    not a dynamic executable
2$ readelf -a 64/bitcoind.static |grep interpreter
3(nothing)

Edit: v2: -pie now explicitly disabled for 32-bit build as it was unusable otherwise.

Tested on:

Debian 7.2 64-bit: OK (tested by me)
Ubuntu 10.04.4 LTS 64-bit: OK (tested by me)
Ubuntu 10.04.4 LTS 32-bit: OK (tested by me, v2)
CentOS 6.5 64bit: OK (tested by alexeft on forums and anton000, v2)
CentOS 6.5 32bit: OK (tested by anton000, v2)

laanwj commented at 11:19 am on March 20, 2014: member

I’ve uploaded the result here (temporary download URI only!):

https://download.visucore.com/bitcoin/bitcoin-0.9.0-linux-static-2.tar.gz https://download.visucore.com/bitcoin/bitcoin-0.9.0-linux-static-2.tar.gz.sig

laanwj commented at 1:00 pm on March 20, 2014: member

OK, whereas the 64-bit ones seem to work fine, the 32-bit static executables produced this way are absolutely broken. I have added a commit to disable -pie for 32-bit static executables, and updated the above downoad.

theuni commented at 5:45 pm on March 20, 2014: member

I’m still very hesitant on this approach. I’d be much more comfortable with picking a minimum required glibc version and wrapping symbols for newer versions. @laanwj What’s the minimum glibc you’ve got on any of those systems? I’ll see if I can work up a POC for the sake of discussion.

laanwj commented at 6:12 pm on March 20, 2014: member

Glibc 2.11 for Ubuntu 12.10, 2.12 for RH. But there were also problems with libc++ symbols…

anton000 commented at 9:44 pm on March 20, 2014: none

+1 thank you @laanwj for this! Currently running fine as daemon on CentOS 6.5 64bit :) Will try to fire up my 32bit centos box to test

edit: works fine on fully updated CentOS 6.5 32bit

laanwj commented at 9:05 am on March 21, 2014: member

Thanks for testing @anton000

ghost commented at 11:12 am on March 25, 2014: none

When will this be public? Need it to run 0.9 on debian.

laanwj commented at 11:21 am on March 25, 2014: member

When it’s ready.

In the meantime you can use and help testing the executables here or build your own.

ghost commented at 11:42 am on March 25, 2014: none

already did - runs perfectly on debian wheezy 64 bit.

theuni commented at 8:58 pm on March 25, 2014: member

@laanwj May as well go ahead and use this, since it fixes real-world problems in the short-term. I’ll keep looking into options for future releases… nothing I’ve come up with so far has been any more appealing.

gitian: add statically built variant of bitcoind/bitcoin-cli ddcd1afc5f

BitcoinPullTester commented at 9:05 am on March 26, 2014: none

Automatic sanity-testing: PASSED, see http://jenkins.bluematt.me/pull-tester/ddcd1afc5fdd148cd56f257b40a12f70841bd1b3 for binaries and test log. This test script verifies pulls every time they are updated. It, however, dies sometimes and fails to test properly. If you are waiting on a test, please check timestamps to verify that the test.log is moving at http://jenkins.bluematt.me/pull-tester/current/ Contact BlueMatt on freenode if something looks broken.

laanwj commented at 9:09 am on March 26, 2014: member

Squashed into one commit, removed special-case for 32/64 bit (-static -pie is invalid on all architectures).

theuni commented at 10:40 pm on March 27, 2014: member

@laanwj Please see https://github.com/theuni/bitcoin/tree/libc-compat . That should fix for 2.13. If the approach works as intended, I can move forward with the other symbols as well.

theuni commented at 0:01 am on March 28, 2014: member

Ok, hold on that. glibc behavior changed at some point, so some of my assumptions were wrong on the above. Looking again.

theuni commented at 3:54 am on March 28, 2014: member

Ok, fresh new idea is pushed up to https://github.com/theuni/bitcoin/tree/libc-compat

To use: ./configure –with-glibc-back-compat or –with-glibc-back-compat=X where X is glibc version 2.X.

The idea is to eventually be able to only enable the work-arounds needed for a specific version. For now, there’s only one enabled for 2.15.

laanwj commented at 10:50 am on March 28, 2014: member

@theuni so I can point my gitian build at that tree and generate testing executables (to try on the various platforms)? Just have to make sure I pass –with-glibc-back-compat ?

theuni commented at 4:24 pm on March 28, 2014: member

@laanwj Yes. Though, the only work-around included for now is for glibc 2.15, so it won’t help on anything older than that. If the approach works and seems reasonable, I can begin adding more.

theuni commented at 1:16 am on March 29, 2014: member

@laanwj Hold on that last one as well. I finally hit on a clean way of handling this, and the memcpy for 2.14 is resolved with it, so now the only concern is libstdc++.

If you’re ok with waiting a week or so, I’ll quit spamming here and just submit a PR that includes gitian descriptors once it’s nice and tidy.

laanwj commented at 1:53 am on March 29, 2014: member

By all means keep ‘spamming’ to keep us informed as you’re working on this, it’s nice to know what people are up to.

laanwj commented at 5:38 am on April 8, 2014: member

@theuni Because of the SSL heartbeat vulnerability we’d like to spin a 0.9.1 as soon as possible. It would be useful to have a portable executable in it, so I’d like to pull this now. This solution has been extensively tested. Your symbol-filtering based solution can be used for next release, however it needs testing first.

luke-jr commented at 6:20 am on April 8, 2014: member

@laanwj Huh? The heartbleed vuln doesn’t affect Bitcoin Core afaik?

laanwj commented at 8:28 am on April 8, 2014: member

@luke-jr The vulnerability does not affect the bitcoin protocol but may affect auxilary usage of TLS/HTTPS in RPC SSL and payment request fetching.

luke-jr commented at 8:34 am on April 8, 2014: member

Fetching too? I thought it was just server-side :(

ghost commented at 8:35 am on April 8, 2014: none

I think it would be good to release a 0.9.1 with the SSL bug patched.

laanwj referenced this in commit dac4e2aebd on Apr 8, 2014

laanwj merged this on Apr 8, 2014

laanwj closed this on Apr 8, 2014

laanwj deleted the branch on Apr 9, 2014

DrahtBot locked this on Sep 8, 2021

gitian: add statically built variant of bitcoind/bitcoin-cli for linux build #3914