TallyLC
May 10, 2025, 4:40pm
21
UPDATE:
Looks like the build packages command is:
cros build-packages '--board=amd64-openfyde' --nowithautotest --autosetgov --nouse_any_chrome
This runs for a short time and then crashes out:
>>> 16:42:07.757 Completed (96 of 1284) sys-fs/dosfstools-4.2-r1::chromiumos to /build/amd64-openfyde/
>>> 16:42:08.430 Completed (97 of 1284) media-libs/lpe-support-topology-0.0.1-r2::chromiumos to /build/amd64-openfyde/
>>> 16:42:08.438 Jobs: 96 of 1284 complete, 1 failed Load avg: 12.2, 5.1, 2.4
* Messages for package chromeos-base/crosid-0.0.1-r210 merged to /build/amd64-openfyde/:
* Log file: /build/amd64-openfyde/tmp/portage/logs/chromeos-base:crosid-0.0.1-r210:20250510-164153.log
* ERROR: chromeos-base/crosid-0.0.1-r210::chromiumos failed (configure phase):
* (no error message)
*
* Call stack:
* ebuild.sh, line 125: Called src_configure
* environment, line 4846: Called meson_src_configure
* environment, line 3786: Called die
* The specific snippet of code:
* "${mesonargs[@]}" ) || die
*
* Build log: /build/amd64-openfyde/tmp/portage/logs/chromeos-base:crosid-0.0.1-r210:20250510-164153.log
* Stable log symlink: /build/amd64-openfyde/tmp/portage/chromeos-base/crosid-0.0.1-r210/temp/build.log
* CWD: /build/amd64-openfyde/tmp/portage/chromeos-base/crosid-0.0.1-r210/work/crosid-0.0.1/platform2/chromeos-config/crosid
* S: /build/amd64-openfyde/tmp/portage/chromeos-base/crosid-0.0.1-r210/work/crosid-0.0.1/platform2/chromeos-config/crosid
16:42:09: NOTICE: Tree Status: welcome to status
16:42:09: ERROR: return code: 1; command: sudo --preserve-env 'PKGDIR=/build/amd64-openfyde/packages' 'PORTAGE_BINHOST=gs://chromeos-prebuilt/board/amd64-generic/postsubmit-R120-15661.0.0-57674-8765886618592172753/packages gs://chromeos-prebuilt/board/amd64-generic/postsubmit-R120-15661.0.0-57683-8765861380626645073/packages gs://chromeos-prebuilt/board/amd64-generic/postsubmit-R120-15661.0.0-57685-8765858341272689441/packages gs://chromeos-prebuilt/board/amd64-generic/postsubmit-R120-15661.0.0-57688-8765852799375903473/packages gs://chromeos-prebuilt/board/amd64-generic/cq-R120-15659.0.0-57605-8766045516440255569/packages' 'CROS_METRICS_DIR=/tmp/tmp9wd1unk6' 'CROS_CACHEDIR=/mnt/host/source/.cache' -- /mnt/host/source/chromite/bin/parallel_emerge '--sysroot=/build/amd64-openfyde' '--root=/build/amd64-openfyde' -uDNv '--backtrack=10' --newrepo --with-test-deps y --getbinpkg --with-bdeps y --usepkg '--jobs=16' '--useoldpkg-atoms=dev-embedded/hps-sdk dev-lang/rust dev-lang/go sys-libs/glibc sys-devel/gcc' '--rebuild-exclude=dev-embedded/hps-sdk 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
Merging board packages failed
Failed Packages: chromeos-base/crosid-0.0.1-r210
But making progress, to be sure. Thanks
TallyLC
May 12, 2025, 10:15am
22
Hi All,
I was looking over the crosid logs and it seems that the problem is in the ebuild with the cross-compiler but I do not yet know how to fix this.
* Package: chromeos-base/crosid-0.0.1-r210
* Repository: chromiumos
* USE: abi_x86_64 amd64 elibc_glibc kernel_linux userland_GNU
* FEATURES: network-sandbox splitdebug userpriv
* Running stacked hooks for pre_pkg_setup
* sysroot_build_bin_dir ...
[ ok ]
09:57:55.951 >>> Unpacking source...
Cloning into '/build/amd64-openfyde/tmp/portage/chromeos-base/crosid-0.0.1-r210/work/crosid-0.0.1/platform2'...
done.
09:57:57.474 >>> Source unpacked in /build/amd64-openfyde/tmp/portage/chromeos-base/crosid-0.0.1-r210/work
* Running stacked hooks for post_src_unpack
* asan_init ...
[ ok ]
* Running stacked hooks for pre_src_prepare
* build_toolchain_catch ...
[ ok ]
09:57:59.059 >>> Preparing source in /build/amd64-openfyde/tmp/portage/chromeos-base/crosid-0.0.1-r210/work/crosid-0.0.1/platform2/chromeos-config/crosid ...
09:57:59.065 >>> Source prepared.
09:57:59.867 >>> Configuring source in /build/amd64-openfyde/tmp/portage/chromeos-base/crosid-0.0.1-r210/work/crosid-0.0.1/platform2/chromeos-config/crosid ...
meson setup --libdir lib64 --localstatedir /var/lib --prefix /usr --sysconfdir /etc --wrap-mode nodownload --build.pkg-config-path /usr/share/pkgconfig --pkg-config-path /usr/lib64/pkgconfig:/usr/share/pkgconfig --native-file /build/amd64-openfyde/tmp/portage/chromeos-base/crosid-0.0.1-r210/temp/meson.x86_64-pc-linux-gnu.amd64.ini --buildtype plain --cross-file /build/amd64-openfyde/tmp/portage/chromeos-base/crosid-0.0.1-r210/temp/meson.x86_64-cros-linux-gnu.amd64.ini -Ddefault_library=both /build/amd64-openfyde/tmp/portage/chromeos-base/crosid-0.0.1-r210/work/crosid-0.0.1/platform2/chromeos-config/crosid /build/amd64-openfyde/tmp/portage/chromeos-base/crosid-0.0.1-r210/work/crosid-0.0.1-build
e[1mThe Meson build systeme[0m
Version: 0.64.1
Source dir: e[1m/build/amd64-openfyde/tmp/portage/chromeos-base/crosid-0.0.1-r210/work/crosid-0.0.1/platform2/chromeos-config/croside[0m
Build dir: e[1m/build/amd64-openfyde/tmp/portage/chromeos-base/crosid-0.0.1-r210/work/crosid-0.0.1-builde[0m
Build type: e[1mcross builde[0m
Project name: e[1mcroside[0m
Project version: e[1mundefinede[0m
meson.build:5:0: e[1;31mERROR:e[0m **Executables created by c compiler x86_64-cros-linux-gnu-clang are not runnable**.
A full log can be found at e[1m/build/amd64-openfyde/tmp/portage/chromeos-base/crosid-0.0.1-r210/work/crosid-0.0.1-build/meson-logs/meson-log.txte[0m
* **ERROR: chromeos-base/crosid-0.0.1-r210::chromiumos failed** (configure phase):
* (no error message)
*
* Call stack:
* ebuild.sh, line 125: Called src_configure
* environment, line 4846: Called meson_src_configure
* environment, line 3786: Called die
* The specific snippet of code:
* "${mesonargs[@]}" ) || die
*
* Build log: /build/amd64-openfyde/tmp/portage/logs/chromeos-base:crosid-0.0.1-r210:20250512-095754.log
* Stable log symlink: /build/amd64-openfyde/tmp/portage/chromeos-base/crosid-0.0.1-r210/temp/build.log
* CWD: /build/amd64-openfyde/tmp/portage/chromeos-base/crosid-0.0.1-r210/work/crosid-0.0.1/platform2/chromeos-config/crosid
* S: /build/amd64-openfyde/tmp/portage/chromeos-base/crosid-0.0.1-r210/work/crosid-0.0.1/platform2/chromeos-config/crosid
Still searching for how to fix this as I would not have expected it to be a problem.
Cheers and have a great day
TallyLC
May 13, 2025, 1:43am
23
Hello All,
Well, I have confirmed this on 3 different setups now in the r120 in that there is something going on with the crosid code and it getting built, but I do not know how to resolve it.
ERROR: chromeos-base/crosid-0.0.1-r210::chromiumos failed (configure phase)
the latest attempt follows a forum post but I get the same results and error.
Any Thoughts?