mesa fails to build for rauru board

[Rob Kean]

I keep getting a failure on the media-libs/mesa emerge. (relevant output below)

any help or suggestions would be greatly appreciated

I have followed the instructions here:  https://www.chromium.org/chromium-os/developer-library/guides/development/developer-guide several times with the same results.

I thought that I might be missing (or misunderstanding) something in the instructions, but `cros build-packages --board="amd64-generic"` successfully builds.

relevant info:

command executed:   

    cros build-packages --board="rauru" --autosetgov --autosetgov-sticky --accept-licenses="*"

mesa build output:
>>> 17:52:19.387 Failed to emerge media-libs/mesa-21.3.9_p20230109-r9 for /build/rauru/, Log file:
>>> 17:52:19.393   /build/rauru/tmp/portage/logs/media-libs:mesa-21.3.9_p20230109-r9:20251102-225141.log
>>> 17:52:19.393 === Start output for job mesa-21.3.9_p20230109-r9 ===
mesa-21.3.9_p20230109-r9:  * Package:    media-libs/mesa-21.3.9_p20230109-r92.8, 14.4, 14.6
mesa-21.3.9_p20230109-r9:  * Repository: chromiumos
mesa-21.3.9_p20230109-r9:  * Maintainer: x11
mesa-21.3.9_p20230109-r9:  * USE:        arm64 classic dri egl elibc_glibc gallium gles2 kernel_linux nptl shared-glapi userland_GNU
mesa-21.3.9_p20230109-r9:  * FEATURES:   network-sandbox sandbox splitdebug userpriv usersandbox
mesa-21.3.9_p20230109-r9:  * Running stacked hooks for pre_pkg_setup
mesa-21.3.9_p20230109-r9:  *    sysroot_build_bin_dir ...
mesa-21.3.9_p20230109-r9:  [ ok ]
mesa-21.3.9_p20230109-r9: 17:51:44.363 >>> Unpacking source...
mesa-21.3.9_p20230109-r9:  * repo(s): https://chromium.googlesource.com
mesa-21.3.9_p20230109-r9:  * project(s): chromiumos/third_party/mesa
mesa-21.3.9_p20230109-r9:  * destdir(s): /build/rauru/tmp/portage/media-libs/mesa-21.3.9_p20230109-r9/work/mesa-21.3.9_p20230109
mesa-21.3.9_p20230109-r9:  * subtree(s):
mesa-21.3.9_p20230109-r9:  * branch(es): upstream/amber
mesa-21.3.9_p20230109-r9:  * path(s): /mnt/host/source/src/third_party/mesa
mesa-21.3.9_p20230109-r9: Cloning into '/build/rauru/tmp/portage/media-libs/mesa-21.3.9_p20230109-r9/work/mesa-21.3.9_p20230109'...
mesa-21.3.9_p20230109-r9: done.
mesa-21.3.9_p20230109-r9: 17:51:53.522 >>> Source unpacked in /build/rauru/tmp/portage/media-libs/mesa-21.3.9_p20230109-r9/work
mesa-21.3.9_p20230109-r9:  * Running stacked hooks for post_src_unpack
mesa-21.3.9_p20230109-r9:  *    asan_init ...
mesa-21.3.9_p20230109-r9:  [ ok ]
mesa-21.3.9_p20230109-r9:  * Running stacked hooks for pre_src_prepare
mesa-21.3.9_p20230109-r9:  *    build_toolchain_catch ...
mesa-21.3.9_p20230109-r9:  [ ok ]
mesa-21.3.9_p20230109-r9: 17:51:55.510 >>> Preparing source in /build/rauru/tmp/portage/media-libs/mesa-21.3.9_p20230109-r9/work/mesa-21.3.9_p20230109 ...
mesa-21.3.9_p20230109-r9:  * Applying UPSTREAM-anv-advertise-rectangularLines-only-for-Gen10.patch ...
mesa-21.3.9_p20230109-r9:  [ ok ]
mesa-21.3.9_p20230109-r9:  * Applying CHROMIUM-i965-increase-BRW_MAX_UBO-to-16.patch ...
mesa-21.3.9_p20230109-r9:  [ ok ]
mesa-21.3.9_p20230109-r9: 17:51:55.568 >>> Source prepared.
mesa-21.3.9_p20230109-r9:  * Running stacked hooks for pre_src_configure
mesa-21.3.9_p20230109-r9:  *    add_pkg_to_cflags ...
mesa-21.3.9_p20230109-r9:  [ ok ]
mesa-21.3.9_p20230109-r9:  *    configure_chromite_local_telemetry ...
mesa-21.3.9_p20230109-r9:  [ ok ]
mesa-21.3.9_p20230109-r9: 17:51:56.789 >>> Configuring source in /build/rauru/tmp/portage/media-libs/mesa-21.3.9_p20230109-r9/work/mesa-21.3.9_p20230109 ...
mesa-21.3.9_p20230109-r9: /build/rauru/build/bin/pkg-config
mesa-21.3.9_p20230109-r9: meson setup --libdir lib64 --localstatedir /var/lib --prefix /usr --sysconfdir /etc --wrap-mode nodownload --build.pkg-config-path /build/rauru/build/broot/usr/share/pkgconfig:/usr/share/pkgconfig --pkg-config-path /usr/lib64/pkgconfig:/usr/share/pkgconfig --native-file /build/rauru/tmp/portage/media-libs/mesa-21.3.9_p20230109-r9/temp/meson.x86_64-pc-linux-gnu.arm64.ini --buildtype plain --cross-file /build/rauru/tmp/portage/media-libs/mesa-21.3.9_p20230109-r9/temp/meson.aarch64-cros-linux-gnu.arm64.ini -Dexecmem=false -Dglvnd=false -Dglx=disabled -Dllvm=false -Dplatforms= -Dprefer-iris=false -Dshader-cache-default=false -Degl=enabled -Dgbm=disabled -Dgles1=disabled -Dgles2=enabled -Dzstd=disabled -Dselinux=false -Ddri-drivers= -Dgallium-drivers= -Dvulkan-drivers= --buildtype release /build/rauru/tmp/portage/media-libs/mesa-21.3.9_p20230109-r9/work/mesa-21.3.9_p20230109 /build/rauru/tmp/portage/media-libs/mesa-21.3.9_p20230109-r9/work/mesa-21.3.9_p20230109-build
mesa-21.3.9_p20230109-r9: The Meson build system
mesa-21.3.9_p20230109-r9: Version: 1.5.1
mesa-21.3.9_p20230109-r9: Source dir: /build/rauru/tmp/portage/media-libs/mesa-21.3.9_p20230109-r9/work/mesa-21.3.9_p20230109
mesa-21.3.9_p20230109-r9: Build dir: /build/rauru/tmp/portage/media-libs/mesa-21.3.9_p20230109-r9/work/mesa-21.3.9_p20230109-build
mesa-21.3.9_p20230109-r9: Build type: cross build
mesa-21.3.9_p20230109-r9: Program python3 found: YES (/usr/bin/python3)
mesa-21.3.9_p20230109-r9: Project name: mesa
mesa-21.3.9_p20230109-r9: Project version: 21.3.9
mesa-21.3.9_p20230109-r9: C compiler for the host machine: aarch64-cros-linux-gnu-clang (clang 21.0 "Chromium OS 21.0_pre563880 clang version 21.0.0git (/mnt/host/source/src/third_party/llvm-project/clang 06d4df1821d8c9f35e046809230ddc0cb1faaf87)")
mesa-21.3.9_p20230109-r9: C linker for the host machine: aarch64-cros-linux-gnu-clang ld.lld 21.0.0
mesa-21.3.9_p20230109-r9: C++ compiler for the host machine: aarch64-cros-linux-gnu-clang++ (clang 21.0 "Chromium OS 21.0_pre563880 clang version 21.0.0git (/mnt/host/source/src/third_party/llvm-project/clang 06d4df1821d8c9f35e046809230ddc0cb1faaf87)")
mesa-21.3.9_p20230109-r9: C++ linker for the host machine: aarch64-cros-linux-gnu-clang++ ld.lld 21.0.0
mesa-21.3.9_p20230109-r9: C compiler for the build machine: x86_64-pc-linux-gnu-clang (clang 21.0 "Chromium OS 21.0_pre563880 clang version 21.0.0git (/mnt/host/source/src/third_party/llvm-project/clang 06d4df1821d8c9f35e046809230ddc0cb1faaf87)")
mesa-21.3.9_p20230109-r9: C linker for the build machine: x86_64-pc-linux-gnu-clang ld.lld 21.0.0
mesa-21.3.9_p20230109-r9: C++ compiler for the build machine: x86_64-pc-linux-gnu-clang++ (clang 21.0 "Chromium OS 21.0_pre563880 clang version 21.0.0git (/mnt/host/source/src/third_party/llvm-project/clang 06d4df1821d8c9f35e046809230ddc0cb1faaf87)")
mesa-21.3.9_p20230109-r9: C++ linker for the build machine: x86_64-pc-linux-gnu-clang++ ld.lld 21.0.0
mesa-21.3.9_p20230109-r9: Build machine cpu family: x86_64
mesa-21.3.9_p20230109-r9: Build machine cpu: x86_64
mesa-21.3.9_p20230109-r9: Host machine cpu family: aarch64
mesa-21.3.9_p20230109-r9: Host machine cpu: aarch64
mesa-21.3.9_p20230109-r9: Target machine cpu family: aarch64
mesa-21.3.9_p20230109-r9: Target machine cpu: aarch64
mesa-21.3.9_p20230109-r9:
mesa-21.3.9_p20230109-r9: meson.build:484:4: ERROR: Problem encountered: EGL requires dri, haiku, or windows
mesa-21.3.9_p20230109-r9:
mesa-21.3.9_p20230109-r9: A full log can be found at /build/rauru/tmp/portage/media-libs/mesa-21.3.9_p20230109-r9/work/mesa-21.3.9_p20230109-build/meson-logs/meson-log.txt
mesa-21.3.9_p20230109-r9:  * ERROR: media-libs/mesa-21.3.9_p20230109-r9::chromiumos failed (configure phase):
mesa-21.3.9_p20230109-r9:  *   (no error message)
mesa-21.3.9_p20230109-r9:  *
mesa-21.3.9_p20230109-r9:  * Call stack:
mesa-21.3.9_p20230109-r9:  *               ebuild.sh, line  125:  Called src_configure
mesa-21.3.9_p20230109-r9:  *             environment, line 4887:  Called meson_src_configure
mesa-21.3.9_p20230109-r9:  *             environment, line 3909:  Called die
mesa-21.3.9_p20230109-r9:  * The specific snippet of code:
mesa-21.3.9_p20230109-r9:  *       "${mesonargs[@]}" ) || die
mesa-21.3.9_p20230109-r9:  *
mesa-21.3.9_p20230109-r9:  * Build log: /build/rauru/tmp/portage/logs/media-libs:mesa-21.3.9_p20230109-r9:20251102-225141.log
mesa-21.3.9_p20230109-r9:  * Stable log symlink: /build/rauru/tmp/portage/media-libs/mesa-21.3.9_p20230109-r9/temp/build.log
mesa-21.3.9_p20230109-r9:  * CWD: /build/rauru/tmp/portage/media-libs/mesa-21.3.9_p20230109-r9/work/mesa-21.3.9_p20230109
mesa-21.3.9_p20230109-r9:  * S:   /build/rauru/tmp/portage/media-libs/mesa-21.3.9_p20230109-r9/work/mesa-21.3.9_p20230109

