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

Issue 674696 link

Starred by 1 user

Issue metadata

Status: Verified
Owner:
Closed: Dec 2016
Cc:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 1
Type: Bug



Sign in to add a comment

Veyron waterfall build fail because of conflicting gcc switches in SimpleChrome

Project Member Reported by manojgupta@chromium.org, Dec 15 2016

Issue description

Started with https://chromium-review.googlesource.com/#/c/415809/ by hashimoto@

-march=armv7-a flag is probably added by GN in SimpleChrome flow. 

https://uberchromegw.corp.google.com/i/chromeos/builders/arm-llvm-toolchain/builds/95/steps/SimpleChromeWorkflow/logs/stdio

FAILED: obj/base/base_static/switches.o 
armv7a-cros-linux-gnueabi-g++ -B/tmp/cbuildbot-tmp2B3216/chrome-sdk-cacheK14JGi/cache/chrome-sdk/tarballs/veyron_jaq+__b__cbuild__internal_master__buildbot_archive__arm-llvm-toolchain__R57-9089.0.0-rc1+target_toolchain/usr/x86_64-pc-linux-gnu/armv7a-cros-linux-gnueabi/binutils-bin/2.25.51-gold -MMD -MF obj/base/base_static/switches.o.d -DV8_DEPRECATION_WARNINGS -DUSE_UDEV -DUI_COMPOSITOR_IMAGE_TRANSPORT -DUSE_ASH=1 -DUSE_AURA=1 -DUSE_NSS_CERTS=1 -DUSE_OZONE=1 -DENABLE_WAYLAND_SERVER=1 -DFULL_SAFE_BROWSING -DSAFE_BROWSING_CSD -DSAFE_BROWSING_DB_LOCAL -DCHROMIUM_BUILD -DENABLE_MEDIA_ROUTER=1 -DFIELDTRIAL_TESTING_ENABLED -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -D__STDC_CONSTANT_MACROS -D__STDC_FORMAT_MACROS -D_FORTIFY_SOURCE=2 -DOS_CHROMEOS -DNDEBUG -DNVALGRIND -DDYNAMIC_ANNOTATIONS_ENABLED=0 -I../.. -Igen -fno-strict-aliasing -funwind-tables -fPIC -pipe -B../../third_party/binutils/Linux_x64/Release/bin -march=armv7-a -mfloat-abi=hard -mtune=generic-armv7-a -pthread -mfpu=neon -mthumb -Wall -Werror -Wno-psabi -Wno-unused-local-typedefs -Wno-maybe-uninitialized -Wno-missing-field-initializers -Wno-unused-parameter -g2 -gsplit-dwarf --sysroot=../../../../../../../../../../tmp/cbuildbot-tmp2B3216/chrome-sdk-cacheK14JGi/cache/chrome-sdk/tarballs/veyron_jaq+__b__cbuild__internal_master__buildbot_archive__arm-llvm-toolchain__R57-9089.0.0-rc1+sysroot_chromeos-base_chromeos-chrome.tar.xz -fvisibility=hidden -O2 -fno-ident -fdata-sections -ffunction-sections -fno-threadsafe-statics -fvisibility-inlines-hidden -std=gnu++11 -Wno-narrowing -Wno-literal-suffix -fno-rtti -fno-exceptions -pipe -mcpu=cortex-a12 -mtune=cortex-a12 -mfpu=neon -mfloat-abi=hard -D__google_stl_debug_vector=1 -c ../../base/task_scheduler/switches.cc -o obj/base/base_static/switches.o
../../base/task_scheduler/switches.cc:1:0: error: switch -mcpu=cortex-a12 conflicts with -march=armv7-a switch [-Werror]
 
Owner: hashimoto@chromium.org
Labels: -Pri-2 Pri-1
Cc: steve...@chromium.org
Status: Assigned (was: Untriaged)
https://chromium-review.googlesource.com/#/c/415810/ solves the -march=armv7-a issue so once the builder picks up artifacts generated with the newest chromeos-chrome ebuild the failure should be fixed.
(Sorry, I thought CQ-DEPEND would solve all dependency issues.)
Status: Fixed (was: Assigned)
Thanks. Marking as fixed.

Comment 8 by dchan@google.com, Mar 4 2017

Labels: VerifyIn-58

Comment 9 by dchan@google.com, Apr 17 2017

Labels: VerifyIn-59

Comment 10 by dchan@google.com, May 30 2017

Labels: VerifyIn-60
Labels: VerifyIn-61
Status: Verified (was: Fixed)
Closing. Please reopen it if its not fixed. Thanks!

Sign in to add a comment