main.o file not recognized in libprotobuf during Gitian(VirtualBox) build of protobuf-win.yml #3766

issue int03h opened this issue on February 28, 2014
  1. int03h commented at 12:23 AM on February 28, 2014: none

    I rebuilt everything over the last few days .. and doing a new build from scratch I get this error on the last .yml of the Gitian build process via Virtualbox.

    /bin/gbuild ../bitcoin/contrib/gitian-descriptors/protobuf-win.yml --- Building for precise amd64 --- Stopping target if it is up 0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...100% Making a new image copy Restoring snapshot 1f6cb3b2-dc04-4a26-8f8d-d1a6433a014a 0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...100% Starting target Checking if target is upWaiting for VM "Gitian-precise-amd64" to power on... .VM "Gitian-precise-amd64" has been successfully started. .... Preparing build environment protobuf-2.5.0.tar.bz2 100% 1823KB 1.8MB/s 00:00 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 x86_64 bash -x < var/build-script > var/build.log 2>&1 (RuntimeError) from ./bin/gbuild:116:inbuild_one_configuration' from ./bin/gbuild:218:in block (2 levels) in <main>' from ./bin/gbuild:213:ineach' from ./bin/gbuild:213:in block in <main>' from ./bin/gbuild:211:ineach' from ./bin/gbuild:211:in `<main>'

    BUILD.LOG OUTPUT make[2]: Entering directory /home/ubuntu/build32/protobuf-2.5.0/src' /bin/bash ../libtool --tag=CXX --mode=link g++ -pthread -Wall -Wwrite-strings -Woverloaded-virtual -Wno-sign-compare -frandom-seed=11 -O2 -pthread -o protoc main.o -lpthread libprotobuf.la libprotoc.la libtool: link: g++ -pthread -Wall -Wwrite-strings -Woverloaded-virtual -Wno-sign-compare -frandom-seed=11 -O2 -pthread -o protoc main.o -lpthread ./.libs/libprotobuf.a ./.libs/libprotoc.a /home/ubuntu/build32/protobuf-2.5.0/src/.libs/libprotobuf.a -pthread main.o: file not recognized: File format not recognized collect2: ld returned 1 exit status make[2]: *** [protoc] Error 1 make[2]: Leaving directory/home/ubuntu/build32/protobuf-2.5.0/src' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/home/ubuntu/build32/protobuf-2.5.0' make: *** [all] Error 2

    Suggestions ?

  2. int03h commented at 12:25 AM on February 28, 2014: none

    FYI on the "new" files created:

    " f29b7d9577417333fb56e023c2977f5726a7c297f320b175a4108cf7cd4c2d29 boost-linux32-1.55.0-gitian-r1.zip 88232451c4104f7eb16e469ac6474fd1231bd485687253f7b2bdf46c0781d535 boost-linux64-1.55.0-gitian-r1.zip 58c99ecca2015e1264ace3a10b16141cdc73cf530f99c72d9dde92dadb072e12 boost-res.yml

    05fe8e9aef00d295f24a94deef7d3a918af5aeef371ba57fdd5a6acd8c51f6cb bitcoin-deps-linux32-gitian-r3.zip 4227aa9d9fedbb4265b8d10a4f78b7435f34b00a54eb4d662bf78f59c6e70c27 bitcoin-deps-linux64-gitian-r3.zip 2dbed7feef867c57fe65a28445ae29bb5702f87a13f05a4cf36bb413199dea50 bitcoin-res.yml

    9cfeb44a272aff79ff076cb3944f174e17a4a2575a678e116261e56e5a2831a5 boost-win32-1.55.0-gitian-r6.zip 868252dd1938d614a3a64b97bf22877f986c82addba3f6185cc27b75ef756329 boost-win64-1.55.0-gitian-r6.zip 52e1d0c078673d85a7de0a47c297233581287726d0e0afe222dd27b872604551 boost-res.yml

    0dd97cbf2548e1b31a00b9a6de9d3f91465bc53c7f6cfb619acbe069f3a6945e bitcoin-deps-win32-gitian-r10.zip b3fdd09dd82f3a9969f5bbcdf5ff13482d72f9baa88d98fa55fe78fec8db8a30 bitcoin-deps-win64-gitian-r10.zip 9ad7ee405a241e1d7779bb4fe6e47e2cfa0f3bc4b149f16641b2eb025a9a9c06 bitcoin-deps-res.yml

    9cfeb44a272aff79ff076cb3944f174e17a4a2575a678e116261e56e5a2831a5 qt-win32-5.2.0-gitian-r2.zip 868252dd1938d614a3a64b97bf22877f986c82addba3f6185cc27b75ef756329 qt-win64-5.2.0-gitian-r2.zip 28fdb844c383047c01620bd7f9b432cee2d7db2955c1c1dc231e129f039a2685 qt-res.yml "

  3. laanwj commented at 8:40 AM on February 28, 2014: member

    That error message usually means that windows/linux targets are being linked together.

  4. laanwj commented at 8:43 AM on February 28, 2014: member

    Are you, by chance, not cleaning up the VM's home directory between gitian runs?

    I could see this happen in the following case

    • Gitian protobuf
      • Extract
      • Configure for linux
      • Builds linux tools like protoc
      • Distclean
      • Configure for windows
      • Builds windows libraries
    • Gitian protobuf
      • Extract
      • Configure for linux
      • Builds linux tools like protoc !!COLLISION!! with previous windows objects
  5. laanwj added the label Build system on Feb 28, 2014
  6. int03h commented at 5:43 PM on February 28, 2014: none

    Yep. Dirty Dirty VM is the culprit. Musta done something to mess up Gitian-clean. Thanks. Closing.

  7. int03h closed this on Feb 28, 2014

  8. MarcoFalke locked this on Sep 8, 2021
Contributors

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-26 12:15 UTC

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