mttools: BuildPackages fails on first attempt |
||
Issue descriptionhttps://build.chromium.org/p/chromiumos/builders/oak-full/builds/2354/steps/BuildPackages/logs/stdio === Start output for job mttools-0.0.1-r121 (0m13.6s) === mttools-0.0.1-r121: >>> Emerging (1 of 1) chromeos-base/mttools-0.0.1-r121::chromiumos for /build/oak/ mttools-0.0.1-r121: * Running stacked hooks for pre_pkg_setup mttools-0.0.1-r121: * sysroot_build_bin_dir ... mttools-0.0.1-r121: [ ok ] mttools-0.0.1-r121: * Running stacked hooks for pre_src_unpack mttools-0.0.1-r121: * python_multilib_setup ... mttools-0.0.1-r121: [ ok ] mttools-0.0.1-r121: >>> Unpacking source... mttools-0.0.1-r121: Cloning into '/build/oak/tmp/portage/chromeos-base/mttools-0.0.1-r121/work/mttools-0.0.1'... mttools-0.0.1-r121: done. mttools-0.0.1-r121: >>> Source unpacked in /build/oak/tmp/portage/chromeos-base/mttools-0.0.1-r121/work mttools-0.0.1-r121: * Running stacked hooks for post_src_unpack mttools-0.0.1-r121: * asan_init ... mttools-0.0.1-r121: [ ok ] mttools-0.0.1-r121: >>> Preparing source in /build/oak/tmp/portage/chromeos-base/mttools-0.0.1-r121/work/mttools-0.0.1 ... mttools-0.0.1-r121: >>> Source prepared. mttools-0.0.1-r121: >>> Configuring source in /build/oak/tmp/portage/chromeos-base/mttools-0.0.1-r121/work/mttools-0.0.1 ... mttools-0.0.1-r121: >>> Source configured. mttools-0.0.1-r121: >>> Compiling source in /build/oak/tmp/portage/chromeos-base/mttools-0.0.1-r121/work/mttools-0.0.1 ... mttools-0.0.1-r121: make -j32 mttools-0.0.1-r121: OUT=. make -C mtreplay all mttools-0.0.1-r121: make[1]: Entering directory '/build/oak/tmp/portage/chromeos-base/mttools-0.0.1-r121/work/mttools-0.0.1/mtreplay' mttools-0.0.1-r121: cd "/build/oak/tmp/portage/chromeos-base/mttools-0.0.1-r121/work/mttools-0.0.1/mtreplay/" && make -r -I "/build/oak/tmp/portage/chromeos-base/mttools-0.0.1-r121/work/mttools-0.0.1/mtreplay" -f "/build/oak/tmp/portage/chromeos-base/mttools-0.0.1-r121/work/mttools-0.0.1/mtreplay/Makefile" SRC="/build/oak/tmp/portage/chromeos-base/mttools-0.0.1-r121/work/mttools-0.0.1/mtreplay" OUT="/build/oak/tmp/portage/chromeos-base/mttools-0.0.1-r121/work/mttools-0.0.1/mtreplay/" "all" mttools-0.0.1-r121: make[2]: Entering directory '/build/oak/tmp/portage/chromeos-base/mttools-0.0.1-r121/work/mttools-0.0.1/mtreplay' mttools-0.0.1-r121: build configuration: mttools-0.0.1-r121: - OUT=/build/oak/tmp/portage/chromeos-base/mttools-0.0.1-r121/work/mttools-0.0.1/mtreplay/ mttools-0.0.1-r121: - SRC=/build/oak/tmp/portage/chromeos-base/mttools-0.0.1-r121/work/mttools-0.0.1/mtreplay mttools-0.0.1-r121: - MODE=opt mttools-0.0.1-r121: - SPLITDEBUG=0 mttools-0.0.1-r121: - NOSTRIP=1 mttools-0.0.1-r121: - VALGRIND=0 mttools-0.0.1-r121: - COLOR=1 mttools-0.0.1-r121: - ARCH=arm mttools-0.0.1-r121: - QEMU_ARCH=arm mttools-0.0.1-r121: - SYSROOT=/build/oak mttools-0.0.1-r121: mttools-0.0.1-r121: + submodule: src mttools-0.0.1-r121: CXX src/main.cc -> src/main.pie.o mttools-0.0.1-r121: CXX src/main.cc -> src/main.pic.o mttools-0.0.1-r121: CXX src/evdev_gestures.cc -> src/evdev_gestures.pie.o mttools-0.0.1-r121: CXX src/evemu_device.cc -> src/evemu_device.pie.o mttools-0.0.1-r121: CXX src/evdev_gestures.cc -> src/evdev_gestures.pic.o mttools-0.0.1-r121: CXX src/evemu_device.cc -> src/evemu_device.pic.o mttools-0.0.1-r121: CXX src/gestures_mock.cc -> src/gestures_mock.pie.o mttools-0.0.1-r121: CXX src/libevdev_mock.cc -> src/libevdev_mock.pic.o mttools-0.0.1-r121: CXX src/libevdev_mock.cc -> src/libevdev_mock.pie.o mttools-0.0.1-r121: CXX src/trimmer.cc -> src/trimmer.pic.o mttools-0.0.1-r121: CXX src/trimmer.cc -> src/trimmer.pie.o mttools-0.0.1-r121: CXX src/gestures_mock.cc -> src/gestures_mock.pic.o mttools-0.0.1-r121: CXX src/replay_device.cc -> src/replay_device.pic.o mttools-0.0.1-r121: CXX src/replay_device.cc -> src/replay_device.pie.o mttools-0.0.1-r121: CXX src/stream.cc -> src/stream.pic.o mttools-0.0.1-r121: CXX src/stream.cc -> src/stream.pie.o mttools-0.0.1-r121: CXX src/prop_provider.cc -> src/prop_provider.pie.o mttools-0.0.1-r121: CXX src/prop_provider.cc -> src/prop_provider.pic.o mttools-0.0.1-r121: LDCXX replay mttools-0.0.1-r121: /usr/x86_64-pc-linux-gnu/armv7a-cros-linux-gnueabi/binutils-bin/2.25.51/ld.gold.real: error: cannot find -lglib-2.0 mttools-0.0.1-r121: collect2: error: ld returned 1 exit status mttools-0.0.1-r121: common.mk:424: recipe for target 'CXX_BINARY(replay)' failed mttools-0.0.1-r121: make[2]: *** [CXX_BINARY(replay)] Error 1 mttools-0.0.1-r121: make[2]: Leaving directory '/build/oak/tmp/portage/chromeos-base/mttools-0.0.1-r121/work/mttools-0.0.1/mtreplay' mttools-0.0.1-r121: common.mk:165: recipe for target 'CXX_BINARY(replay)' failed mttools-0.0.1-r121: make[1]: *** [CXX_BINARY(replay)] Error 2 mttools-0.0.1-r121: make[1]: Leaving directory '/build/oak/tmp/portage/chromeos-base/mttools-0.0.1-r121/work/mttools-0.0.1/mtreplay' mttools-0.0.1-r121: Makefile:18: recipe for target 'replay' failed mttools-0.0.1-r121: make: *** [replay] Error 2 mttools-0.0.1-r121: * __helpers_die: WARNING: emake failed mttools-0.0.1-r121: * ERROR: chromeos-base/mttools-0.0.1-r121::chromiumos failed (compile phase): mttools-0.0.1-r121: * command: emake mttools-0.0.1-r121: * mttools-0.0.1-r121: * Call stack: mttools-0.0.1-r121: * ebuild.sh, line 93: Called src_compile mttools-0.0.1-r121: * environment, line 3209: Called cros-workon_src_compile mttools-0.0.1-r121: * environment, line 696: Called cw_emake mttools-0.0.1-r121: * environment, line 1013: Called die mttools-0.0.1-r121: * The specific snippet of code: mttools-0.0.1-r121: * die "command: emake $*"; mttools-0.0.1-r121: * mttools-0.0.1-r121: * If you need support, post the output of `emerge --info '=chromeos-base/mttools-0.0.1-r121::chromiumos'`, mttools-0.0.1-r121: * the complete build log and the output of `emerge -pqv '=chromeos-base/mttools-0.0.1-r121::chromiumos'`. mttools-0.0.1-r121: * The complete build log is located at '/build/oak/tmp/portage/logs/chromeos-base:mttools-0.0.1-r121:20160314-071358.log'. mttools-0.0.1-r121: * For convenience, a symlink to the build log is located at '/build/oak/tmp/portage/chromeos-base/mttools-0.0.1-r121/temp/build.log'. mttools-0.0.1-r121: * The ebuild environment file is located at '/build/oak/tmp/portage/chromeos-base/mttools-0.0.1-r121/temp/environment'. mttools-0.0.1-r121: * Working directory: '/build/oak/tmp/portage/chromeos-base/mttools-0.0.1-r121/work/mttools-0.0.1' mttools-0.0.1-r121: * S: '/build/oak/tmp/portage/chromeos-base/mttools-0.0.1-r121/work/mttools-0.0.1' mttools-0.0.1-r121: >>> Failed to emerge chromeos-base/mttools-0.0.1-r121 for /build/oak/, Log file: mttools-0.0.1-r121: >>> '/build/oak/tmp/portage/logs/chromeos-base:mttools-0.0.1-r121:20160314-071358.log' mttools-0.0.1-r121: mttools-0.0.1-r121: * Messages for package chromeos-base/mttools-0.0.1-r121 merged to /build/oak/: mttools-0.0.1-r121: mttools-0.0.1-r121: * ERROR: chromeos-base/mttools-0.0.1-r121::chromiumos failed (compile phase): mttools-0.0.1-r121: * command: emake mttools-0.0.1-r121: * mttools-0.0.1-r121: * Call stack: mttools-0.0.1-r121: * ebuild.sh, line 93: Called src_compile mttools-0.0.1-r121: * environment, line 3209: Called cros-workon_src_compile mttools-0.0.1-r121: * environment, line 696: Called cw_emake mttools-0.0.1-r121: * environment, line 1013: Called die mttools-0.0.1-r121: * The specific snippet of code: mttools-0.0.1-r121: * die "command: emake $*"; mttools-0.0.1-r121: * mttools-0.0.1-r121: * If you need support, post the output of `emerge --info '=chromeos-base/mttools-0.0.1-r121::chromiumos'`, mttools-0.0.1-r121: * the complete build log and the output of `emerge -pqv '=chromeos-base/mttools-0.0.1-r121::chromiumos'`. mttools-0.0.1-r121: * The complete build log is located at '/build/oak/tmp/portage/logs/chromeos-base:mttools-0.0.1-r121:20160314-071358.log'. mttools-0.0.1-r121: * For convenience, a symlink to the build log is located at '/build/oak/tmp/portage/chromeos-base/mttools-0.0.1-r121/temp/build.log'. mttools-0.0.1-r121: * The ebuild environment file is located at '/build/oak/tmp/portage/chromeos-base/mttools-0.0.1-r121/temp/environment'. mttools-0.0.1-r121: * Working directory: '/build/oak/tmp/portage/chromeos-base/mttools-0.0.1-r121/work/mttools-0.0.1' mttools-0.0.1-r121: * S: '/build/oak/tmp/portage/chromeos-base/mttools-0.0.1-r121/work/mttools-0.0.1' === Complete: job mttools-0.0.1-r121 (0m13.6s) === Failed chromeos-base/mttools-0.0.1-r121 (in 0m13.6s), retrying later. ... Retrying emerge of chromeos-base/mttools-0.0.1-r121. Started chromeos-base/mttools-0.0.1-r121 (logged in /tmp/mttools-0.0.1-r121-p8_XrI) Completed chromeos-base/mttools-0.0.1-r121 (in 0m9.7s) WARNING: The following packages failed once or more, but succeeded upon retry. This might indicate incorrect dependencies. chromeos-base/mttools-0.0.1-r121 @@@STEP_WARNINGS@@@
,
Mar 14 2016
I checked, we do not need glib anymore. Not sure if we ever needed to be honest ;) djkurtz, fix is in the queue: https://chromium-review.googlesource.com/#/c/332209/
,
Mar 14 2016
The following revision refers to this bug: https://chromium.googlesource.com/chromiumos/platform/mttools/+/906f3a0a929968a8725e6a2dae7fe1b5f39f02c4 commit 906f3a0a929968a8725e6a2dae7fe1b5f39f02c4 Author: Dennis Kempin <denniskempin@chromium.org> Date: Mon Mar 14 16:05:41 2016 Remove dependency on glib-2.0 We linked against glib, but no longer need that dependency. BUG= chromium:594565 TEST=emerge mttools Change-Id: Iea13cca7f4f626bd6e60cc3e0fc6cef4672ef10a Reviewed-on: https://chromium-review.googlesource.com/332209 Commit-Ready: Dennis Kempin <denniskempin@chromium.org> Tested-by: Dennis Kempin <denniskempin@chromium.org> Reviewed-by: Andrew de los Reyes <adlr@chromium.org> [modify] https://crrev.com/906f3a0a929968a8725e6a2dae7fe1b5f39f02c4/mtreplay/src/module.mk
,
Mar 15 2016
https://chromegw.corp.google.com/i/chromiumos/builders/oak-full/builds/2360/steps/BuildPackages/logs/stdio mttools now builds on first attempt. |
||
►
Sign in to add a comment |
||
Comment 1 by adlr@chromium.org
, Mar 14 2016