Created attachment 534062 [details] The contents of the file "build.log" The compilation chromium-67.0.3396.40 failed with the error: "inline assembly requires more registers than available": ... FAILED: obj/third_party/ffmpeg/ffmpeg_internal/h264_cabac.o i686-pc-linux-gnu-clang -MMD -MF obj/third_party/ffmpeg/ffmpeg_internal/h264_cabac.o.d -DHAVE_AV_CONFIG_H -D_POSIX_C_SOURCE=200112 -D_XOPEN_SOURCE=600 -DPIC -DHAVE_EBP_AVAILABLE=1 -D_ISOC9$ In file included from ../../third_party/ffmpeg/libavcodec/h264_cabac.c:36: In file included from ../../third_party/ffmpeg/libavcodec/cabac_functions.h:46: ../../third_party/ffmpeg/libavcodec/x86/cabac.h:193:9: error: inline assembly requires more registers than available BRANCHLESS_GET_CABAC("%0", "%q0", "(%4)", "%1", "%w1", ^ ../../third_party/ffmpeg/libavcodec/x86/cabac.h:143:9: note: expanded from macro 'BRANCHLESS_GET_CABAC' "movzbl "statep" , "ret" \n\t"\ ... Compilation of chromium-66.0.3359.170 under the same conditions is successful.
Created attachment 534064 [details] Output of the "emerge --info" command
I don't intend to expend any effort on this myself. Patches welcome.
https://bugs.chromium.org/p/chromium/issues/detail?id=796379 Seems upstream is tracking it, I figured they'd have abandoned 32bit.
This post refers to a patch, but I didn't see it https://groups.google.com/a/chromium.org/forum/#!msg/chromium-dev/VBlimAzVDbY/xsjxQg1KAwAJ
(In reply to David Flogeras from comment #4) > This post refers to a patch, but I didn't see it > > https://groups.google.com/a/chromium.org/forum/#!msg/chromium-dev/ > VBlimAzVDbY/xsjxQg1KAwAJ the patch is here (referenced further up the thread): https://bazaar.launchpad.net/~chromium-team/chromium-browser/bionic-stable/view/head:/debian/patches/fix-ffmpeg-ia32-build.patch what's pretty terrible is that apparently this bug has been known to chromium devs since december, yet here we are, with no buildable chromium/x86 in the tree...
The patch proposed in Сomment 5 works: Chromium-67.0.3396.40 compiles successfully.
(In reply to Mike Gilbert from comment #2) > I don't intend to expend any effort on this myself. Patches welcome. is there any chance the patch referenced in #5 will be incorporated into the tree? i can confirm that this bug affects all chromium-67.* and chromium-68.* versions currently in the tree.
Yes, I do intend to add a patch here; I just want to do a little testing first.
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=4df468253f85ead4ce444e2d4945d2457181606b commit 4df468253f85ead4ce444e2d4945d2457181606b Author: Mike Gilbert <floppym@gentoo.org> AuthorDate: 2018-07-22 04:44:12 +0000 Commit: Mike Gilbert <floppym@gentoo.org> CommitDate: 2018-07-22 04:44:54 +0000 www-client/chromium: disable EBP usage in ffmpeg on x86 Closes: https://bugs.gentoo.org/656902 Package-Manager: Portage-2.3.40_p15, Repoman-2.3.9_p247 www-client/chromium/chromium-67.0.3396.99.ebuild | 1 + www-client/chromium/chromium-68.0.3440.68.ebuild | 1 + www-client/chromium/chromium-69.0.3493.3.ebuild | 1 + www-client/chromium/files/chromium-ffmpeg-ebp-r0.patch | 18 ++++++++++++++++++ www-client/chromium/files/chromium-ffmpeg-ebp-r1.patch | 18 ++++++++++++++++++ 5 files changed, 39 insertions(+)
