Issue metadata
Sign in to add a comment
|
ChromeSDK build failures in PFQ |
||||||||||||||||||||||
Issue descriptionhttps://chromegw.corp.google.com/i/chromeos/builders/master-chromium-pfq/builds/2598 ChromeSDK stage failures on most of platform PFQs: FAILED: /b/cbuild/internal_master/.cache/distfiles/target/chrome-src/src/third_party/llvm-build/Release+Asserts/bin/clang -Wl,-O1 -Wl,-O2 -Wl,--as-needed -freorder-functions=callgraph -Wl,-rosegment -Wl,--plugin-opt,split_segment=yes -Wl,-z,now -Wl,-z,relro -Wl,-z,defs -pthread -Wl,-z,noexecstack -fPIC -fuse-ld=gold -Wl,--disable-new-dtags -Wl,-O1 -Wl,--as-needed -Wl,--gc-sections -o genversion -Wl,--start-group obj.host/third_party/yasm/source/patched-yasm/modules/preprocs/nasm/genversion.genversion.o -Wl,--end-group clang: error: unknown argument: '-freorder-functions=callgraph' ninja: build stopped: subcommand failed.
,
Mar 2 2016
Issue 591391 has been merged into this issue.
,
Mar 2 2016
See the duplicate bug on comment #2 for some example builds that failed this way. It looks like the last 3 PFW builds for all the effected machines have all failed this way
,
Mar 2 2016
Reverted in https://chromium-review.googlesource.com/#/c/330120/ |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by bccheng@chromium.org
, Mar 2 2016