[BTC-dev] What would happen if...

[Stanislav Datskovskiy]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Message follows.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.19 (GNU/Linux)

iQEcBAEBCgAGBQJVHzcFAAoJELmCKKABq//H+4cH/ifM/P2r/o3Ur8eQiAv6FXWJ
coELnTFiNNaQoQ8u7OsIJxjyKMtnK+rfQDksOv0pgvJJxRCCQ6ut1xBnXC8zGgph
CHHAJHkcrYN9jf8Y6+ern8zwCetPRiLhMe9cCSJzUB0Na2KGg6JQsn8pRE1qAuyG
JjuewZeaJsqhTwFctxoIYXPV90k4gYnZEujRvYNLYmKaluWCPQoCHOLCrpqeXCkR
0rt35xhVYKK4TieoL4Q92oeeUV4j/yYAW+V653mN47XlwEaWnj9cagA8WDg12Ebw
Di6Up6HTAh8hmE5F6QffH+SApGdfZRJwrJKgtmbC2zILOEg1jrThd0nod7nkFoQ=
=i2jv
-----END PGP SIGNATURE-----
-------------- next part --------------
So, what happens if we take the pseudo-static 'portatron' build and
try to run on 'pogotron' ?

Guess what:

# bitcoind 
-sh: bitcoind: not found

To old 'busybox' hand, this means missing dynamic deps:


# ldd /usr/bin/bitcoind
checking sub-depends for 'not found'
checking sub-depends for '/lib/libpthread.so.0'
        ld-uClibc.so.0 => /lib/ld-uClibc.so.0 (0xb6f0f000)
        libdl.so.0 => /lib/libdl.so.0 (0xb6f03000)
        libc.so.0 => /lib/libc.so.0 (0xb6eb6000)
checking sub-depends for 'not found'
checking sub-depends for 'not found'
checking sub-depends for '/lib/libgcc_s.so.1'
checking sub-depends for 'not found'
checking sub-depends for '/lib/libc.so.0'
        ld-uClibc.so.0 => /lib/ld-uClibc.so.0 (0xb6f9f000)
        libdl.so.2 => not found (0x00000000)
        libpthread.so.0 => /lib/libpthread.so.0 (0x00000000)
        libstdc++.so.6 => not found (0x00000000)
        libm.so.6 => not found (0x00000000)
        libgcc_s.so.1 => /lib/libgcc_s.so.1 (0x00000000)
        libc.so.6 => not found (0x00000000)
        libc.so.0 => /lib/libc.so.0 (0x00000000)
        /lib/ld-uClibc.so.0 => /lib/ld-uClibc.so.0 (0x00000000)

Sucks.


In unrelated news, tested a build of 'pogotron' containing mke2fs -
for the process described earlier (where, if disk does not contain a blockchain,
it first gets formatted before anything else happens.)

And guess what,

# mke2fs /dev/sda1
mke2fs: lseek: Value too large for defined data type

So far all I could find was 'busybox sucks, try other version' and other
lamer spew.

Looks like it will have to be dealt with.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: message.txt.sig
Type: application/octet-stream
Size: 490 bytes
Desc: not available
URL: <http://therealbitcoin.org/ml/btc-dev/attachments/20150403/message_01f02d621e4fd8db9e1b3ad0c3b569e9669eef96.txt.sig>