Issue metadata
Sign in to add a comment
|
Build broken: libbase.so: undefined symbol: __executable_start |
||||||||||||||||||||||
Issue descriptionIssue was not present this morning when I synced; seems to have regressed in the past 5 hours or so. Assigning to thomasanderson@, who introduced do_generate_fontconfig_caches in https://chromium-review.googlesource.com/c/chromium/src/+/938578. Please reassign if needed. CC'ing sheriffs/gardener. gn args: is_debug = false dcheck_always_on = true is_component_build = true target_os = "chromeos" use_goma = true > ninja -C out/Default -j 100 ash_unittests ninja: Entering directory `out/Default' [1/1] Regenerating ninja files [528/9199] ACTION //base/test:do_generate_fontconfig_caches(//build/toolchain/linux:clang_x64) FAILED: fontconfig_caches/STAMP python ../../build/gn_run_binary.py generate_fontconfig_caches ./generate_fontconfig_caches: symbol lookup error: /usr/local/google/chromium/src/out/Default/./libbase.so: undefined symbol: __executable_start generate_fontconfig_caches failed with exit code 127 [627/9190] CXX obj/components/invalidation/public/public/single_object_invalidation_set.o ninja: build stopped: subcommand failed.
,
Apr 27 2018
Looks like it's not just you, since there was a post about this on chromium-dev. However, in that post, transport_security_state_generator was the failing executable, so this is not specific to generate_fontconfig_caches.
,
Apr 27 2018
,
Apr 27 2018
Revert has landed and the issue appears to be fixed now. https://chromium.googlesource.com/chromium/src/+/cc0afbf73869a90f09a0f244a303799d880a0b00
,
Apr 27 2018
,
Apr 28 2018
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/04ec9b02e0485b9fd94de8689d0ca8b923c1ea9c commit 04ec9b02e0485b9fd94de8689d0ca8b923c1ea9c Author: Siddhartha <ssid@chromium.org> Date: Sat Apr 28 01:31:25 2018 Reland "Add utils to read elf binary and get Build id" This reverts commit cc0afbf73869a90f09a0f244a303799d880a0b00. Reason for revert: Move the variable to test file and use it only on official builds. Both Chromeos component and official build works. Original change's description: > Revert "Add utils to read elf binary and get Build id" > > This reverts commit 61248f1ac6be47bcbd6012749f046eaf57bdc007. > > Reason for revert: Suspected breaking component builds ( bug 837817 ) > > Original change's description: > > Add utils to read elf binary and get Build id > > > > Adds code to parse elf binary to get build id from > > .note.gnu.build-id section. The build ID is needed to symbolize > > heap dumps from the users. > > > > BUG=734705 > > > > Change-Id: If4365e232c060ba96071ba1e1c43618f9807e39c > > Reviewed-on: https://chromium-review.googlesource.com/1028995 > > Commit-Queue: Siddhartha S <ssid@chromium.org> > > Reviewed-by: Lei Zhang <thestig@chromium.org> > > Cr-Commit-Position: refs/heads/master@{#554304} > > TBR=thestig@chromium.org,ssid@chromium.org > > Change-Id: If512434b55bcc912990e3997a86f6f93722b15fb > No-Presubmit: true > No-Tree-Checks: true > No-Try: true > Bug: 734705 > Reviewed-on: https://chromium-review.googlesource.com/1033795 > Reviewed-by: Thomas Anderson <thomasanderson@chromium.org> > Commit-Queue: Thomas Anderson <thomasanderson@chromium.org> > Cr-Commit-Position: refs/heads/master@{#554532} TBR=thestig@chromium.org,ssid@chromium.org,thomasanderson@chromium.org Change-Id: Ie2fb8f7fe0759dc418a1bc4ffc57bdb4542ba606 Bug: 734705, 837817 Reviewed-on: https://chromium-review.googlesource.com/1033498 Commit-Queue: Siddhartha S <ssid@chromium.org> Reviewed-by: Siddhartha S <ssid@chromium.org> Cr-Commit-Position: refs/heads/master@{#554601} [modify] https://crrev.com/04ec9b02e0485b9fd94de8689d0ca8b923c1ea9c/base/BUILD.gn [add] https://crrev.com/04ec9b02e0485b9fd94de8689d0ca8b923c1ea9c/base/debug/elf_reader_linux.cc [add] https://crrev.com/04ec9b02e0485b9fd94de8689d0ca8b923c1ea9c/base/debug/elf_reader_linux.h [add] https://crrev.com/04ec9b02e0485b9fd94de8689d0ca8b923c1ea9c/base/debug/elf_reader_linux_unittest.cc |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by khorimoto@chromium.org
, Apr 27 2018