./bin/gbuild ../bitcoin/contrib/gitian-descriptors/deps-linux.yml - fails on Checksum of MiniuPnP #3725

issue int03h opened this issue on February 21, 2014
  1. int03h commented at 7:25 PM on February 21, 2014: none

    I successfully built boost but now when I try to do the deps it fails. I am using a current clone of the github repo. Am I doing something wrong ? Looks like the checksum on miniupnp is a mismatch to what the yml is expecting ?

    root@miner2:/bitcoin/gitian-builder# ./bin/gbuild ../bitcoin/contrib/gitian-descriptors/deps-linux.yml --- Building for precise i386 --- Stopping target if it is up 0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...100% Making a new image copy Restoring snapshot 4d8aabff-34c8-46f6-b6a3-5aa3de6b06f7 0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...100% Starting target Checking if target is upWaiting for VM "Gitian-precise-i386" to power on... VM "Gitian-precise-i386" has been successfully started. . Preparing build environment openssl-1.0.1e.tar.gz 100% 4355KB 4.3MB/s 00:00 miniupnpc-1.8.tar.gz 100% 111 0.1KB/s 00:00 qrencode-3.4.3.tar.bz2 100% 362KB 362.0KB/s 00:00 protobuf-2.5.0.tar.bz2 100% 1823KB 1.8MB/s 00:00 db-4.8.30.NC.tar.gz 100% 22MB 10.9MB/s 00:02 Updating apt-get repository (log in var/install.log) Installing additional packages (log in var/install.log) Grabbing package manifest Creating build script (var/build-script) Running build script (log in var/build.log) ./bin/gbuild:21:in system!': failed to run on-target setarch i386 bash -x < var/build-script > var/build.log 2>&1 (RuntimeError) from ./bin/gbuild:116:inbuild_one_configuration' from ./bin/gbuild:218 from ./bin/gbuild:213:in each' from ./bin/gbuild:213 from ./bin/gbuild:211:ineach' from ./bin/gbuild:211

    Here is the output from : build.log

    root@miner2:/bitcoin/gitian-builder/var# more build.log

    • set -e
    • umask 002
    • export OUTDIR=/home/ubuntu/out
    • OUTDIR=/home/ubuntu/out
    • GBUILD_BITS=32
    • MAKEOPTS=(-j2)
    • REFERENCE_DATETIME='2013-06-01 00:00:00'
    • REFERENCE_DATE=2013-06-01
    • REFERENCE_TIME=00:00:00
    • cd build
    • STAGING=/home/ubuntu/install
    • TEMPDIR=/home/ubuntu/tmp
    • OPTFLAGS=-O2
    • export LD_PRELOAD=/usr/lib/faketime/libfaketime.so.1
    • LD_PRELOAD=/usr/lib/faketime/libfaketime.so.1
    • export 'FAKETIME=2013-06-01 00:00:00'
    • FAKETIME='2013-06-01 00:00:00'
    • export TZ=UTC
    • TZ=UTC
    • export LIBRARY_PATH=/home/ubuntu/install/lib
    • LIBRARY_PATH=/home/ubuntu/install/lib
    • sha256sum -c
    • echo 'f74f15e8c8ff11aa3d5bb5f276d202ec18d7246e95f961db76054199c69c1ae3 openss l-1.0.1e.tar.gz' openssl-1.0.1e.tar.gz: OK
    • sha256sum -c
    • echo 'bc5f73c7b0056252c1888a80e6075787a1e1e9112b808f863a245483ff79859c miniup npc-1.8.tar.gz' miniupnpc-1.8.tar.gz: FAILED sha256sum: WARNING: 1 computed checksum did NOT match <<<<<<<<<<<====== ?

    This worked great BTW : f29b7d9577417333fb56e023c2977f5726a7c297f320b175a4108cf7cd4c2d29 boost-linux32- 1.55.0-gitian-r1.zip 88232451c4104f7eb16e469ac6474fd1231bd485687253f7b2bdf46c0781d535 boost-linux64- 1.55.0-gitian-r1.zip cb74aa9a75b8ffdc22391397a9725ebf8d2da9a1e4cf5addc3640ba56ce8fe93 boost-res.yml Done.

  2. laanwj commented at 7:42 PM on February 21, 2014: member

    Where did you get that miniupnpc-1.8.tar.gz? Mine is:

    bc5f73c7b0056252c1888a80e6075787a1e1e9112b808f863a245483ff79859c  miniupnpc-1.8.tar.gz
    

    I've also tried re-downloading the file mentioned in the release process ( http://miniupnp.free.fr/files/download.php?file=miniupnpc-1.8.tar.gz ), running sha256sum and it matches this.

  3. laanwj commented at 7:46 PM on February 21, 2014: member

    BTW your boost-linux*.zip mismatch mine:

    149a464f02aa809a340306d13fc0ecb1a347057ca99daf846100e7e3c53d85c2  boost-linux32-1.55.0-gitian-r1.zip
    c47bc1a5ffa5097c10280fb2fffb462a925cac5873c4ce7268e404281bddd133  boost-linux64-1.55.0-gitian-r1.zip
    

    What build environment did you use? KVM, Virtualbox or LXC? Can you upload the boost-linux32 zip somewhere so that I can compare what is different?

  4. int03h commented at 8:01 PM on February 21, 2014: none

    Files here : http://miner.frimmel.net:81/files/bitcoin/ - I punched a hole out for you .. this wont be a permalink .. these are a copy of whats in my inputs dir. I used Gavins instructions on his blog. I have Saucy (Xubuntu) as the build machine and 2 Precise (SRV) - clean installs - PRECISELY following the instructions here : http://gavintech.blogspot.com/2014/02/gitian-building-bitcoin-releases.html

    EDIT: I got the miniupnpc from where it says in the release process doc.. i.e. what you said. I wgot it again and its the same.

    root@miner2:/var/www/files/bitcoin# ls boost_1_55_0.tar.bz2 miniupnpc-1.8.tar.gz boost-linux32-1.55.0-gitian-r1.zip openssl-1.0.1e.tar.gz boost-linux64-1.55.0-gitian-r1.zip protobuf-2.5.0.tar.bz2 boost-mingw-gas-cross-compile-2013-03-03.patch qrencode-3.4.3.tar.bz2 db-4.8.30.NC.tar.gz zlib-1.2.8.tar.gz

    root@miner2:/var/www/files/bitcoin# sha256sum miniupnpc-1.8.tar.gz d7ee97b99c96c6fe689a3f7b2ddeb4729f1aefedf7c177928ff6da100d92ff78 miniupnpc-1.8.tar.gz

  5. laanwj commented at 8:09 PM on February 21, 2014: member

    Do I see correctly that your miniupnpc is only 111 bytes? This should be 70624. Probably it contains an error message and something went wrong while downloading.

  6. laanwj commented at 8:16 PM on February 21, 2014: member

    Difference in the boost result seems to be in boost_iostreams. Yours has some zlib-related files where mine have not;

    $ ar tv a/lib/libboost_iostreams-mt.a                                               
    rw-r--r-- 0/0  44424 Jan  1 01:00 1970 file_descriptor.o
    rw-r--r-- 0/0  40104 Jan  1 01:00 1970 mapped_file.o
    
    $ ar tv b/lib/libboost_iostreams-mt.a 
    rw-r--r-- 0/0  44424 Jan  1 01:00 1970 file_descriptor.o
    rw-r--r-- 0/0  40104 Jan  1 01:00 1970 mapped_file.o
    rw-r--r-- 0/0  22488 Jan  1 01:00 1970 gzip.o
    rw-r--r-- 0/0  34032 Jan  1 01:00 1970 zlib.o
    

    We had a similar problem with protobuf. It's annoying and I'll take a look if I can fix boost configuration to use a normalized setting here.

    However this should not affect the resutling executable.

  7. laanwj added the label Docs and Output on Feb 21, 2014
  8. int03h commented at 8:31 PM on February 21, 2014: none

    Copy and Paste issue .. damn. I copied it out of the process doc into a windows notepad doc .. bet it put a carriage return in there somewhere instead of a line break .. whatever.. sorry. Got the file and checksums fine. I will let you know how the rest goes in terms of checksums. @laanwj Thank you for your help! I appreciate it!

  9. int03h commented at 8:35 PM on February 21, 2014: none

    From Gavins document this is the build environment it setups up :

    sudo apt-get install autoconf2.13 automake build-essential bsdmainutils faketime g++ g++-mingw-w64 git-core libqt4-dev libtool libz-dev mingw-w64 nsis pciutils pkg-config psmisc subversion unzip zip

    note libz-dev ..

  10. laanwj commented at 8:41 PM on February 21, 2014: member

    Yes -- zlib-dev is needed for buildling the windows qt dependency. This is a difference between build environments. For LXC/KVM gitian only installs the packages that are needed, for Virtualbox you install all the packages for all the dependencies at once.

    Can you re-try building boost with the descriptor from #3726? You should get the same output as me with that.

  11. int03h commented at 12:31 AM on February 22, 2014: none

    Hmm .. looks like the same hashes as what I got previous at the top of the thread.

    http://miner.frimmel.net:81/files/bitcoin/

    f29b7d9577417333fb56e023c2977f5726a7c297f320b175a4108cf7cd4c2d29 boost-linux32-1.55.0-gitian-r1.zip 88232451c4104f7eb16e469ac6474fd1231bd485687253f7b2bdf46c0781d535 boost-linux64-1.55.0-gitian-r1.zip cb74aa9a75b8ffdc22391397a9725ebf8d2da9a1e4cf5addc3640ba56ce8fe93 boost-res.yml

    How do I merge that pull request you made #3726 into my build environment ? I am very new to GIT. I am assuming it didin't pull in since I have the same checksum for both.

  12. int03h commented at 2:29 AM on February 22, 2014: none

    I c .. you merged it into your own github repo .. gosh.. soo much to learn. sorry.. I am noob trash.

  13. laanwj commented at 7:08 AM on February 22, 2014: member

    The easiest (AFAIK) way to get my exact tree would be:

    git remote add laanwj https://github.com/laanwj/bitcoin.git
    git fetch laanwj
    git checkout laanwj/2012_02_gitian_linux_boost_nozlib
    
  14. laanwj commented at 7:09 AM on February 22, 2014: member

    But don't bother: I'm going to fix this the other way around: enable, not disable zlib for all boost builds. So your build is already valid.

  15. int03h commented at 2:25 PM on February 23, 2014: none

    Success! (someone should have warned me not to attempt to compile this on an abacus :) ) . anyhow this may be useful (?) :

    f29b7d9577417333fb56e023c2977f5726a7c297f320b175a4108cf7cd4c2d29 boost-linux32-1.55.0-gitian-r1.zip 88232451c4104f7eb16e469ac6474fd1231bd485687253f7b2bdf46c0781d535 boost-linux64-1.55.0-gitian-r1.zip cb74aa9a75b8ffdc22391397a9725ebf8d2da9a1e4cf5addc3640ba56ce8fe93 boost-res.yml

    05fe8e9aef00d295f24a94deef7d3a918af5aeef371ba57fdd5a6acd8c51f6cb bitcoin-deps-linux32-gitian-r3.zip 4227aa9d9fedbb4265b8d10a4f78b7435f34b00a54eb4d662bf78f59c6e70c27 bitcoin-deps-linux64-gitian-r3.zip 09f0303520ed34d858ca39a74fbeb027b9cc10bfc5ee0e113d5956640e16d429 bitcoin-res.yml

    60dc2d3b61e9c7d5dbe2f90d5955772ad748a47918ff2d8b74e8db9b1b91c909 boost-win32-1.55.0-gitian-r6.zip f65fcaf346bc7b73bc8db3a8614f4f6bee2f61fcbe495e9881133a7c2612a167 boost-win64-1.55.0-gitian-r6.zip 3e272e350b4b8aabc7af9a3eff608f5d47e75ce3421151322ac57b2d91657552 boost-res.yml 0ba0855e1084132d05fd8687c19d8430b91f6c410a9ab7938e4fea650c2b22c8 bitcoin-deps-win32-gitian-r10.zip 5f9ffba0c13ddefc1d339f66ab973ea64623c9cc1f9078cb2b145bce86bd28e2 bitcoin-deps-win64-gitian-r10.zip 73b47fec50f09af8d9bd8bb413c6defb226ee68f6978fd0ddd8813ff9d4351ab bitcoin-deps-res.yml

    963e3e5e85879010a91143c90a711a5d1d5aba992e38672cdf7b54e42c56b2f1 qt-win32-5.2.0-gitian-r2.zip 751c579830d173ef3e6f194e83d18b92ebef6df03289db13ab77a52b6bc86ef0 qt-win64-5.2.0-gitian-r2.zip 0f1b5b0e34616342d0edd44bffa3d932e2206eaae37ec947bbb9fb4ddb48f5a0 qt-res.yml

    fa15886536e71b9ca0c66a2a11a93aecfbaf45d2e220794501dafdfe3be584e5 protobuf-win32-2.5.0-gitian-r4.zip fe1b4270217ee21eaf0eb1f1dfa8091f9ccb51522897b6eb3bf6765595ffeea4 protobuf-win64-2.5.0-gitian-r4.zip c3542c5d85d51f9159fec1b24feebd838555924f2a8ea0dc021ee48f38f73906 protobuf-win32-res.yml da7cadd78ad5c3763e6d2e7dc9a3d0afcaced2d439b575a568970256382ce0fa bin/32/bitcoin-cli a629e96fbdfb098ba19b1b61d8952746af419cf4063f7eafbc29c5a44e9406c5 bin/32/bitcoin-qt d9125a96cd8d4e06ed50276be69ab89c07284d90d2798ddcf24d099eb3776295 bin/32/bitcoind 6e0e46dbd4d5e1b05c945a79ecf50309dd33d5e2516c8e845848e810133dd29c bin/32/test_bitcoin 2d73d2137351214a9367ba3ecf005b9f9b5ffd6372f69f0364f92d567261efb0 bin/32/test_bitcoin-qt 71c44d0d7216a39c2b288ab73d3347f3a6ae51779e1016268a84b484f7b3c748 bin/64/bitcoin-cli 2c651a21d00e574bd6b32d77e15aa2b0606e2d2be05a24e4341173854b8313b6 bin/64/bitcoin-qt b7e01520c9c19ab79a3bfdb23636626d1cbe08c47831c0b4533aad71bbf5303c bin/64/bitcoind a0d54931779731d21ee345fb29bfd0819ee6a1a43db2b6946c6dbb8e8cff8e47 bin/64/test_bitcoin f5f8f8db2e7a12e9ec07bb219201debf004e5d68d2f80e57eed6a1022be4f4f9 bin/64/test_bitcoin-qt ad22b03560c546c3a5a6d2fc5f522e3232a5cc75b5b9bca67e1cb925c06fada6 src/bitcoin-0.9.0.tar.gz 92db0bdb21a2bbf6b0864872614fadf86a10fce348c8441a371ebdc16d37e5da bitcoin-res.yml

    c1b1cdee999e4070cd7c8488791262c04b65afcee4cae739be3805d5f43e92a3 32/bitcoin-0.9.0-win32-setup.exe 9617c72f35a56984d4b3a14501fd9a2e6e4f5dca8628034269aa6c4473dc8c9c 32/bitcoin-cli.exe 890a29d4cb51ff99fbd75e93d8b3ad4a89b077734656cd17e387e0a154a998a9 32/bitcoin-qt.exe 9cae6a375b52a81eb9c1e550e82092fd5ee8f25ed129b46712b36e97bb5479d7 32/bitcoind.exe 4fac5a4964c5a1178fcbe45b54277826fa6d713877bee44a8d4732e4c1e92969 32/test_bitcoin-qt.exe a3dec7188e91406fd3ec4e540a39f01cb43ae2c5a4e3d6ed29eb577f36f6da63 32/test_bitcoin.exe 40c8a1d3bafa3c91c79863d47cc71dff38dd24ecccee56a2c33cd601f3e3e54b 64/bitcoin-0.9.0-win64-setup.exe 25043f564a23d820b686880b0466e61fa3731d7b707d64bd6b90710f666b9384 64/bitcoin-cli.exe 9a9410164b0b4ae67b2fdfdac26c7e53dcdfd83b6ca9fca24fd4a9172d3f2419 64/bitcoin-qt.exe d0e1ae188e0fc14d2a99ff201803cacef548be33987758bcef3b487bfaabc688 64/bitcoind.exe 09a64d597bbba37a2e18de1606a17fa7d711ed688655fea7b4766ef778672d21 64/test_bitcoin-qt.exe 7376ebb36f42e224cc3b26fd2085d4da0eb012aace9f2bbad9479b19470f1c72 64/test_bitcoin.exe ad22b03560c546c3a5a6d2fc5f522e3232a5cc75b5b9bca67e1cb925c06fada6 src/bitcoin-0.9.0.tar.gz 0119fc3a18bf8c7f84373aefb4b6acebdc762022ee793a9ab12e30319b859c0f bitcoin-res.yml

    Close the ticket if your side is squared away.

  16. int03h commented at 2:35 PM on February 23, 2014: none

    Confirmed installed and running on Windows 8.1 - using 64 bit installer as per above.

  17. int03h commented at 5:46 PM on February 23, 2014: none

    Using a0d54931779731d21ee345fb29bfd0819ee6a1a43db2b6946c6dbb8e8cff8e47 bin/64/test_bitcoin I get the following errors: (its all greek to me) but thought it might be something you guys need to look at) :

    Running 110 test cases... accounting_tests.cpp(60): error in "acc_orderupgrade": check results[0].nTime == 1333333333 failed accounting_tests.cpp(63): error in "acc_orderupgrade": check results[2].nTime == 1333333336 failed accounting_tests.cpp(64): error in "acc_orderupgrade": check results[2].strOtherAccount == "c" failed accounting_tests.cpp(75): error in "acc_orderupgrade": check pwalletMain->nOrderPosNext == 4

    -snip-

    UPDATE: Resolved with new master.

  18. laanwj commented at 7:09 AM on February 24, 2014: member

    Regarding the test errors: Can you retry building bitcoin (not the dependencies) with a newer version of master with d5f1e72 in it? That commit fixes mingw formatting issues.

  19. laanwj commented at 7:15 AM on February 24, 2014: member

    For the rest the dependencies match except protobuf for win32:

    You have:

    fa15886536e71b9ca0c66a2a11a93aecfbaf45d2e220794501dafdfe3be584e5 protobuf-win32-2.5.0-gitian-r4.zip
    fe1b4270217ee21eaf0eb1f1dfa8091f9ccb51522897b6eb3bf6765595ffeea4 protobuf-win64-2.5.0-gitian-r4.zip
    

    I have:

    0fd5750d740ec0086b7af65375d55904c5b7aad048271c4b6ad3569ea46fc4d7  protobuf-win32-2.5.0-gitian-r4.zip
    16d7857d06265c409f1770b4d86b8c8ebc325b3760987490039faa9284b7ae2e  protobuf-win64-2.5.0-gitian-r4.zip
    

    Could you upload these for comparison?

  20. int03h commented at 10:29 PM on February 24, 2014: none

    @laanwj update: 32-bit and 64-bit test_bitcoin.exe tested and working fine from a git clone of master a couple of hours ago.

  21. laanwj commented at 6:21 AM on February 25, 2014: member

    Re: protobuf difference: ok now that is obscure. There is one file that differs:

    Binary files a/host/bin/protoc and b/host/bin/protoc differ
    

    This is the protoc for the host. Looks like there is a difference in ordering in the symbols within the executable, libstdc++.so.6 and __gmon_start__ are swapped.

    Good to hear that the resulting executables are working fine! (not that a tool symbol ordering issue is expected to make any impact on the end product :).

  22. laanwj commented at 7:00 AM on February 25, 2014: member

    Can you try building protobuf-win depedency with the descriptor from #3742 ? I hope that fixes the nondetermnism.

  23. int03h commented at 4:34 PM on February 25, 2014: none

    Update in #3742. Lets close this since all issues are resolved. @laanwj thanks again!

  24. int03h closed this on Feb 25, 2014

  25. MarcoFalke locked this on Sep 8, 2021

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-13 18:16 UTC

This site is hosted by @0xB10C
More mirrored repositories can be found on mirror.b10c.me