www-client/chromium fails to build if media-libs/mesa is built with -gbm. However, this dependency relation is currently not modelled in the ebuild. Unfortunately I cannot provide a build log of the failed build right now, build was done in a temporary Docker container. If requested, I reproduce it and provide the log. Reproducible: Always
Bundled mesa is used by chromium currently. Please provide build.log and emerge --info. Is it possible that you have enabled Ozone?
Reproduced with chromium-83.
Docker is currently running on another machine that has more CPU cycles free for such tasks. Build.log will be attached when ready. I haven't yet heard of Ozone so I don't think I'm using it ;) Even though chromium might use an internal copy of mesa, it already fails in the configure step, where it tries to find a "libgbm" using pkg-config and fails.
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=3dd2e9b7d65f712837c01e5481052cfc4c2932f0 commit 3dd2e9b7d65f712837c01e5481052cfc4c2932f0 Author: Stephan Hartmann <stha09@googlemail.com> AuthorDate: 2020-05-08 13:16:10 +0000 Commit: Mike Gilbert <floppym@gentoo.org> CommitDate: 2020-05-08 14:59:25 +0000 www-client/chromium: depend on media-libs/mesa[gbm] Closes: https://bugs.gentoo.org/721622 Package-Manager: Portage-2.3.89, Repoman-2.3.20 Signed-off-by: Stephan Hartmann <stha09@googlemail.com> Signed-off-by: Mike Gilbert <floppym@gentoo.org> Closes: https://github.com/gentoo/gentoo/pull/15713 www-client/chromium/chromium-81.0.4044.138.ebuild | 1 + www-client/chromium/chromium-83.0.4103.34.ebuild | 1 + 2 files changed, 2 insertions(+)
