-
Notifications
You must be signed in to change notification settings - Fork 192
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[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
Comments
also my chromium source is cloned from Fydeos/chromium-raspberry-pi |
Pls, update the latest overlays. If you use chromium src from us, you need to modify |
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.... |
It's my fault, you are right. |
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. Thanks, |
updates, |
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 |
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 |
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. |
Shouldn't this issue be closed since it has been resolved? |
!!! 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
The text was updated successfully, but these errors were encountered: