chromium_os-raspberry_pi icon indicating copy to clipboard operation
chromium_os-raspberry_pi copied to clipboard

[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"

Open PatrickChenHZ opened this issue 3 years ago • 10 comments

!!! 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

PatrickChenHZ avatar Nov 27 '20 17:11 PatrickChenHZ

also my chromium source is cloned from Fydeos/chromium-raspberry-pi

PatrickChenHZ avatar Nov 27 '20 17:11 PatrickChenHZ

Pls, update the latest overlays. If you use chromium src from us, you need to modify chromeos-base/chromeos-chrome-86.0.4240.28_rc-r1::fyde-for-rpi , try modify ~chromeos-base/chrome-icu-86.0.4240.28_rc to >=~chromeos-base/chrome-icu-86.0.4240.28_rc. You can also mask our chrome ebuild file by add chromeos-base/chromeos-chrome::fyde-for-rpi to overlay-rpi4/profiles/base/package.mask, build system will compile the ebuild in chromiumos instead.

yunshansimon avatar Dec 03 '20 08:12 yunshansimon

HI, I just follow the instruction and tried, with both, the build_package process ends up with "All ebuilds are masked", you need to unmusk at least.... What I tried is change ~chromeos-base/chrome-icu-${PV} to >=chromeos-base/chrome-icu-${PV} Though i don't understand why there needs an "~" but I when I removed it, it looks like it is compelling. Can you explan what is the purpose for ~ and what it will effect when I removed it. Thank you so much.

PatrickChenHZ avatar Dec 04 '20 00:12 PatrickChenHZ

It's my fault, you are right. ~ means need a specific version of the package. My repo is a little early version. You will never pass the compiling if you haven't exactly some version of chrome-icu as mine.

yunshansimon avatar Dec 04 '20 03:12 yunshansimon

Thanks for your reply, my build process works fine now. The new problem I encountered is it will stuck at somepoint of build process and keep printing out jobs:791 of 989 complete,16running for the rest of the day. I did some debug work, and found it will stop at raspberrypi-kernel-5.4.74-r2. And won't pass that. The log for kernel package building shows it cannot find /mnt/host/source/src/third_party/kernel/v5.4-rpi, then it will say cloning into bare repository /var/cache/chromeos-cache/distfiles/egit-src/kernel-rpi But I found both directory is just empty. I have no idea how to fix this issue, should I manually download Raspberrypi kernel source and put that into it's directory?

Thanks, patrick chen

PatrickChenHZ avatar Dec 06 '20 01:12 PatrickChenHZ

updates,

PatrickChenHZ avatar Dec 06 '20 01:12 PatrickChenHZ

Sorry, my problem. It is necessary to setup a github ssh key in the host and chroot building system to clone the kernel repo, And i am using a VM for this build so it is not already setup. I would recommend add this hint to the readme instruction, thanks

PatrickChenHZ avatar Dec 06 '20 01:12 PatrickChenHZ

I am not sure which stage am I suppose to have the git ssh key seted up so that kernel repo will clone automaticly, probably board initialize stage. My current make up solution is manually clone overlay repo branch fydeos-5.4 into /mnt/host/source/src/third_party/kernel and rename the repo folder to v5.4-rpi it works as intended

PatrickChenHZ avatar Dec 06 '20 02:12 PatrickChenHZ

I had successfully built the chromium os, and also fiured out USB boot support to it, I will be adding some additional instructions to readme, and creat a pull request regarding instruction inprovement and issue fixing and usb boot. Thanks to you so much.

PatrickChenHZ avatar Dec 06 '20 10:12 PatrickChenHZ

Shouldn't this issue be closed since it has been resolved?

Ruffio avatar Jan 05 '21 08:01 Ruffio