--- at the end ---

 * Messages for package media-libs/mesa-21.3.9_p20230109-r9 merged to /build/rauru/:
 * Log file: /build/rauru/tmp/portage/logs/media-libs:mesa-21.3.9_p20230109-r9:20251102-225141.log

 * ERROR: media-libs/mesa-21.3.9_p20230109-r9::chromiumos failed (configure phase):
 *   (no error message)
 *
 * Call stack:
 *               ebuild.sh, line  125:  Called src_configure
 *             environment, line 4887:  Called meson_src_configure
 *             environment, line 3909:  Called die
 * The specific snippet of code:
 *       "${mesonargs[@]}" ) || die
 *
 * Build log: /build/rauru/tmp/portage/logs/media-libs:mesa-21.3.9_p20230109-r9:20251102-225141.log
 * Stable log symlink: /build/rauru/tmp/portage/media-libs/mesa-21.3.9_p20230109-r9/temp/build.log
 * CWD: /build/rauru/tmp/portage/media-libs/mesa-21.3.9_p20230109-r9/work/mesa-21.3.9_p20230109
 * S:   /build/rauru/tmp/portage/media-libs/mesa-21.3.9_p20230109-r9/work/mesa-21.3.9_p20230109

------

18:13:12: ERROR: return code: 1; command: sudo --preserve-env 'PKGDIR=/build/rauru/packages' 'PORTAGE_BINHOST=gs://chromeos-prebuilt/board/arm64-generic/postsubmit-R144-16468.0.0-80442-8699509185735666097/packages gs://chromeos-prebuilt/board/arm64-generic/postsubmit-R144-16468.0.0-80442-8699509184666532737/packages gs://chromeos-prebuilt/board/arm64-generic/postsubmit-R144-16469.0.0-80443-8699504799551411137/packages gs://chromeos-prebuilt/board/arm64-generic/postsubmit-R144-16469.0.0-80443-8699504798516120833/packages gs://chromeos-prebuilt/board/arm64-generic/cq-R144-16467.0.0-80424-8699573168358645681/packages' 'CROS_CACHEDIR=/mnt/host/source/.cache' -- /mnt/host/source/chromite/bin/parallel_emerge '--sysroot=/build/rauru' '--root=/build/rauru' -uDNv '--backtrack=30' --newrepo --with-test-deps y '--force-remote-binary=chromeos-base/chromeos-chrome' '--force-remote-binary=chromeos-base/chrome-icu' --getbinpkg --with-bdeps y --usepkg '--jobs=4' '--useoldpkg-atoms=dev-lang/rust dev-lang/go sys-libs/glibc sys-devel/gcc' '--rebuild-exclude=dev-lang/rust dev-lang/go sys-libs/glibc sys-devel/gcc' virtual/target-os virtual/target-os-dev virtual/target-os-factory virtual/target-os-factory-shim virtual/target-os-test chromeos-base/autotest-all
Merging board packages failed
Failed Packages: media-libs/mesa-21.3.9_p20230109-r9

