build error for board = amd64-generic (dev/host x64)

56 views
Skip to first unread message

Anthony Loeppert

unread,
Feb 3, 2025, 8:16:47 PMFeb 3
to ChromiumOS Development
Hello all. It has been a while since I built the chromiumos source and when I did I was a "partner". I'm trying now as a guy off the street and I'm hitting this odd error during package building - I get about 900 packages in and then this. Context:

sync
cros_sdk
inside chroot:
cros build-packages --board=amd64-generic --accept-licenses="*"

* ERROR: media-libs/dav1d-1.4.2::portage-stable failed (configure phase):
 *   (no error message)
 *
 * Call stack:
 *               ebuild.sh, line  125:  Called src_configure
 *             environment, line 3807:  Called meson-multilib_src_configure
 *             environment, line 2490:  Called multilib-minimal_src_configure
 *             environment, line 2797:  Called multilib_foreach_abi 'multilib-minimal_abi_src_configure'
 *             environment, line 3030:  Called multibuild_foreach_variant '_multilib_multibuild_wrapper' 'multilib-minimal_abi_src_configure'
 *             environment, line 2658:  Called _multibuild_run '_multilib_multibuild_wrapper' 'multilib-minimal_abi_src_configure'
 *             environment, line 2656:  Called _multilib_multibuild_wrapper 'multilib-minimal_abi_src_configure'
 *             environment, line  720:  Called multilib-minimal_abi_src_configure
 *             environment, line 2791:  Called multilib_src_configure
 *             environment, line 3256:  Called meson_src_configure
 *             environment, line 2592:  Called die
 * The specific snippet of code:
 *       "${mesonargs[@]}" ) || die
 *
 * Build log: /build/amd64-generic/tmp/portage/logs/media-libs:dav1d-1.4.2:20250203-194159.log
 * Stable log symlink: /build/amd64-generic/tmp/portage/media-libs/dav1d-1.4.2/temp/build.log
 * CWD: /build/amd64-generic/tmp/portage/media-libs/dav1d-1.4.2/work/dav1d-1.4.2-abi_x86_64.amd64
 * S:   /build/amd64-generic/tmp/portage/media-libs/dav1d-1.4.2/work/dav1d-1.4.2

Going into the next level of error log:
The Meson build system
Version: 1.5.1
Source dir: /build/amd64-generic/tmp/portage/media-libs/dav1d-1.4.2/work/dav1d-1.4.2
Build dir: /build/amd64-generic/tmp/portage/media-libs/dav1d-1.4.2/work/dav1d-1.4.2-abi_x86_64.amd64
Build type: cross build
Project name: dav1d
Project version: 1.4.2

../dav1d-1.4.2/meson.build:25:0: ERROR: Executables created by c compiler x86_64-cros-linux-gnu-clang are not runnable.

What am I missing? My intuition tells me something simple but I don't see it.

Regards,
Anthony

Raul Rangel

unread,
Feb 4, 2025, 3:57:51 PMFeb 4
to ChromiumOS Development, Anthony Loeppert
Unfortunately the real error message is getting gobbled up: https://issuetracker.google.com/issues/320482846
A patch to fix that would be appreciated :)

If I had to guess you are running Ubuntu 24.04. See the note about user namespaces in the getting started guide: https://www.chromium.org/chromium-os/developer-library/guides/development/developer-guide/#prerequisites

Anthony Loeppert

unread,
Feb 18, 2025, 6:45:34 PMFeb 18
to Raul Rangel, ChromiumOS Development
Hi Raul. First thank you for pointing out that thing I could not see: Ubuntu 24 being the problem.
I setup a VM with Ubuntu 22.04 and had no issue. So I moved on with my life but was annoyed a bit so I went back to 24.10 to see if I could understand the problem.

I don't know the why (the key isn't populated on Ubuntu 24) but 
is where my build died.

I fiddled around a bit but ultimately decided to leave it be as I don't have resources to properly test any change anyway because of the host/target combinations. I'm only trying x64 -> x64

But maybe this will help anyone that already has Ubuntu 24.xx installed and just wants a quick fix:
Change this to
echo "/bin/true"
To skip the checks.

I compiled the packages and created an image on both Ubuntu 22 unmodified and Ubuntu 24 skipping meson_test.py and all seemed well (but I did not use --no-usepkg).

Regards,
Anthony

Raul Rangel

unread,
Feb 18, 2025, 8:50:15 PMFeb 18
to Anthony Loeppert, ChromiumOS Development
Did the commands in the getting started guide not work for Ubuntu 24?
sudo sysctl -w kernel.apparmor_restrict_unprivileged_unconfined=0
sudo sysctl -w kernel.apparmor_restrict_unprivileged_userns=0

Anthony Loeppert

unread,
Feb 19, 2025, 2:05:25 AMFeb 19
to Raul Rangel, ChromiumOS Development
It never occured to me (wise) to disable host OS security features to compile chromiumos. So I didn't try that route.

Regards,
Anthony

Reply all
Reply to author
Forward
0 new messages