[Desktop-packages] [Bug 1978989] Re: FTBFS on armhf since version 102: the final link step segfaults
** Changed in: chromium-browser (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1978989 Title: FTBFS on armhf since version 102: the final link step segfaults Status in chromium-browser package in Ubuntu: Fix Released 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). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1978989/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1978989] Re: FTBFS on armhf since version 102: the final link step segfaults
Started happening again for 109. https://launchpadlibrarian.net/643916878/buildlog_snap_ubuntu_focal_armhf_chromium- snap-from-source-beta_BUILDING.txt.gz ** Changed in: chromium-browser (Ubuntu) Status: Fix Released => In Progress ** Changed in: chromium-browser (Ubuntu) Assignee: Olivier Tilloy (osomon) => Nathan Teodosio (nteodosio) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1978989 Title: FTBFS on armhf since version 102: the final link step segfaults Status in chromium-browser package in Ubuntu: In Progress 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). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1978989/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1978989] Re: FTBFS on armhf since version 102: the final link step segfaults
Also happened on the dev snap and this patch solved it, thanks! ** Changed in: chromium-browser (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1978989 Title: FTBFS on armhf since version 102: the final link step segfaults Status in chromium-browser package in Ubuntu: Fix Released 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). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1978989/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1978989] Re: FTBFS on armhf since version 102: the final link step segfaults
** Branch linked: lp:~chromium-team/chromium-browser/bionic-dev -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1978989 Title: FTBFS on armhf since version 102: the final link step segfaults Status in chromium-browser package in Ubuntu: Fix Committed 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). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1978989/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1978989] Re: FTBFS on armhf since version 102: the final link step segfaults
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 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1978989 Title: FTBFS on armhf since version 102: the final link step segfaults Status in chromium-browser package in Ubuntu: Fix Committed 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). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1978989/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1978989] Re: FTBFS on armhf since version 102: the final link step segfaults
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 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1978989 Title: FTBFS on armhf since version 102: the final link step segfaults Status in chromium-browser package in Ubuntu: In Progress 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). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1978989/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
