Skip to content

[Issue report][Bug report]Cannot build_packages, emerge there are no ebuilds to satisfy "chromeos-base/chrome-icu-86.0.4240.28_rc for /build/rpi4" #108

Open
@PatrickChenHZ

Description

@PatrickChenHZ

!!! CONFIG_PROTECT is empty for '/build/rpi4/'

These are the packages that would be merged, in order:

Calculating dependencies . .. ... done!

emerge: there are no ebuilds to satisfy "~chromeos-base/chrome-icu-86.0.4240.28_rc" for /build/rpi4/.
(dependency required by "chromeos-base/chromeos-chrome-86.0.4240.28_rc-r1::fyde-for-rpi" [ebuild])
(dependency required by "virtual/chromeos-interface-1-r5::chromiumos[-chromeless_tty]" [ebuild])
(dependency required by "virtual/target-chromium-os-1-r143::chromiumos" [ebuild])
(dependency required by "virtual/target-os-1-r3::chromiumos" [ebuild])
(dependency required by "virtual/target-os" [argument])
13:23:17 ERROR : emerge detected broken ebuilds. See error message above.
(cr) (release-R86-13421.B/(7bd3fbb...)) patrickchen@primaryVM ~/trunk/src/scripts $

Very sure that my overlay repo is R86-rpi4, my chromium source is chromium-m86,and my chromiumos source tree is release-R86-13421.B, They should match
I also failed to figure this out. I had tried everything recently. New discovery is that we have to use their chromium source, and must have it locally setup, you can refer to build.conf file to find this. But The error didn't change with local chromium source. I also tried following Emerge official doc to trouble shoot, and run emerge-rpi4 chromeos-base/chrome-icu This end up with another error complaning about cannot find package NSS. And Even I installed NSS and PKG_CONFIG manually in chroot, it still won't be able to find it. Another Attmpt I made is compiling chromium out side chroot, and hope it will also compile chrome-icu, but it end up not compiling and throw error"undefined symbol: chromeos::DBusClientFydeOS::DBusClientsFydeOS(bool)"

Considering repo is still being updated, I think the instruction is just too old, or author add something that need extra steps.

Please also refer to old ISSUE about facing error while building packages. There is a lot of people having this issue

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions