New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 837794 link

Starred by 1 user

Issue metadata

Status: Verified
Owner:
Closed: Apr 2018
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 1
Type: Bug
Build-Toolchain



Sign in to add a comment

SimpleChromeArtifacts/TestsimpleChromeWorkflow broken on Chrome PFQ

Project Member Reported by tbarzic@chromium.org, Apr 27 2018

Issue description

https://cros-goldeneye.corp.google.com/chromeos/healthmonitoring/buildDetails?buildbucketId=8948068321109933168

From TestSimpleChromeWorkflow:
[8072/41469] SOLINK ./libmojo_core.so
FAILED: libmojo_core.so libmojo_core.so.TOC 
python "../../build/toolchain/gcc_solink_wrapper.py" --readelf="readelf" --nm="nm" --sofile="./libmojo_core.so" --tocfile="./libmojo_core.so.TOC" --output="./libmojo_core.so"  -- armv7a-cros-linux-gnueabi-clang++ -B/tmp/cbuildbot-tmpEny6M_/chrome-sdk-cacheiUTcyc/cache/chrome-sdk/tarballs/daisy+__b__c__cbuild__repository__buildbot_archive__daisy-chromium-pfq__R68-10624.0.0-rc1+target_toolchain/usr/x86_64-pc-linux-gnu/armv7a-cros-linux-gnueabi/binutils-bin/2.27.0-gold -Wno-unknown-warning-option -shared -fPIC -Wl,-z,noexecstack -Wl,-z,now -Wl,-z,relro -Wl,-z,defs -Wl,--no-as-needed -lpthread -Wl,--as-needed -fuse-ld=gold -B../../third_party/binutils/Linux_x64/Release/bin -Wl,--threads -Wl,--thread-count=4 -Wl,--icf=all --target=arm-linux-gnueabihf -Wl,-O2 -Wl,--gc-sections -Wl,--gdb-index --sysroot=../../../../../../../../../../../tmp/cbuildbot-tmpEny6M_/chrome-sdk-cacheiUTcyc/cache/chrome-sdk/tarballs/daisy+__b__c__cbuild__repository__buildbot_archive__daisy-chromium-pfq__R68-10624.0.0-rc1+sysroot_chromeos-base_chromeos-chrome.tar.xz -L../../../../../../../../../../../tmp/cbuildbot-tmpEny6M_/chrome-sdk-cacheiUTcyc/cache/chrome-sdk/tarballs/daisy+__b__c__cbuild__repository__buildbot_archive__daisy-chromium-pfq__R68-10624.0.0-rc1+sysroot_chromeos-base_chromeos-chrome.tar.xz/lib -Wl,-rpath-link=../../../../../../../../../../../tmp/cbuildbot-tmpEny6M_/chrome-sdk-cacheiUTcyc/cache/chrome-sdk/tarballs/daisy+__b__c__cbuild__repository__buildbot_archive__daisy-chromium-pfq__R68-10624.0.0-rc1+sysroot_chromeos-base_chromeos-chrome.tar.xz/lib -L../../../../../../../../../../../tmp/cbuildbot-tmpEny6M_/chrome-sdk-cacheiUTcyc/cache/chrome-sdk/tarballs/daisy+__b__c__cbuild__repository__buildbot_archive__daisy-chromium-pfq__R68-10624.0.0-rc1+sysroot_chromeos-base_chromeos-chrome.tar.xz/usr/lib -Wl,-rpath-link=../../../../../../../../../../../tmp/cbuildbot-tmpEny6M_/chrome-sdk-cacheiUTcyc/cache/chrome-sdk/tarballs/daisy+__b__c__cbuild__repository__buildbot_archive__daisy-chromium-pfq__R68-10624.0.0-rc1+sysroot_chromeos-base_chromeos-chrome.tar.xz/usr/lib -L../../../../../../../../../../../tmp/cbuildbot-tmpEny6M_/chrome-sdk-cacheiUTcyc/cache/chrome-sdk/tarballs/daisy+__b__c__cbuild__repository__buildbot_archive__daisy-chromium-pfq__R68-10624.0.0-rc1+sysroot_chromeos-base_chromeos-chrome.tar.xz/usr/local/lib -Wl,-rpath-link=../../../../../../../../../../../tmp/cbuildbot-tmpEny6M_/chrome-sdk-cacheiUTcyc/cache/chrome-sdk/tarballs/daisy+__b__c__cbuild__repository__buildbot_archive__daisy-chromium-pfq__R68-10624.0.0-rc1+sysroot_chromeos-base_chromeos-chrome.tar.xz/usr/local/lib -Wl,--version-script=/b/c/cbuild/repository/.cache/distfiles/target-master/chrome-src/src/mojo/edk/export_only_thunks_api.lst -Wl,-O1 -Wl,-O2 -Wl,--as-needed -stdlib=libc++  -o "./libmojo_core.so" -Wl,-soname="libmojo_core.so" @"./libmojo_core.so.rsp"
/tmp/cbuildbot-tmpEny6M_/chrome-sdk-cacheiUTcyc/cache/chrome-sdk/tarballs/daisy+__b__c__cbuild__repository__buildbot_archive__daisy-chromium-pfq__R68-10624.0.0-rc1+target_toolchain/usr/bin/../include/c++/v1/ios:690: error: undefined reference to 'std::__1::ios_base::init(void*)'
/tmp/cbuildbot-tmpEny6M_/chrome-sdk-cacheiUTcyc/cache/chrome-sdk/tarballs/daisy+__b__c__cbuild__repository__buildbot_archive__daisy-chromium-pfq__R68-10624.0.0-rc1+target_toolchain/usr/bin/../include/c++/v1/streambuf:227: error: undefined reference to 'std::__1::locale::locale()'
/tmp/cbuildbot-tmpEny6M_/chrome-sdk-cacheiUTcyc/cache/chrome-sdk/tarballs/daisy+__b__c__cbuild__repository__buildbot_archive__daisy-chromium-pfq__R68-10624.0.0-rc1+target_toolchain/usr/bin/../include/c++/v1/ios:690: error: undefined reference to 'std::__1::ios_base::init(void*)'
/tmp/cbuildbot-tmpEny6M_/chrome-sdk-cacheiUTcyc/cache/chrome-sdk/tarballs/daisy+__b__c__cbuild__repository__buildbot_archive__daisy-chromium-pfq__R68-10624.0.0-rc1+target_toolchain/usr/bin/../include/c++/v1/streambuf:299: error: undefined reference to 'std::__1::locale::~locale()'
/tmp/cbuildbot-tmpEny6M_/chrome-sdk-cacheiUTcyc/cache/chrome-sdk/tarballs/daisy+__b__c__cbuild__repository__buildbot_archive__daisy-chromium-pfq__R68-10624.0.0-rc1+target_toolchain/usr/bin/../include/c++/v1/streambuf:227: error: undefined reference to 'std::__1::locale::locale()'
/tmp/cbuildbot-tmpEny6M_/chrome-sdk-cacheiUTcyc/cache/chrome-sdk/tarballs/daisy+__b__c__cbuild__repository__buildbot_archive__daisy-chromium-pfq__R68-10624.0.0-rc1+target_toolchain/usr/bin/../include/c++/v1/iosfwd:123: error: undefined reference to 'std::__1::ios_base::~ios_base()'
/tmp/cbuildbot-tmpEny6M_/chrome-sdk-cacheiUTcyc/cache/chrome-sdk/tarballs/daisy+__b__c__cbuild__repository__buildbot_archive__daisy-chromium-pfq__R68-10624.0.0-rc1+target_toolchain/usr/bin/../include/c++/v1/streambuf:299: error: undefined reference to 'std::__1::locale::~locale()'
/tmp/cbuildbot-tmpEny6M_/chrome-sdk-cacheiUTcyc/cache/chrome-sdk/tarballs/daisy+__b__c__cbuild__repository__buildbot_archive__daisy-chromium-pfq__R68-10624.0.0-rc1+target_toolchain/usr/bin/../include/c++/v1/streambuf:299: error: undefined reference to 'std::__1::locale::~locale()'
/tmp/cbuildbot-tmpEny6M_/chrome-sdk-cacheiUTcyc/cache/chrome-sdk/tarballs/daisy+__b__c__cbuild__repository__buildbot_archive__daisy-chromium-pfq__R68-10624.0.0-rc1+target_toolchain/usr/bin/../include/c++/v1/iosfwd:123: error: undefined reference to 'std::__1::ios_base::~ios_base()'
/tmp/cbuildbot-tmpEny6M_/chrome-sdk-cacheiUTcyc/cache/chrome-sdk/tarballs/daisy+__b__c__cbuild__repository__buildbot_archive__daisy-chromium-pfq__R68-10624.0.0-rc1+target_toolchain/usr/bin/../include/c++/v1/ostream:313: error: undefined reference to 'std::__1::ios_base::~ios_base()'
/tmp/cbuildbot-tmpEny6M_/chrome-sdk-cacheiUTcyc/cache/chrome-sdk/tarballs/daisy+__b__c__cbuild__repository__buildbot_archive__daisy-chromium-pfq__R68-10624.0.0-rc1+target_toolchain/usr/bin/../include/c++/v1/iosfwd:123: error: undefined reference to 'std::__1::ios_base::~ios_base()'
obj/mojo/edk/impl_for_mojo_core/channel.o:channel.cc:vtable for mojo::edk::Channel: error: undefined reference to '__cxa_pure_virtual'
/tmp/cbuildbot-tmpEny6M_/chrome-sdk-cacheiUTcyc/cache/chrome-sdk/tarballs/daisy+__b__c__cbuild__repository__buildbot_archive__daisy-chromium-pfq__R68-10624.0.0-rc1+target_toolchain/usr/bin/../include/c++/v1/math.h:736: error: undefined reference to 'ceilf'
obj/mojo/edk/impl_for_mojo_core/channel.o:channel.cc:vtable for mojo::edk::Channel: error: undefined reference to '__cxa_pure_virtual'
/tmp/cbuildbot-tmpEny6M_/chrome-sdk-cacheiUTcyc/cache/chrome-sdk/tarballs/daisy+__b__c__cbuild__repository__buildbot_archive__daisy-chromium-pfq__R68-10624.0.0-rc1+target_toolchain/usr/bin/../include/c++/v1/streambuf:299: error: undefined reference to 'std::__1::locale::~locale()'
/tmp/cbuildbot-tmpEny6M_/chrome-sdk-cacheiUTcyc/cache/chrome-sdk/tarballs/daisy+__b__c__cbuild__repository__buildbot_archive__daisy-chromium-pfq__R68-10624.0.0-rc1+target_toolchain/usr/bin/../include/c++/v1/__hash_table:2143: error: undefined reference to 'std::__1::__next_prime(unsigned int)'
obj/mojo/edk/impl_for_mojo_core/channel.o:channel.cc:vtable for mojo::edk::Channel: error: undefined reference to '__cxa_pure_virtual'
obj/mojo/edk/impl_for_mojo_core/channel.o:channel.cc:vtable for mojo::edk::Channel: error: undefined reference to '__cxa_pure_virtual'
/tmp/cbuildbot-tmpEny6M_/chrome-sdk-cacheiUTcyc/cache/chrome-sdk/tarballs/daisy+__b__c__cbuild__repository__buildbot_archive__daisy-chromium-pfq__R68-10624.0.0-rc1+target_toolchain/usr/bin/../include/c++/v1/math.h:736: error: undefined reference to 'ceilf'
/tmp/cbuildbot-tmpEny6M_/chrome-sdk-cacheiUTcyc/cache/chrome-sdk/tarballs/daisy+__b__c__cbuild__repository__buildbot_archive__daisy-chromium-pfq__R68-10624.0.0-rc1+target_toolchain/usr/bin/../include/c++/v1/__hash_table:2153: error: undefined reference to 'std::__1::__next_prime(unsigned int)'
/tmp/cbuildbot-tmpEny6M_/chrome-sdk-cacheiUTcyc/cache/chrome-sdk/tarballs/daisy+__b__c__cbuild__repository__buildbot_archive__daisy-chromium-pfq__R68-10624.0.0-rc1+target_toolchain/usr/bin/../include/c++/v1/math.h:736: error: undefined reference to 'ceilf'
/tmp/cbuildbot-tmpEny6M_/chrome-sdk-cacheiUTcyc/cache/chrome-sdk/tarballs/daisy+__b__c__cbuild__repository__buildbot_archive__daisy-chromium-pfq__R68-10624.0.0-rc1+target_toolchain/usr/bin/../include/c++/v1/math.h:736: error: undefined reference to 'ceilf'
/tmp/cbuildbot-tmpEny6M_/chrome-sdk-cacheiUTcyc/cache/chrome-sdk/tarballs/daisy+__b__c__cbuild__repository__buildbot_archive__daisy-chromium-pfq__R68-10624.0.0-rc1+target_toolchain/usr/bin/../include/c++/v1/ios:756: error: undefined reference to 'std::__1::ios_base::getloc() const'
../../mojo/edk/system/request_context.cc:55: error: undefined reference to '__cxa_guard_acquire'
../../mojo/edk/system/user_message_impl.cc:299: error: undefined reference to '__cxa_guard_acquire'
../../mojo/edk/system/request_context.cc:55: error: undefined reference to '__cxa_guard_release'
/tmp/cbuildbot-tmpEny6M_/chrome-sdk-cacheiUTcyc/cache/chrome-sdk/tarballs/daisy+__b__c__cbuild__repository__buildbot_archive__daisy-chromium-pfq__R68-10624.0.0-rc1+target_toolchain/usr/bin/../include/c++/v1/__locale:190: error: undefined reference to 'std::__1::locale::use_facet(std::__1::locale::id&) const'
../../mojo/edk/system/user_message_impl.cc:299: error: undefined reference to '__cxa_guard_release'
/tmp/cbuildbot-tmpEny6M_/chrome-sdk-cacheiUTcyc/cache/chrome-sdk/tarballs/daisy+__b__c__cbuild__repository__buildbot_archive__daisy-chromium-pfq__R68-10624.0.0-rc1+target_toolchain/usr/bin/../include/c++/v1/ios:529: error: undefined reference to 'std::__1::ios_base::clear(unsigned int)'
/tmp/cbuildbot-tmpEny6M_/chrome-sdk-cacheiUTcyc/cache/chrome-sdk/tarballs/daisy+__b__c__cbuild__repository__buildbot_archive__daisy-chromium-pfq__R68-10624.0.0-rc1+target_toolchain/usr/bin/../include/c++/v1/ostream:463: error: undefined reference to 'std::__1::ios_base::getloc() const'
/tmp/cbuildbot-tmpEny6M_/chrome-sdk-cacheiUTcyc/cache/chrome-sdk/tarballs/daisy+__b__c__cbuild__repository__buildbot_archive__daisy-chromium-pfq__R68-10624.0.0-rc1+target_toolchain/usr/bin/../include/c++/v1/ostream:276: error: undefined reference to 'std::uncaught_exception()'
/tmp/cbuildbot-tmpEny6M_/chrome-sdk-cacheiUTcyc/cache/chrome-sdk/tarballs/daisy+__b__c__cbuild__repository__buildbot_archive__daisy-chromium-pfq__R68-10624.0.0-rc1+target_toolchain/usr/bin/../include/c++/v1/__locale:190: error: undefined reference to 'std::__1::locale::use_facet(std::__1::locale::id&) const'
/tmp/cbuildbot-tmpEny6M_/chrome-sdk-cacheiUTcyc/cache/chrome-sdk/tarballs/daisy+__b__c__cbuild__repository__buildbot_archive__daisy-chromium-pfq__R68-10624.0.0-rc1+target_toolchain/usr/bin/../include/c++/v1/ios:529: error: undefined reference to 'std::__1::ios_base::clear(unsigned int)'
/tmp/cbuildbot-tmpEny6M_/chrome-sdk-cacheiUTcyc/cache/chrome-sdk/tarballs/daisy+__b__c__cbuild__repository__buildbot_archive__daisy-chromium-pfq__R68-10624.0.0-rc1+target_toolchain/usr/bin/../include/c++/v1/ios:756: error: undefined reference to 'std::__1::ios_base::getloc() const'
/tmp/cbuildbot-tmpEny6M_/chrome-sdk-cacheiUTcyc/cache/chrome-sdk/tarballs/daisy+__b__c__cbuild__repository__buildbot_archive__daisy-chromium-pfq__R68-10624.0.0-rc1+target_toolchain/usr/bin/../include/c++/v1/__locale:190: error: undefined reference to 'std::__1::locale::use_facet(std::__1::locale::id&) const'
/tmp/cbuildbot-tmpEny6M_/chrome-sdk-cacheiUTcyc/cache/chrome-sdk/tarballs/daisy+__b__c__cbuild__repository__buildbot_archive__daisy-chromium-pfq__R68-10624.0.0-rc1+target_toolchain/usr/bin/../include/c++/v1/ostream:0: error: undefined reference to 'std::__1::ctype<char>::id'
/tmp/cbuildbot-tmpEny6M_/chrome-sdk-cacheiUTcyc/cache/chrome-sdk/tarballs/daisy+__b__c__cbuild__repository__buildbot_archive__daisy-chromium-pfq__R68-10624.0.0-rc1+target_toolchain/usr/bin/../include/c++/v1/ios:529: error: undefined reference to 'std::__1::ios_base::clear(unsigned int)'
/tmp/cbuildbot-tmpEny6M_/chrome-sdk-cacheiUTcyc/cache/chrome-sdk/tarballs/daisy+__b__c__cbuild__repository__buildbot_archive__daisy-chromium-pfq__R68-10624.0.0-rc1+target_toolchain/usr/bin/../include/c++/v1/ostream:276: error: undefined reference to 'std::uncaught_exception()'
/tmp/cbuildbot-tmpEny6M_/chrome-sdk-cacheiUTcyc/cache/chrome-sdk/tarballs/daisy+__b__c__cbuild__repository__buildbot_archive__daisy-chromium-pfq__R68-10624.0.0-rc1+target_toolchain/usr/bin/../include/c++/v1/ios:529: error: undefined reference to 'std::__1::ios_base::clear(unsigned int)'
/tmp/cbuildbot-tmpEny6M_/chrome-sdk-cacheiUTcyc/cache/chrome-sdk/tarballs/daisy+__b__c__cbuild__repository__buildbot_archive__daisy-chromium-pfq__R68-10624.0.0-rc1+target_toolchain/usr/bin/../include/c++/v1/ostream:0: error: undefined reference to 'std::__1::num_put<char, std::__1::ostreambuf_iterator<char, std::__1::char_traits<char> > >::id'
/tmp/cbuildbot-tmpEny6M_/chrome-sdk-cacheiUTcyc/cache/chrome-sdk/tarballs/daisy+__b__c__cbuild__repository__buildbot_archive__daisy-chromium-pfq__R68-10624.0.0-rc1+target_toolchain/usr/bin/../include/c++/v1/ostream:276: error: undefined reference to 'std::uncaught_exception()'
/tmp/cbuildbot-tmpEny6M_/chrome-sdk-cacheiUTcyc/cache/chrome-sdk/tarballs/daisy+__b__c__cbuild__repository__buildbot_archive__daisy-chromium-pfq__R68-10624.0.0-rc1+target_toolchain/usr/bin/../include/c++/v1/ostream:0: error: undefined reference to 'std::__1::ctype<char>::id'
/tmp/cbuildbot-tmpEny6M_/chrome-sdk-cacheiUTcyc/cache/chrome-sdk/tarballs/daisy+__b__c__cbuild__repository__buildbot_archive__daisy-chromium-pfq__R68-10624.0.0-rc1+target_toolchain/usr/bin/../include/c++/v1/ostream:492: error: undefined reference to 'std::__1::ios_base::getloc() const'
../../third_party/tcmalloc/chromium/src/sampler.cc:67: error: undefined reference to 'log'
/tmp/cbuildbot-tmpEny6M_/chrome-sdk-cacheiUTcyc/cache/chrome-sdk/tarballs/daisy+__b__c__cbuild__repository__buildbot_archive__daisy-chromium-pfq__R68-10624.0.0-rc1+target_toolchain/usr/bin/../include/c++/v1/__locale:190: error: undefined reference to 'std::__1::locale::use_facet(std::__1::locale::id&) const'
/tmp/cbuildbot-tmpEny6M_/chrome-sdk-cacheiUTcyc/cache/chrome-sdk/tarballs/daisy+__b__c__cbuild__repository__buildbot_archive__daisy-chromium-pfq__R68-10624.0.0-rc1+target_toolchain/usr/bin/../include/c++/v1/ostream:276: error: undefined reference to 'std::uncaught_exception()'
/tmp/cbuildbot-tmpEny6M_/chrome-sdk-cacheiUTcyc/cache/chrome-sdk/tarballs/daisy+__b__c__cbuild__repository__buildbot_archive__daisy-chromium-pfq__R68-10624.0.0-rc1+target_toolchain/usr/bin/../include/c++/v1/ostream:0: error: undefined reference to 'std::__1::num_put<char, std::__1::ostreambuf_iterator<char, std::__1::char_traits<char> > >::id'
/tmp/cbuildbot-tmpEny6M_/chrome-sdk-cacheiUTcyc/cache/chrome-sdk/tarballs/daisy+__b__c__cbuild__repository__buildbot_archive__daisy-chromium-pfq__R68-10624.0.0-rc1+target_toolchain/usr/bin/../include/c++/v1/ostream:0: error: undefined reference to 'std::__1::ctype<char>::id'
../../base/debug/task_annotator.cc:27: error: undefined reference to '__cxa_guard_acquire'
../../base/debug/task_annotator.cc:27: error: undefined reference to '__cxa_guard_release'
../../base/debug/task_annotator.cc:27: error: undefined reference to '__cxa_guard_acquire'
../../base/debug/task_annotator.cc:27: error: undefined reference to '__cxa_guard_release'
/tmp/cbuildbot-tmpEny6M_/chrome-sdk-cacheiUTcyc/cache/chrome-sdk/tarballs/daisy+__b__c__cbuild__repository__buildbot_archive__daisy-chromium-pfq__R68-10624.0.0-rc1+target_toolchain/usr/bin/../include/c++/v1/__hash_table:2143: error: undefined reference to 'std::__1::__next_prime(unsigned int)'
../../third_party/tcmalloc/chromium/src/tcmalloc.cc:1446: error: undefined reference to 'std::set_new_handler(void (*)())'
../../third_party/tcmalloc/chromium/src/tcmalloc.cc:1447: error: undefined reference to 'std::set_new_handler(void (*)())'
../../third_party/tcmalloc/chromium/src/tcmalloc.cc:1446: error: undefined reference to 'std::set_new_handler(void (*)())'
/tmp/cbuildbot-tmpEny6M_/chrome-sdk-cacheiUTcyc/cache/chrome-sdk/tarballs/daisy+__b__c__cbuild__repository__buildbot_archive__daisy-chromium-pfq__R68-10624.0.0-rc1+target_toolchain/usr/bin/../include/c++/v1/__hash_table:2153: error: undefined reference to 'std::__1::__next_prime(unsigned int)'
../../third_party/tcmalloc/chromium/src/tcmalloc.cc:1447: error: undefined reference to 'std::set_new_handler(void (*)())'
/tmp/cbuildbot-tmpEny6M_/chrome-sdk-cacheiUTcyc/cache/chrome-sdk/tarballs/daisy+__b__c__cbuild__repository__buildbot_archive__daisy-chromium-pfq__R68-10624.0.0-rc1+target_toolchain/usr/bin/../include/c++/v1/ios:690: error: undefined reference to 'std::__1::ios_base::init(void*)'
/tmp/cbuildbot-tmpEny6M_/chrome-sdk-cacheiUTcyc/cache/chrome-sdk/tarballs/daisy+__b__c__cbuild__repository__buildbot_archive__daisy-chromium-pfq__R68-10624.0.0-rc1+target_toolchain/usr/bin/../include/c++/v1/streambuf:227: error: undefined reference to 'std::__1::locale::locale()'
/tmp/cbuildbot-tmpEny6M_/chrome-sdk-cacheiUTcyc/cache/chrome-sdk/tarballs/daisy+__b__c__cbuild__repository__buildbot_archive__daisy-chromium-pfq__R68-10624.0.0-rc1+target_toolchain/usr/bin/../include/c++/v1/ios:690: error: undefined reference to 'std::__1::ios_base::init(void*)'
/tmp/cbuildbot-tmpEny6M_/chrome-sdk-cacheiUTcyc/cache/chrome-sdk/tarballs/daisy+__b__c__cbuild__repository__buildbot_archive__daisy-chromium-pfq__R68-10624.0.0-rc1+target_toolchain/usr/bin/../include/c++/v1/streambuf:227: error: undefined reference to 'std::__1::locale::locale()'
../../base/logging.cc:0: error: undefined reference to 'std::__1::ctype<char>::id'
/tmp/cbuildbot-tmpEny6M_/chrome-sdk-cacheiUTcyc/cache/chrome-sdk/tarballs/daisy+__b__c__cbuild__repository__buildbot_archive__daisy-chromium-pfq__R68-10624.0.0-rc1+target_toolchain/usr/bin/../include/c++/v1/ostream:0: error: undefined reference to 'std::__1::num_put<char, std::__1::ostreambuf_iterator<char, std::__1::char_traits<char> > >::id'
../../base/metrics/histogram.cc:313: error: undefined reference to 'log'
../../base/metrics/histogram.cc:322: error: undefined reference to 'log'
../../base/metrics/histogram.cc:328: error: undefined reference to 'exp'
../../base/metrics/histogram.cc:328: error: undefined reference to 'round'
/tmp/cbuildbot-tmpEny6M_/chrome-sdk-cacheiUTcyc/cache/chrome-sdk/tarballs/daisy+__b__c__cbuild__repository__buildbot_archive__daisy-chromium-pfq__R68-10624.0.0-rc1+target_toolchain/usr/bin/../include/c++/v1/ostream:0: error: undefined reference to 'std::__1::num_put<char, std::__1::ostreambuf_iterator<char, std::__1::char_traits<char> > >::id'
../../base/allocator/allocator_shim.cc:57: error: undefined reference to 'std::get_new_handler()'
../../base/allocator/allocator_shim.cc:57: error: undefined reference to 'std::get_new_handler()'
../../base/allocator/allocator_shim.cc:57: error: undefined reference to 'std::get_new_handler()'
../../base/allocator/allocator_shim.cc:57: error: undefined reference to 'std::get_new_handler()'
clang-7: error: linker command failed with exit code 1 (use -v to see invocation)
[8073/41469] CC obj/third_party/sqlite/chromium_sqlite3/recover_varint.o

 
Cc: roc...@chromium.org
might be related to
https://bugs.chromium.org/p/chromium/issues/detail?id=822034&desc=5
(Ship Mojo core as a shared library for Chrome OS and ARC++)

