Build chromium failed !!!!
Reported by
wangqing...@loongson.cn,
Oct 11
|
|||||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_13_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/71.0.3565.0 Safari/537.36 Steps to reproduce the problem: 1. pull lastest chromium code 2. build chromium with `ninja -C out/Release chrome` What is the expected behavior? What went wrong? [1/1] LINK ./chrome FAILED: chrome python "../../build/toolchain/gcc_link_wrapper.py" --output="./chrome" -- mips64el-redhat-linux-g++ -pie -Wl,--version-script=../../build/linux/chrome.map -fPIC -Wl,-z,noexecstack -Wl,-z,now -Wl,-z,relro -Wl,-z,defs -Wl,--as-needed -Wl,--hash-style=sysv -EL -mabi=64 -Wl,-O2 -Wl,--gc-sections -rdynamic -nodefaultlibs -pie -Wl,-rpath-link=. -Wl,--disable-new-dtags -o "./chrome" -Wl,--start-group @"./chrome.rsp" -Wl,--end-group -lc -lgcc_s -lm -lrt -ldl -lpthread -lX11 -lX11-xcb -lxcb -lXcomposite -lXcursor -lXdamage -lXext -lXfixes -lXi -lXrender -lXtst -lgmodule-2.0 -lglib-2.0 -lgobject-2.0 -lgthread-2.0 -lsmime3 -lnss3 -lnssutil3 -lplds4 -lplc4 -lnspr4 -lcups -lgssapi_krb5 -lkrb5 -lk5crypto -lcom_err -lz -lcrypt -lexpat -ldbus-1 -latomic -lXss -luuid -lXrandr -lresolv -lgio-2.0 -lasound -lpulse -lpangocairo-1.0 -lpango-1.0 -lfribidi -lcairo -lpci -latk-1.0 -latk-bridge-2.0 -latspi -lgtk-3 -lgdk-3 -lcairo-gobject -lgdk_pixbuf-2.0 obj/pdf/libpdf.a: error adding symbols: Malformed archive collect2: error: ld returned 1 exit status ninja: build stopped: subcommand failed. Did this work before? N/A Chrome version: 71.0.3565.0 Channel: n/a OS Version: OS X 10.13.6 Flash Version:
,
Oct 12
Have you tried running `gclient sync`?
,
Oct 14
Yes, I tried I want to ask you if you have encountered such a problem before?
,
Oct 14
,
Oct 15
As this issue is Build related, this is out of scope of triaging at TE end. Hence adding 'TE-NeedsTriageHelp' label and requesting the Build team to look into the issue and help in further triaging. Thanks..
,
Oct 15
,
Oct 16
What revision did you sync to? Can you try syncing to today's HEAD and see if the problem persists? You can also try git bisect to track this down. |
|||||
►
Sign in to add a comment |
|||||
Comment 1 by meh...@chromium.org
, Oct 11Components: -Platform>DevTools Build