FTBFS on armhf since version 102: the final link step segfaults

Bug #1978989 reported by Olivier Tilloy
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
chromium-browser (Ubuntu)
Fix Released
Critical
Nathan Teodosio

Bug Description

Example build log:

[51110/51110] LINK ./chrome
FAILED: chrome
python3 "../../build/toolchain/gcc_link_wrapper.py" --output="./chrome" -- ../../../../../usr/bin/clang++-10 -Wl,--version-script=../../build/linux/chrome.map -Wl,--build-id=sha1 -fPIC -Wl,-z,noexecstack -Wl,-z,relro -Wl,-z,now --target=arm-linux-gnueabihf -no-canonical-prefixes -Wl,-O2 -Wl,--gc-sections -rdynamic -Wl,-z,defs -Wl,--as-needed -nostdlib++ -pie -Wl,--disable-new-dtags -Wl,-rpath=\$ORIGIN -o "./chrome" -Wl,--start-group @"./chrome.rsp" ./libffmpeg.so -Wl,--end-group -ldl -lpthread -lrt -lgmodule-2.0 -lgobject-2.0 -lgthread-2.0 -lglib-2.0 -lnss3 -lnssutil3 -lsmime3 -lplds4 -lplc4 -lnspr4 -latk-1.0 -latk-bridge-2.0 -lcups -lgio-2.0 -ldbus-1 -latomic -lresolv -lexpat -luuid -ldrm -lxcb -lxkbcommon -lX11 -lXcomposite -lXdamage -lXext -lXfixes -lXrender -lXrandr -lXtst -lgbm -lwayland-client -lpangocairo-1.0 -lpango-1.0 -lcairo -lasound -lXi -lpci -latspi -lxshmfence
clang++-10: error: unable to execute command: Segmentation fault (core dumped)
clang++-10: error: linker command failed due to signal (use -v to see invocation)
ninja: build stopped: subcommand failed.

This is observed for the deb package builds targeting bionic (built with clang 10), on armhf only (other architectures build fine).

Revision history for this message
Olivier Tilloy (osomon) wrote :
summary: - FTBFS on armhf since version 103: the final link step segfaults
+ FTBFS on armhf since version 102: the final link step segfaults
Revision history for this message
Olivier Tilloy (osomon) wrote :

This is also affecting chromium-browser 102.0.5005.115 (current stable release), making this bug urgent to fix, as this means the latest stable update cannot go to bionic users because it fails to build for armhf.

Changed in chromium-browser (Ubuntu):
importance: High → Critical
Revision history for this message
Olivier Tilloy (osomon) wrote :

The packages for chromium-browser 103.0.5060.53-0ubuntu0.18.04.1 successfully built on all architectures (including armhf) at the first attempt in ppa:chromium-team/beta, so it looks like the patch is enough to work around the problem.

Changed in chromium-browser (Ubuntu):
status: In Progress → Fix Committed
Revision history for this message
Nathan Teodosio (nteodosio) wrote :

Also happened on the dev snap and this patch solved it, thanks!

Changed in chromium-browser (Ubuntu):
status: Fix Committed → Fix Released
Revision history for this message
Nathan Teodosio (nteodosio) wrote :
Changed in chromium-browser (Ubuntu):
status: Fix Released → In Progress
assignee: Olivier Tilloy (osomon) → Nathan Teodosio (nteodosio)
Changed in chromium-browser (Ubuntu):
status: In Progress → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.