Comment 2 by roc...@chromium.org, Apr 27 2018

Uh that's not good. Worst case, we can revert https://chromium-review.googlesource.com/1026515 and then https://chromium-review.googlesource.com/1024750, but it might actually be quicker to fix just the Chrome build. How can I repro this failure locally?
Cc: steve...@chromium.org ihf@chromium.org
Let me try repro locally, I'm not sure about exact steps.

adding people who might know of the bat

Comment 4 by ihf@chromium.org, Apr 27 2018

Not familiar.
What's puzzling is that this did not blow up on the previous PFQ run, which used the same Chrome version, and chromite change is not that recent either.

From the cls on the blame list for the failed run this comes closest to looking  suspicious (though, I haven't one too much digging yet):
https://chromium-review.googlesource.com/c/chromiumos/overlays/chromiumos-overlay/+/514233

Cc: benchan@chromium.org
forgot to update cc

Comment 7 by roc...@chromium.org, Apr 27 2018

Cc: manojgupta@chromium.org
To clarify, no, the chromite CL is probably not responsible for this, but the chromium CL could be. It's unclear why this didn't break earlier though.

In any case, to revert the chromium CL would require us to first revert the chromite CL. It may be quicker to just figure out why the chrome build is broken in this environment and commit a fix to chromium.
Cc: achuith@chromium.org

Comment 9 by roc...@chromium.org, Apr 27 2018

FWIW if I attempt to build for daisy locally I don't see any issues?
How are you trying to repro this? 
Best way to repro locally would be to use same identical steps as builder:
i.e. $ cros tryjob --local <board>-chrome-pfq-tryjob
I was just trying to do a local build of the failing (daisy) board.

cros tryjob fails horribly and inexplicably for me. I have a working repo checkout and have built and pushed branded official build images to a local device for a different board, so I am fairly sure I have all git auth stuff set up properly.

When cros tryjob runs repo init, it dies after fetching refs from chromium.googlesource.com/external/repo, with a gpg error "No public key". I don't really know what to do with this.
I was able to repro it like:
cd <chrome_root>/src
mkdir test_cros_sdk
gsutil.py cp -r gs://chromeos-image-archive/daisy-chromium-pfq/R68-10624.0.0-rc1 test_cros_sdk/
cros chrome-sdk --board daisy --sdk-path test_cros_sdk/R68-10624.0.0-rc1/


So with those repro steps, I can repro the same kind of link failures (basically, missing libc++) with any trivial executable target. e.g.


local/main.cc:
#include <iostream>
int main() {
  std::cout << "goodbye cruel world\n";
  return 0;
}


local/BUILD.gn:
executable("test") {
  sources = ["main.cc"]
}


autoninja -C out_daisy/Release local:test

===

../../third_party/tcmalloc/chromium/src/sampler.cc:67: error: undefined reference to 'log'
../../base/allocator/allocator_shim.cc:57: error: undefined reference to 'std::get_new_handler()'
../../base/allocator/allocator_shim.cc:57: error: undefined reference to 'std::get_new_handler()'
../../base/allocator/allocator_shim.cc:57: error: undefined reference to 'std::get_new_handler()'
../../third_party/tcmalloc/chromium/src/tcmalloc.cc:1446: error: undefined reference to 'std::set_new_handler(void (*)())'
../../base/allocator/allocator_shim.cc:57: error: undefined reference to 'std::get_new_handler()'
../../third_party/tcmalloc/chromium/src/tcmalloc.cc:1447: error: undefined reference to 'std::set_new_handler(void (*)())'
../../third_party/tcmalloc/chromium/src/tcmalloc.cc:1446: error: undefined reference to 'std::set_new_handler(void (*)())'
../../third_party/tcmalloc/chromium/src/tcmalloc.cc:1447: error: undefined reference to 'std::set_new_handler(void (*)())'
clang-7: error: linker command failed with exit code 1 (use -v to see invocation)

Yeah OK, can confirm. If I locally revert the mojo_core dependency altogether, this toolchain still fails to link any executable targets.

libosmesa.so fails next, and I imagine if that weren't built, the chrome executable itself would fail to link too.

Seems like a toolchain/sysroot issue?
Does adding '-lc++' to linker flags fix the problem? If it was a toolchain issue, I am curious why this is only happening in SimpleChrome mode.
Yes explicitly adding -lc++ (and -lm, actually) fixes the issue.
Ok, I can send a Cl to add these flags to Chrome ebuild to unbreak PFQ. Not sure why they are explicitly needed all of a sudden.
Makes sense if it's just affecting SimpleChrome and will unblock PFQ.

I suppose a separate bug should track investigation of what actually
changed though. Smells like something that could lead to subtle issues
later if not understood.
agree, we should definitely figure out what changed. 
rockot@ What is the clang command line in your local test?
Components: Tools>ChromeOS-Toolchain
Here's the exact command line emitted by ninja to link the test executable from comment #13:

python "../../build/toolchain/gcc_link_wrapper.py" --output="./test" -- armv7a-cros-linux-gnueabi-clang++ -B/z/c/1/.cros_cache/chrome-sdk/tarballs/daisy+__z__c__1__src__test_cros_sdk__R68-10624.0.0-rc1+target_toolchain/usr/x86_64-pc-linux-gnu/armv7a-cros-linux-gnueabi/binutils-bin/2.27.0-gold -Wno-unknown-warning-option -fPIC -Wl,-z,noexecstack -Wl,-z,now -Wl,-z,relro -Wl,-z,defs -Wl,--no-as-needed -lpthread -Wl,--as-needed -fuse-ld=gold -B../../third_party/binutils/Linux_x64/Release/bin -Wl,--threads -Wl,--thread-count=4 -Wl,--icf=all --target=arm-linux-gnueabihf -Wl,-O2 -Wl,--gc-sections -Wl,--gdb-index --sysroot=../../../.cros_cache/chrome-sdk/tarballs/daisy+__z__c__1__src__test_cros_sdk__R68-10624.0.0-rc1+sysroot_chromeos-base_chromeos-chrome.tar.xz -L../../../.cros_cache/chrome-sdk/tarballs/daisy+__z__c__1__src__test_cros_sdk__R68-10624.0.0-rc1+sysroot_chromeos-base_chromeos-chrome.tar.xz/lib -Wl,-rpath-link=../../../.cros_cache/chrome-sdk/tarballs/daisy+__z__c__1__src__test_cros_sdk__R68-10624.0.0-rc1+sysroot_chromeos-base_chromeos-chrome.tar.xz/lib -L../../../.cros_cache/chrome-sdk/tarballs/daisy+__z__c__1__src__test_cros_sdk__R68-10624.0.0-rc1+sysroot_chromeos-base_chromeos-chrome.tar.xz/usr/lib -Wl,-rpath-link=../../../.cros_cache/chrome-sdk/tarballs/daisy+__z__c__1__src__test_cros_sdk__R68-10624.0.0-rc1+sysroot_chromeos-base_chromeos-chrome.tar.xz/usr/lib -L../../../.cros_cache/chrome-sdk/tarballs/daisy+__z__c__1__src__test_cros_sdk__R68-10624.0.0-rc1+sysroot_chromeos-base_chromeos-chrome.tar.xz/usr/local/lib -Wl,-rpath-link=../../../.cros_cache/chrome-sdk/tarballs/daisy+__z__c__1__src__test_cros_sdk__R68-10624.0.0-rc1+sysroot_chromeos-base_chromeos-chrome.tar.xz/usr/local/lib -Wl,-rpath-link=. -Wl,--disable-new-dtags -Wl,-O1 -Wl,-O2 -Wl,--as-needed -stdlib=libc++  -o "./test" -Wl,--start-group @"./test.rsp"  -Wl,--end-group   -ldl -lpthread -lrt 

For comparison the command line emitted when doing whatever a default daisy local build is (i.e. cros chrome-sdk --board=daisy) looks like this:

python "../../build/toolchain/gcc_link_wrapper.py" --output="./test" -- armv7a-cros-linux-gnueabi-clang++ -B/z/c/1/.cros_cache/chrome-sdk/tarballs/daisy+10614.0.0+target_toolchain/usr/x86_64-pc-linux-gnu/armv7a-cros-linux-gnueabi/binutils-bin/2.27.0-gold -Wno-unknown-warning-option -fPIC -Wl,-z,noexecstack -Wl,-z,now -Wl,-z,relro -Wl,-z,defs -Wl,--no-as-needed -lpthread -Wl,--as-needed -fuse-ld=gold -B../../third_party/binutils/Linux_x64/Release/bin -Wl,--threads -Wl,--thread-count=4 -Wl,--icf=all --target=arm-linux-gnueabihf -Wl,-O2 -Wl,--gc-sections -Wl,--gdb-index --sysroot=../../../.cros_cache/chrome-sdk/tarballs/daisy+10614.0.0+sysroot_chromeos-base_chromeos-chrome.tar.xz -L../../../.cros_cache/chrome-sdk/tarballs/daisy+10614.0.0+sysroot_chromeos-base_chromeos-chrome.tar.xz/lib -Wl,-rpath-link=../../../.cros_cache/chrome-sdk/tarballs/daisy+10614.0.0+sysroot_chromeos-base_chromeos-chrome.tar.xz/lib -L../../../.cros_cache/chrome-sdk/tarballs/daisy+10614.0.0+sysroot_chromeos-base_chromeos-chrome.tar.xz/usr/lib -Wl,-rpath-link=../../../.cros_cache/chrome-sdk/tarballs/daisy+10614.0.0+sysroot_chromeos-base_chromeos-chrome.tar.xz/usr/lib -L../../../.cros_cache/chrome-sdk/tarballs/daisy+10614.0.0+sysroot_chromeos-base_chromeos-chrome.tar.xz/usr/local/lib -Wl,-rpath-link=../../../.cros_cache/chrome-sdk/tarballs/daisy+10614.0.0+sysroot_chromeos-base_chromeos-chrome.tar.xz/usr/local/lib -Wl,-rpath-link=. -Wl,--disable-new-dtags -Wl,-O1 -Wl,-O2 -Wl,--as-needed -stdlib=libc++  -o "./test" -Wl,--start-group @"./test.rsp"  -Wl,--end-group   -ldl -lpthread -lrt

And this links just fine. I may be overlooking something, but I think they're exactly the same command lines, modulo which toolchain and sysroot they reference.

Finally, just to be sure, the only discernible and relevant differences between the args.gn generated in each case are the values of cros_target_cc, cros_target_cxx, cros_target_ld, and target_sysroot, all of which are to be expected. So I think this is likely a toolchain or sysroot change that's responsible.
Project Member

Comment 24 by bugdroid1@chromium.org, Apr 28 2018

The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/overlays/chromiumos-overlay/+/6681886a5cecd35d50ac59284a05f5dcfc0775aa

commit 6681886a5cecd35d50ac59284a05f5dcfc0775aa
Author: Manoj Gupta <manojgupta@google.com>
Date: Sat Apr 28 00:56:43 2018

chromeos-chrome: Attempt to fix TestsimpleChromeWorkflow.

Explictly add 'lc++' and 'lm' to link flags.

BUG= chromium:837794 
TEST=PFQ passes.

Change-Id: I698fef3087fe16aa59a01310999951c5f8539369
Reviewed-on: https://chromium-review.googlesource.com/1033501
Commit-Queue: Manoj Gupta <manojgupta@chromium.org>
Trybot-Ready: Manoj Gupta <manojgupta@chromium.org>
Reviewed-by: Ilja H. Friedel <ihf@chromium.org>
Tested-by: Ilja H. Friedel <ihf@chromium.org>

[modify] https://crrev.com/6681886a5cecd35d50ac59284a05f5dcfc0775aa/chromeos-base/chromeos-chrome/chromeos-chrome-9999.ebuild

rockot@ tbarzic@ or local testing, can you modify the cros_target_extra_ldflags variable in gn args and add "-lc++ -lm" to it.
You will have to regenerate the ninja files but go/SimpleChrome doesn't tell how to do so right now.
Yeah, adding those only to cros_target_extra_ldflags yields a working build configuration.
Owner: manojgupta@chromium.org
Project Member

Comment 28 by bugdroid1@chromium.org, Apr 28 2018

The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/chromite/+/117b08a5550a91575e97fa2b6b0a4f026bd043d6

commit 117b08a5550a91575e97fa2b6b0a4f026bd043d6
Author: Manoj Gupta <manojgupta@google.com>
Date: Sat Apr 28 02:58:43 2018

SimpleChrome: Attempt to fix SimpleChromeWorkflow.

Append "-lc++" and "-lm" to ldflags.

BUG= chromium:837794 
TEST=SimpleChromeWorkFlow passes.

Change-Id: I55c8bcbf1317b42149d9ed9a2bc45d3d922c8acb
Reviewed-on: https://chromium-review.googlesource.com/1033458
Tested-by: Ilja H. Friedel <ihf@chromium.org>
Trybot-Ready: Ilja H. Friedel <ihf@chromium.org>
Reviewed-by: Luis Lozano <llozano@chromium.org>
Reviewed-by: Ilja H. Friedel <ihf@chromium.org>

[modify] https://crrev.com/117b08a5550a91575e97fa2b6b0a4f026bd043d6/cli/cros/cros_chrome_sdk.py

Project Member

Comment 29 by bugdroid1@chromium.org, Apr 28 2018

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/c59c4fdb7c8423d932bb1375567c720d3b81bb8c

commit c59c4fdb7c8423d932bb1375567c720d3b81bb8c
Author: chromite-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com <chromite-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com>
Date: Sat Apr 28 04:18:24 2018

Roll src/third_party/chromite/ 7c0757b09..117b08a55 (1 commit)

https://chromium.googlesource.com/chromiumos/chromite.git/+log/7c0757b099e5..117b08a5550a

$ git log 7c0757b09..117b08a55 --date=short --no-merges --format='%ad %ae %s'
2018-04-27 manojgupta SimpleChrome: Attempt to fix SimpleChromeWorkflow.

Created with:
  roll-dep src/third_party/chromite
BUG= chromium:837794 


The AutoRoll server is located here: https://chromite-chromium-roll.skia.org

Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+/master/autoroll/README.md

If the roll is causing failures, please contact the current sheriff, who should
be CC'd on the roll, and stop the roller if necessary.


TBR=chrome-os-gardeners@chromium.org

Change-Id: If6311515375dcee38066d337fd42d0ffa4336a7f
Reviewed-on: https://chromium-review.googlesource.com/1034154
Reviewed-by: Chromite Chromium Autoroll <chromite-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com>
Commit-Queue: Chromite Chromium Autoroll <chromite-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com>
Cr-Commit-Position: refs/heads/master@{#554627}
[modify] https://crrev.com/c59c4fdb7c8423d932bb1375567c720d3b81bb8c/DEPS

Labels: -Restrict-View-Google
Status: Verified (was: Untriaged)
Marking as fixed. will be tracking the toolchain issue in a different bug.
shouldn't we revert those ldflags/libs hacks ?  we don't want those in general.
Yes, will revert after I verify that the toolchain issue is fixed.
Project Member

Comment 33 by bugdroid1@chromium.org, Apr 30 2018

The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/overlays/chromiumos-overlay/+/c3499c953da3d8e9200e4b1bea52b10fd7fa83e3

commit c3499c953da3d8e9200e4b1bea52b10fd7fa83e3
Author: Manoj Gupta <manojgupta@chromium.org>
Date: Mon Apr 30 04:23:31 2018

Revert "chromeos-chrome: Attempt to fix TestsimpleChromeWorkflow."

This reverts commit 6681886a5cecd35d50ac59284a05f5dcfc0775aa.

Reason for revert: No longer needed after CL:1034205.

Original change's description:
> chromeos-chrome: Attempt to fix TestsimpleChromeWorkflow.
>
> Explictly add 'lc++' and 'lm' to link flags.
>
> BUG= chromium:837794 
> TEST=PFQ passes.
>
> Change-Id: I698fef3087fe16aa59a01310999951c5f8539369
> Reviewed-on: https://chromium-review.googlesource.com/1033501
> Commit-Queue: Manoj Gupta <manojgupta@chromium.org>
> Trybot-Ready: Manoj Gupta <manojgupta@chromium.org>
> Reviewed-by: Ilja H. Friedel <ihf@chromium.org>
> Tested-by: Ilja H. Friedel <ihf@chromium.org>

Bug:  chromium:837794 
Change-Id: Iee6f065041fcdab4b214eaf596fe77982fe11408
Reviewed-on: https://chromium-review.googlesource.com/1034393
Commit-Ready: Manoj Gupta <manojgupta@chromium.org>
Tested-by: Manoj Gupta <manojgupta@chromium.org>
Reviewed-by: Mike Frysinger <vapier@chromium.org>

[modify] https://crrev.com/c3499c953da3d8e9200e4b1bea52b10fd7fa83e3/chromeos-base/chromeos-chrome/chromeos-chrome-9999.ebuild

Project Member

Comment 34 by bugdroid1@chromium.org, Apr 30 2018

The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/chromite/+/64133ee653fbc7bfe176eb55e13b931a52bedabb

commit 64133ee653fbc7bfe176eb55e13b931a52bedabb
Author: Manoj Gupta <manojgupta@chromium.org>
Date: Mon Apr 30 04:23:32 2018

Revert "SimpleChrome: Attempt to fix SimpleChromeWorkflow."

This reverts commit 117b08a5550a91575e97fa2b6b0a4f026bd043d6.

Reason for revert: No longer needed after CL:1034205.

Original change's description:
> SimpleChrome: Attempt to fix SimpleChromeWorkflow.
>
> Append "-lc++" and "-lm" to ldflags.
>
> BUG= chromium:837794 
> TEST=SimpleChromeWorkFlow passes.
>
> Change-Id: I55c8bcbf1317b42149d9ed9a2bc45d3d922c8acb
> Reviewed-on: https://chromium-review.googlesource.com/1033458
> Tested-by: Ilja H. Friedel <ihf@chromium.org>
> Trybot-Ready: Ilja H. Friedel <ihf@chromium.org>
> Reviewed-by: Luis Lozano <llozano@chromium.org>
> Reviewed-by: Ilja H. Friedel <ihf@chromium.org>

Bug:  chromium:837794 
Change-Id: I1767f6af4c2cb91e5bce931ab1a60630e279b84d
Reviewed-on: https://chromium-review.googlesource.com/1034313
Commit-Ready: Manoj Gupta <manojgupta@chromium.org>
Tested-by: Manoj Gupta <manojgupta@chromium.org>
Reviewed-by: Mike Frysinger <vapier@chromium.org>

[modify] https://crrev.com/64133ee653fbc7bfe176eb55e13b931a52bedabb/cli/cros/cros_chrome_sdk.py

Project Member

Comment 35 by bugdroid1@chromium.org, Apr 30 2018

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/2f322ec618866f4ce6418076fa998ccad21e74d3

commit 2f322ec618866f4ce6418076fa998ccad21e74d3
Author: chromite-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com <chromite-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com>
Date: Mon Apr 30 06:25:33 2018

Roll src/third_party/chromite/ f578e9249..64133ee65 (1 commit)

https://chromium.googlesource.com/chromiumos/chromite.git/+log/f578e9249f18..64133ee653fb

$ git log f578e9249..64133ee65 --date=short --no-merges --format='%ad %ae %s'
2018-04-29 manojgupta Revert "SimpleChrome: Attempt to fix SimpleChromeWorkflow."

Created with:
  roll-dep src/third_party/chromite
BUG= chromium:837794 


The AutoRoll server is located here: https://chromite-chromium-roll.skia.org

Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+/master/autoroll/README.md

If the roll is causing failures, please contact the current sheriff, who should
be CC'd on the roll, and stop the roller if necessary.


TBR=chrome-os-gardeners@chromium.org

Change-Id: Ie329a31141115eba0a1fd11c85395da0e15af347
Reviewed-on: https://chromium-review.googlesource.com/1034452
Commit-Queue: Chromite Chromium Autoroll <chromite-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com>
Reviewed-by: Chromite Chromium Autoroll <chromite-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com>
Cr-Commit-Position: refs/heads/master@{#554700}
[modify] https://crrev.com/2f322ec618866f4ce6418076fa998ccad21e74d3/DEPS

Sign in to add a comment