-
Notifications
You must be signed in to change notification settings - Fork 5
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
Yocto warns about not being able to find defconfig when building odroid-xu4
#60
Comments
MACHINE=odroid-xu4 bitbake virtual/kernel Build Configuration: Initialising tasks: 100% |##########################################################################################################################################################################| Time: 0:00:03 Summary: There were 2 WARNING messages shown. I cannot reproduce on my side @agherzan |
Here is the log and revisions of what I tried (the current master):
|
Why did it pick-up linux-stable_4.10.bb ? 4.10 is for Odroid C2 https://github.com/akuster/meta-odroid/blob/pyro/recipes-kernel/linux/linux-stable_4.10.bb I will retry a clean build just for checking again |
I see the warning when starting a clean build. It is basically because the BSP does not specify a compatible machine for the Odroid C2: https://github.com/akuster/meta-odroid/blob/pyro/recipes-kernel/linux/linux-stable_4.10.bb (I believe the odroid-c2 is not listed as a compatible machine there because https://github.com/akuster/meta-odroid/blob/pyro/recipes-kernel/linux/linux-hardkernel_3.14.bb is supposed to be the kernel recipe for the C2 - at least in the pyro branch of the BSP). So because of this bitbake scans the 4.10 recipe anyway and complains there is no defconfig for the odroid-xu4, even though the 4.9 kernel recipe is to be used. |
We could:
|
For your points: 1 - https://github.com/akuster/meta-odroid does not have issues set-up in github. I've already e-mailed the maintainer a few days ago about an actual issue on the XU4 and got no answer, so I see there's little or no interest from their part. |
Agreed for the first point. For the second one I don't. And this is because other users are building custom images or using our build process and I'd like them to have an experience as clean as possible. And if we can fix this from our layers, I think we should. |
Running a yocto build for odroid-xu4 yields the following warning:
The text was updated successfully, but these errors were encountered: