Skip to content
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

Open
PatrickChenHZ opened this issue Nov 27, 2020 · 10 comments
Labels
solved & solution provided Read this, we have a fix for you

Comments

@PatrickChenHZ
Copy link

PatrickChenHZ commented Nov 27, 2020

!!! 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
Copy link
Author

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

@yunshansimon
Copy link
Member

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.

@PatrickChenHZ
Copy link
Author

PatrickChenHZ commented Dec 4, 2020

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.

@yunshansimon
Copy link
Member

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.

@PatrickChenHZ
Copy link
Author

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
Copy link
Author

PatrickChenHZ commented Dec 6, 2020

updates,

@PatrickChenHZ
Copy link
Author

PatrickChenHZ commented Dec 6, 2020

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
Copy link
Author

PatrickChenHZ commented Dec 6, 2020

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
Copy link
Author

PatrickChenHZ commented Dec 6, 2020

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.

@fydeos-alpha fydeos-alpha added the solved & solution provided Read this, we have a fix for you label Dec 13, 2020
@fydeos-alpha fydeos-alpha reopened this Dec 20, 2020
@Ruffio
Copy link

Ruffio commented Jan 5, 2021

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
solved & solution provided Read this, we have a fix for you
Projects
None yet
Development

No branches or pull requests

4 participants