[Rob Kean]

I thought that it was that I was using the 'stable' branch instead of the correct board-specific branch, but I get the same error when I use the 'factory-rauru-16167.B' branch.   :-(

[OpenOS Project]

Try this project for your builds . . . 

https://github.com/google/cro3

cro3 - Make ChromiumOS development extremely easy

cro3 is an extremely user-friendly tool for ChromiumOS developers.

It provides a simple way to do common development tasks and make the barrier for contributing to ChromiumOS and cro3 itself as low as possible.

It also makes discovering features and functionality as easy as and clear as possible, with command completions.

Moreover, it manages local development hardware including DUTs and Servos, and act as working examples of commands to interact with them.

We hope cro3 gives you some time for a nap and/or coffee, or other tasks by making your work more effective ;)

Core principles

Make the basic ChromiumOS development workflow extremely easy

Background: There have been a huge barriers to get started with the ChromiumOS development. It scares newcomers sometimes, and such environment is not sustainable, scalable or efficient. The top priority of cro3 is to mitigate this high barrier of entry.

Basic workflows include: checkout the source code, build images / deploying packages / run tests with / without modifications.

Make it extremely easy to start using cro3

Background: As stated in the above, our goal is lowering the barrier for people who are about to start contribution to ChromiumOS. To achive that, a tool that aids the goal should be extremely easy as well to start using it.

