[yocto] tzdata overwrites existing localtime/zoneinfo?
Hi, It seems to me that the tzdata package will overwrite whatever the current time zone is with its default. This is not great if you’re upgrading the package on an existing system. Should the creation of the file and link be removed from the do_install and only be done in the pkg_postinst? Regards, Anders Montonen -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] Using dpkg-buildpackage within Yocto image
Hello, I would like to be able to build debian packages on yocto itself. This means I would call something like this: dpkg-buildpackage -us -uc -rfakeroot This already does not work, since fakeroot does not exist in the image. It seems there was an older recipe for this but I can't find it in newer releases (sumo). If I build without -rfakeroot as root user I get a step further but then I get: dpkg-checkbuilddeps: error: Unmet build dependencies: debhelper (>= 9) dh-systemd I unfortunately could not find the right recipes which would provide those files. Am I missing something? Thanks in advance, Fabian -- von unterwegs-- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] build core-image-minimal with no bootloader
Hello! How do I build a core-image-minimal without any bootloader ? I tried adding the following lines in conf/local.conf, but without any effect IMAGE_BOOTLOADER = "" PREFERRED_PROVIDER_u-boot = "" PREFERRED_PROVIDER_virtual/bootloader = "" Thank you, Cristian Bercaru -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Working on Dependent Recipes in eSDK
> ChenQi wrote on 10/22/2018 07:04:32 PM: > > Hi Aaron, > > The main pain for now is that `devtool sdk-install ' does > not work as expected, right? > I just checked the codes of sdk-install, and found that it does not fit > the current RSS design. > I'd like to check with you if this is the major concern from your team? > Do you have some other concerns? > I'll open enhancements/bugs on bugzilla and hopefully will work on them > in the 2.7 development cycle. > > Best Regards, > Chen Qi > > ... snip ... Well, I'm not quite sure how "devtool sdk-install " relates after "devtool modify " has been called. My developers use devtool to install dependent recipes into the eSDK when they start working on something. Often they find that they need to make a change in the library code that a dependent recipe provides. In effect, they are developing a patch for the dependent recipe. So they use devtool to say they're going to modify that dependent recipe, and they go and make the changes they want. Then what? How do they get those changes, that patch, available to the eSDK? Any changes made to the library code provided by the dependent recipe are not available to the eSDK, except through devtool commands. In effect there are two different worlds at play, the eSDK sysroots versus the recipe sysroots. The devtool commands seem to make use of the recipe sysroots, but in my mind that defeats the purpose of an eSDK. So I made a plug-in for devtool were I can force the eSDK sysroots to be updated. I'm not sure how that works, but it seems to propagate the workspace (recipe sysroot land) to the eSDK, so changes that developers make are now available for use. I want my developers to use the toolchain (cmake, make, gcc, etc) provided by the eSDK and by things installed into it (devtool sdk-install), rather than having to use devtool as their iterative build command. Ultimately, I would like to be able to skip my devtool plug-in, as it requires the use of "devtool build " and "devtool sdk-sysroot" each time a dependent recipe is modified. But I am not sure how that would work, other than the devtool build command should be updating the eSDK sysroots itself. -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Need Help To Solve Errors while build of Yocto Project
Hi, I am not a developer but according to that manual, one of the requirements is Python 3.4 or greater. I see Python2 stuff in the attached screen shots. Someone else could probably be more definitive. That might not be the reason but you could try with Python 3. https://www.yoctoproject.org/docs/2.5.1/brief-yoctoprojectqs/brief-yoctoprojectqs.html#brief-compatible-distro Scott On Thu, Oct 25, 2018 at 8:13 AM Bhavin Dharmendrabhai Maru < bhavin.m...@vvdntech.in> wrote: > Hi Support Team, > > I am new to yocto project and start to build yocto project by the steps > provided in below link: > > https://www.yoctoproject.org/docs/2.5.1/brief-yoctoprojectqs/brief-yoctoprojectqs.html > > I am getting errors when i give *$ bitbake core-image-sato *command. > details screenshot of errors are attached with this email for your > reference. > > Kindly help me to solve these errors. Any help in this will be appreciated. > > Thanks and Regards, > Bhavin Maru > -- > ___ > yocto mailing list > yocto@yoctoproject.org > https://lists.yoctoproject.org/listinfo/yocto > -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] [SDK] including kernel devsrc to the SDK failes
Hi, I am trying to add the kernel devsrc to the SDK but I am getting the following error Problem: conflicting requests - nothing provides /bin/awk needed by kernel-devsrc-1.0-r0.imx8mqevk I have applied the following patch to try and fix this problem. http://git.yoctoproject.org/cgit/cgit.cgi/linux-yocto/commit/?id=8af11c1cdd8fa08217e702b57cf96e9030db52b2 I have verified that it was applied and run kernel-devsrc works. The error is from do_populate_sdk and I am suspecting that the problem is related to me using rpm. I believe rpm might be to smart in this case detecting the dependency and resulting dnf from failing when running the task do_populate_sdk. Any suggestion on how to get forward on this error. I would like to run dnf manually to check any dependency of the kernel-devsrc rpm package but cannot figure out how. BR Måns Zigher -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [yocto-docs][PATCH v2] kernel-dev: note about the change detection of kernel feature files
On 10/22/18 5:07 AM, Urs Fässler wrote: It is not the expected behavior that changes on the .cfg files only referenced from .scc files are not detected. This looks good to me. Also note that I have an outstanding bugzilla to see if I can invalidate stamps, etc, when these elements change .. so at that point, I'd be able to fixup this documentation section. Bruce Signed-off-by: Urs Fässler Signed-off-by: Pascal Bach --- documentation/kernel-dev/kernel-dev-common.xml | 4 1 file changed, 4 insertions(+) diff --git a/documentation/kernel-dev/kernel-dev-common.xml b/documentation/kernel-dev/kernel-dev-common.xml index 83b02b1c1..2e421e7ba 100644 --- a/documentation/kernel-dev/kernel-dev-common.xml +++ b/documentation/kernel-dev/kernel-dev-common.xml @@ -2623,6 +2623,10 @@ .scc file in the SRC_URI statement to reference multiple kernel features. + +Bitbake only detects changes on files listed in +SRC_URI. + -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] [meta-security][PATCH] os-release: remove OS_RELEASE_FEILD extending
depends on the OS_RELEASRE_FEILD os-release changes in core otherwise yocto-check-layer will fail Signed-off-by: Armin Kuster --- meta-security-compliance/recipes-core/os-release/os-release.bbappend | 3 --- 1 file changed, 3 deletions(-) diff --git a/meta-security-compliance/recipes-core/os-release/os-release.bbappend b/meta-security-compliance/recipes-core/os-release/os-release.bbappend index e9fd44a..604bacb 100644 --- a/meta-security-compliance/recipes-core/os-release/os-release.bbappend +++ b/meta-security-compliance/recipes-core/os-release/os-release.bbappend @@ -1,4 +1 @@ -OS_RELEASE_FIELDS += "CPE_NAME" - CPE_NAME="cpe:/o:openembedded:nodistro:0" - -- 2.7.4 -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
