Issue metadata
Sign in to add a comment
|
GN: Chrome OS: asan-informational builders fail to build with GN |
||||||||||||||||||||||||
Issue descriptionWe didn't think to test the chromeos ASAN builders with GN and they broke when we switched the default: https://build.chromium.org/p/chromiumos.chromium/builders/x86-generic-tot-asan-informational/builds/11156 We should just fix these in GN asap.
,
Jul 6 2016
See also bug 622498 and bug 622397 .
,
Jul 6 2016
I can reproduce this locally in a chroot with: USE="accessibility asan autotest build_tests buildcheck chrome_debug chrome_remoting clang cups evdev_gestures fonts gn gold highdpi nacl opengles ozone runhooks v4l2_codec vaapi xkbcommon -X -afdo_use -app_shell -chrome_debug_tests -chrome_internal -chrome_media -component_build -envoy -hardfp -internal_gles_conform -internal_khronos_glcts -mojo (-neon) -opengl -v4lplugin -verbose -vtable_verify" emerge-amd64-generic chromeos-chrome
,
Jul 6 2016
The problem appears to be related to clang, not asan specifically.
This also fails in simple chrome for amd64-generic with:
gn gen out_$SDK_BOARD/Release --args="${GN_ARGS} is_clang=true"
,
Jul 6 2016
The issues linked in comment #2 appear to be test failures, this is a build failure.
,
Jul 6 2016
|
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by steve...@chromium.org
, Jul 6 2016