How: Follow best practices and common ways to do things. Prefer defaults always if there is no clear reason to change that.

Be an executable reference of how to do things by providing best practices as a code

Background: Documentation can be rotten silently. Code rots as well, but it is easier to notice that it's broken. Also, people tend to prefer coding over writing documents.

How: Provide enough background information in the code as comments. Put links to the documentation. Put anything useful that may help future developers and users. Avoid natural languages that is confusing. Instead, translate the logics and steps described in documentation as a code.

--
--
ChromiumOS Developers mailing list: chromiu...@chromium.org
View archives, change email options, or unsubscribe:
https://groups.google.com/a/chromium.org/group/chromium-os-dev
To unsubscribe from this group and stop receiving emails from it, send an email to chromium-os-d...@chromium.org.

[Rob Kean]

thank you.  I'll give this a try this evening!

[Rob Kean]

that didn't help.  it hasn't been updated in about a year and the build command fails with deprecation errors.  :-(

[Fei Shao]

Rauru should be using the Mali packages instead of Mesa. Maybe something went wrong with the external build dependencies.
What's the output of `equery-rauru d media-libs/mesa`?

[Fei Shao]

Never mind, I think I found the issue. Can you try the following patch under `src/overlays/`?

```

diff --git a/chipset-mt8196/virtual/opengles/opengles-1.8.ebuild b/chipset-mt8196/virtual/opengles/opengles-1.8.ebuild
index b0509cefcc7b..f2326cf2a6f4 100644
--- a/chipset-mt8196/virtual/opengles/opengles-1.8.ebuild
+++ b/chipset-mt8196/virtual/opengles/opengles-1.8.ebuild
@@ -8,7 +8,7 @@ DESCRIPTION="Virtual for OpenGLES implementations"
 
 LICENSE="metapackage"
 SLOT="0"
-KEYWORDS="-* arm"
+KEYWORDS="-* arm arm64"
 IUSE=""
 
 DEPEND="

```

I'll send a patch to fix that on the main branch.

[Rob Kean]

testing now...

[Rob Kean]

thank you.  This seemed to work.  the build-packages command completed.  I'll try to create an image with the build either tonight or tomorrow