Re: [yocto] Difference b/w yocto kernels and normal linux.org kernels
Hi Paul Eggleton, I have some doubts on the SDK and build errors. Could you please clarify my doubts. 1. Can we get the consolidated log/file for total installed packages for corresponding SDK. If user wants to know what packages are included in the SDK. 2. When trying to build the images always getting a error saying that clean things in kernel path in build error log, then we goto that path run command make mrproper then it is working fine. Thanks and Regards, Raghavendra K. From: Paul Eggleton paul.eggle...@linux.intel.com Sent: Friday, March 13, 2015 2:23 PM To: Raghavendra Kakarla Cc: yocto@yoctoproject.org Subject: Re: Difference b/w yocto kernels and normal linux.org kernels On Friday 13 March 2015 08:14:13 Raghavendra Kakarla wrote: Is it kernel is must be a git repository code for building in the yocto? When i gave my custom kernel which is not a git repository code and it is in my development PC, i got invalid SRCREV number error. But when give the same kernel from the git repository it is working. Can you please help me in resolving this error. If you want to use your own non-git sources you are moving further away from how the linux-yocto recipe works. If you have not already I would suggest using linux-yocto-custom as described in our kernel development manual: http://www.yoctoproject.org/docs/current/kernel-dev/kernel-dev.html#working-with-your-own-sources Note that you must not have SRCPV included in the recipe's value of PV, or you will get the error you mentioned. Cheers, Paul -- Paul Eggleton Intel Open Source Technology Centre -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Kernel Panic: /sbin/init not found
-Original Message- From: Paul Eggleton [mailto:paul.eggle...@linux.intel.com] Sent: Thursday, April 02, 2015 7:37 PM To: Yu, Chan KitX Cc: yocto@yoctoproject.org Subject: Re: [yocto] Kernel Panic: /sbin/init not found Hi Chan Kit, On Thursday 02 April 2015 09:25:35 Yu, Chan KitX wrote: My Yocto build environment was working perfectly until last week when I got kernel panic caused by missing/sbin/init. When I examined the image, I found that /sbin/init is indeed absent from the root image. To troubleshoot the issue, I tried building a stock Yocto whose target platform is 64-bit machine using a freshly installed Ubuntu 14.04 from another build machine. Despite that, the kernel panic still occurs and that's the main reason I'm writing here; that is to see if anyone else has the same issue. I did not make any change or any customization to local.conf aside from setting MACHINE to 64 bit and adding the following lines which enable multilib: IMAGE_INSTALL = lib32-connman require conf/multilib.conf MULTILIBS = multilib:lib32 DEFAULTTUNE_virtclass-multilib-lib32 = x86 I would be more than happy to provide necessary diagnostic message shall you request so. Let me know if you guys are able to reproduce this issue. What version of the build system are you using? What exact image are you building? What image output type are you trying this with (ext3 / live / etc.)? What is your MACHINE value? Build Configuration: BB_VERSION= 1.24.0 BUILD_SYS = x86_64-linux NATIVELSBSTRING = Ubuntu-14.04 TARGET_SYS= x86_64-poky-linux MACHINE = valleyisland-64 DISTRO= poky DISTRO_VERSION= 1.7.1 TUNE_FEATURES = m64 corei7 TARGET_FPU= meta meta-yocto meta-yocto-bsp= dizzy:ec75238f6cc2d2d8d40e0268f6d2acc070cbe9a4 meta-intel meta-valleyisland = dizzy:c39a4bf4450845fca6f1b26ccfc0db192a4567e8 The above is the build configuration. As of the image that I was trying to build, I did the hddimg and iso. I got the KP issue from using the iso image. I thought the issue might have to do with the meta-valleyisland so I switched to genericx86-64 instead. No luck. Can you attach the manifest file for the image that is broken? Attached. UPDATE: I tried disabling the multilib feature by commenting out the following in local.conf: IMAGE_INSTALL = lib32-connman require conf/multilib.conf MULTILIBS = multilib:lib32 DEFAULTTUNE_virtclass-multilib-lib32 = x86 I used to enable multilib in Yocto by adding those lines and it has always worked. I got this step from https://wiki.yoctoproject.org/wiki/Multilib#How_to_use_it . However, I'm not very sure if that's the proper way to enable multilib in Yocto. Thanks, Chan Kit -- Paul Eggleton Intel Open Source Technology Centre core-image-sato-sdk-valleyisland-64-20150402170740.rootfs.manifest Description: core-image-sato-sdk-valleyisland-64-20150402170740.rootfs.manifest -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Kernel Panic: /sbin/init not found
-Original Message- From: ChenQi [mailto:qi.c...@windriver.com] Sent: Friday, April 03, 2015 3:03 PM To: Yu, Chan KitX; Paul Eggleton Cc: yocto@yoctoproject.org Subject: Re: [yocto] Kernel Panic: /sbin/init not found On 04/03/2015 02:43 PM, Yu, Chan KitX wrote: -Original Message- From: Yu, Chan KitX Sent: Friday, April 03, 2015 2:30 PM To: 'Paul Eggleton' Cc: yocto@yoctoproject.org Subject: RE: [yocto] Kernel Panic: /sbin/init not found -Original Message- From: Paul Eggleton [mailto:paul.eggle...@linux.intel.com] Sent: Thursday, April 02, 2015 7:37 PM To: Yu, Chan KitX Cc: yocto@yoctoproject.org Subject: Re: [yocto] Kernel Panic: /sbin/init not found Hi Chan Kit, On Thursday 02 April 2015 09:25:35 Yu, Chan KitX wrote: My Yocto build environment was working perfectly until last week when I got kernel panic caused by missing/sbin/init. When I examined the image, I found that /sbin/init is indeed absent from the root image. To troubleshoot the issue, I tried building a stock Yocto whose target platform is 64-bit machine using a freshly installed Ubuntu 14.04 from another build machine. Despite that, the kernel panic still occurs and that's the main reason I'm writing here; that is to see if anyone else has the same issue. I did not make any change or any customization to local.conf aside from setting MACHINE to 64 bit and adding the following lines which enable multilib: IMAGE_INSTALL = lib32-connman require conf/multilib.conf MULTILIBS = multilib:lib32 DEFAULTTUNE_virtclass-multilib-lib32 = x86 I would be more than happy to provide necessary diagnostic message shall you request so. Let me know if you guys are able to reproduce this issue. What version of the build system are you using? What exact image are you building? What image output type are you trying this with (ext3 / live / etc.)? What is your MACHINE value? Build Configuration: BB_VERSION= 1.24.0 BUILD_SYS = x86_64-linux NATIVELSBSTRING = Ubuntu-14.04 TARGET_SYS= x86_64-poky-linux MACHINE = valleyisland-64 DISTRO= poky DISTRO_VERSION= 1.7.1 TUNE_FEATURES = m64 corei7 TARGET_FPU= meta meta-yocto meta-yocto-bsp= dizzy:ec75238f6cc2d2d8d40e0268f6d2acc070cbe9a4 meta-intel meta-valleyisland = dizzy:c39a4bf4450845fca6f1b26ccfc0db192a4567e8 The above is the build configuration. As of the image that I was trying to build, I did the hddimg and iso. I got the KP issue from using the iso image. I thought the issue might have to do with the meta-valleyisland so I switched to genericx86-64 instead. No luck. Can you attach the manifest file for the image that is broken? Attached. UPDATE: I tried disabling the multilib feature by commenting out the following in local.conf: IMAGE_INSTALL = lib32-connman The problem is that you set IMAGE_INSTALL to lib32-connman. You should use the following. IMAGE_INSTALL_append = lib32-connman (Note there's a white space before lib32-connman in the assignment above.) Regards, Chen Qi Trying that out now. Fingers crossed. Thank you sir. Chan Kit require conf/multilib.conf MULTILIBS = multilib:lib32 DEFAULTTUNE_virtclass-multilib-lib32 = x86 Argh...I forgot to mention the main thing; that is the KP issue disappears iff I disable the multilib by removing/commenting those lines. As happy as I am since I found the root cause, I really need the multilib feature and hopefully we can dig deeper from here to fix this. Chan Kit -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Kernel Panic: /sbin/init not found
On 04/03/2015 02:43 PM, Yu, Chan KitX wrote: -Original Message- From: Yu, Chan KitX Sent: Friday, April 03, 2015 2:30 PM To: 'Paul Eggleton' Cc: yocto@yoctoproject.org Subject: RE: [yocto] Kernel Panic: /sbin/init not found -Original Message- From: Paul Eggleton [mailto:paul.eggle...@linux.intel.com] Sent: Thursday, April 02, 2015 7:37 PM To: Yu, Chan KitX Cc: yocto@yoctoproject.org Subject: Re: [yocto] Kernel Panic: /sbin/init not found Hi Chan Kit, On Thursday 02 April 2015 09:25:35 Yu, Chan KitX wrote: My Yocto build environment was working perfectly until last week when I got kernel panic caused by missing/sbin/init. When I examined the image, I found that /sbin/init is indeed absent from the root image. To troubleshoot the issue, I tried building a stock Yocto whose target platform is 64-bit machine using a freshly installed Ubuntu 14.04 from another build machine. Despite that, the kernel panic still occurs and that's the main reason I'm writing here; that is to see if anyone else has the same issue. I did not make any change or any customization to local.conf aside from setting MACHINE to 64 bit and adding the following lines which enable multilib: IMAGE_INSTALL = lib32-connman require conf/multilib.conf MULTILIBS = multilib:lib32 DEFAULTTUNE_virtclass-multilib-lib32 = x86 I would be more than happy to provide necessary diagnostic message shall you request so. Let me know if you guys are able to reproduce this issue. What version of the build system are you using? What exact image are you building? What image output type are you trying this with (ext3 / live / etc.)? What is your MACHINE value? Build Configuration: BB_VERSION= 1.24.0 BUILD_SYS = x86_64-linux NATIVELSBSTRING = Ubuntu-14.04 TARGET_SYS= x86_64-poky-linux MACHINE = valleyisland-64 DISTRO= poky DISTRO_VERSION= 1.7.1 TUNE_FEATURES = m64 corei7 TARGET_FPU= meta meta-yocto meta-yocto-bsp= dizzy:ec75238f6cc2d2d8d40e0268f6d2acc070cbe9a4 meta-intel meta-valleyisland = dizzy:c39a4bf4450845fca6f1b26ccfc0db192a4567e8 The above is the build configuration. As of the image that I was trying to build, I did the hddimg and iso. I got the KP issue from using the iso image. I thought the issue might have to do with the meta-valleyisland so I switched to genericx86-64 instead. No luck. Can you attach the manifest file for the image that is broken? Attached. UPDATE: I tried disabling the multilib feature by commenting out the following in local.conf: IMAGE_INSTALL = lib32-connman The problem is that you set IMAGE_INSTALL to lib32-connman. You should use the following. IMAGE_INSTALL_append = lib32-connman (Note there's a white space before lib32-connman in the assignment above.) Regards, Chen Qi require conf/multilib.conf MULTILIBS = multilib:lib32 DEFAULTTUNE_virtclass-multilib-lib32 = x86 Argh...I forgot to mention the main thing; that is the KP issue disappears iff I disable the multilib by removing/commenting those lines. As happy as I am since I found the root cause, I really need the multilib feature and hopefully we can dig deeper from here to fix this. Chan Kit -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Kernel Panic: /sbin/init not found
-Original Message- From: Yu, Chan KitX Sent: Friday, April 03, 2015 2:30 PM To: 'Paul Eggleton' Cc: yocto@yoctoproject.org Subject: RE: [yocto] Kernel Panic: /sbin/init not found -Original Message- From: Paul Eggleton [mailto:paul.eggle...@linux.intel.com] Sent: Thursday, April 02, 2015 7:37 PM To: Yu, Chan KitX Cc: yocto@yoctoproject.org Subject: Re: [yocto] Kernel Panic: /sbin/init not found Hi Chan Kit, On Thursday 02 April 2015 09:25:35 Yu, Chan KitX wrote: My Yocto build environment was working perfectly until last week when I got kernel panic caused by missing/sbin/init. When I examined the image, I found that /sbin/init is indeed absent from the root image. To troubleshoot the issue, I tried building a stock Yocto whose target platform is 64-bit machine using a freshly installed Ubuntu 14.04 from another build machine. Despite that, the kernel panic still occurs and that's the main reason I'm writing here; that is to see if anyone else has the same issue. I did not make any change or any customization to local.conf aside from setting MACHINE to 64 bit and adding the following lines which enable multilib: IMAGE_INSTALL = lib32-connman require conf/multilib.conf MULTILIBS = multilib:lib32 DEFAULTTUNE_virtclass-multilib-lib32 = x86 I would be more than happy to provide necessary diagnostic message shall you request so. Let me know if you guys are able to reproduce this issue. What version of the build system are you using? What exact image are you building? What image output type are you trying this with (ext3 / live / etc.)? What is your MACHINE value? Build Configuration: BB_VERSION= 1.24.0 BUILD_SYS = x86_64-linux NATIVELSBSTRING = Ubuntu-14.04 TARGET_SYS= x86_64-poky-linux MACHINE = valleyisland-64 DISTRO= poky DISTRO_VERSION= 1.7.1 TUNE_FEATURES = m64 corei7 TARGET_FPU= meta meta-yocto meta-yocto-bsp= dizzy:ec75238f6cc2d2d8d40e0268f6d2acc070cbe9a4 meta-intel meta-valleyisland = dizzy:c39a4bf4450845fca6f1b26ccfc0db192a4567e8 The above is the build configuration. As of the image that I was trying to build, I did the hddimg and iso. I got the KP issue from using the iso image. I thought the issue might have to do with the meta-valleyisland so I switched to genericx86-64 instead. No luck. Can you attach the manifest file for the image that is broken? Attached. UPDATE: I tried disabling the multilib feature by commenting out the following in local.conf: IMAGE_INSTALL = lib32-connman require conf/multilib.conf MULTILIBS = multilib:lib32 DEFAULTTUNE_virtclass-multilib-lib32 = x86 Argh...I forgot to mention the main thing; that is the KP issue disappears iff I disable the multilib by removing/commenting those lines. As happy as I am since I found the root cause, I really need the multilib feature and hopefully we can dig deeper from here to fix this. Chan Kit -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Kernel Panic: /sbin/init not found
On Friday 03 April 2015 08:16:44 Yu, Chan KitX wrote: -Original Message- From: Yu, Chan KitX Sent: Friday, April 03, 2015 3:06 PM To: Chen, Qi (Wind River); Paul Eggleton Cc: yocto@yoctoproject.org Subject: RE: [yocto] Kernel Panic: /sbin/init not found -Original Message- From: ChenQi [mailto:qi.c...@windriver.com] Sent: Friday, April 03, 2015 3:03 PM To: Yu, Chan KitX; Paul Eggleton Cc: yocto@yoctoproject.org Subject: Re: [yocto] Kernel Panic: /sbin/init not found On 04/03/2015 02:43 PM, Yu, Chan KitX wrote: -Original Message- From: Yu, Chan KitX Sent: Friday, April 03, 2015 2:30 PM To: 'Paul Eggleton' Cc: yocto@yoctoproject.org Subject: RE: [yocto] Kernel Panic: /sbin/init not found -Original Message- From: Paul Eggleton [mailto:paul.eggle...@linux.intel.com] Sent: Thursday, April 02, 2015 7:37 PM To: Yu, Chan KitX Cc: yocto@yoctoproject.org Subject: Re: [yocto] Kernel Panic: /sbin/init not found Hi Chan Kit, On Thursday 02 April 2015 09:25:35 Yu, Chan KitX wrote: My Yocto build environment was working perfectly until last week when I got kernel panic caused by missing/sbin/init. When I examined the image, I found that /sbin/init is indeed absent from the root image. To troubleshoot the issue, I tried building a stock Yocto whose target platform is 64-bit machine using a freshly installed Ubuntu 14.04 from another build machine. Despite that, the kernel panic still occurs and that's the main reason I'm writing here; that is to see if anyone else has the same issue. I did not make any change or any customization to local.conf aside from setting MACHINE to 64 bit and adding the following lines which enable multilib: IMAGE_INSTALL = lib32-connman require conf/multilib.conf MULTILIBS = multilib:lib32 DEFAULTTUNE_virtclass-multilib-lib32 = x86 I would be more than happy to provide necessary diagnostic message shall you request so. Let me know if you guys are able to reproduce this issue. What version of the build system are you using? What exact image are you building? What image output type are you trying this with (ext3 / live / etc.)? What is your MACHINE value? Build Configuration: BB_VERSION= 1.24.0 BUILD_SYS = x86_64-linux NATIVELSBSTRING = Ubuntu-14.04 TARGET_SYS= x86_64-poky-linux MACHINE = valleyisland-64 DISTRO= poky DISTRO_VERSION= 1.7.1 TUNE_FEATURES = m64 corei7 TARGET_FPU= meta meta-yocto meta-yocto-bsp= dizzy:ec75238f6cc2d2d8d40e0268f6d2acc070cbe9a4 meta-intel meta-valleyisland = dizzy:c39a4bf4450845fca6f1b26ccfc0db192a4567e8 The above is the build configuration. As of the image that I was trying to build, I did the hddimg and iso. I got the KP issue from using the iso image. I thought the issue might have to do with the meta-valleyisland so I switched to genericx86-64 instead. No luck. Can you attach the manifest file for the image that is broken? Attached. UPDATE: I tried disabling the multilib feature by commenting out the following in local.conf: IMAGE_INSTALL = lib32-connman The problem is that you set IMAGE_INSTALL to lib32-connman. You should use the following. IMAGE_INSTALL_append = lib32-connman (Note there's a white space before lib32-connman in the assignment above.) Regards, Chen Qi Trying that out now. Fingers crossed. Thank you sir. Chan Kit OK, it turned out that prepending the space before lib32-connman does not do any good. However, commenting out the line which contains the IMAGE_INSTALL_append does. That begs the question; what does lib32-connman do? It's not lib32-connman that's the problem. The problem is that you were effectively setting the value of IMAGE_INSTALL to something and the default in core-image.bbclass is being set with ?= , and because it's already set at the time the ?= is parsed, the defaults (including the chain leading to sysvinit/systemd) are not being added, among many other packages. If you use IMAGE_INSTALL_append rather than IMAGE_INSTALL (or use a proper image recipe instead of appending to IMAGE_INSTALL from local.conf) you shouldn't have a problem. Cheers, Paul -- Paul Eggleton Intel Open Source Technology Centre -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Kernel Panic: /sbin/init not found
-Original Message- From: Yu, Chan KitX Sent: Friday, April 03, 2015 3:06 PM To: Chen, Qi (Wind River); Paul Eggleton Cc: yocto@yoctoproject.org Subject: RE: [yocto] Kernel Panic: /sbin/init not found -Original Message- From: ChenQi [mailto:qi.c...@windriver.com] Sent: Friday, April 03, 2015 3:03 PM To: Yu, Chan KitX; Paul Eggleton Cc: yocto@yoctoproject.org Subject: Re: [yocto] Kernel Panic: /sbin/init not found On 04/03/2015 02:43 PM, Yu, Chan KitX wrote: -Original Message- From: Yu, Chan KitX Sent: Friday, April 03, 2015 2:30 PM To: 'Paul Eggleton' Cc: yocto@yoctoproject.org Subject: RE: [yocto] Kernel Panic: /sbin/init not found -Original Message- From: Paul Eggleton [mailto:paul.eggle...@linux.intel.com] Sent: Thursday, April 02, 2015 7:37 PM To: Yu, Chan KitX Cc: yocto@yoctoproject.org Subject: Re: [yocto] Kernel Panic: /sbin/init not found Hi Chan Kit, On Thursday 02 April 2015 09:25:35 Yu, Chan KitX wrote: My Yocto build environment was working perfectly until last week when I got kernel panic caused by missing/sbin/init. When I examined the image, I found that /sbin/init is indeed absent from the root image. To troubleshoot the issue, I tried building a stock Yocto whose target platform is 64-bit machine using a freshly installed Ubuntu 14.04 from another build machine. Despite that, the kernel panic still occurs and that's the main reason I'm writing here; that is to see if anyone else has the same issue. I did not make any change or any customization to local.conf aside from setting MACHINE to 64 bit and adding the following lines which enable multilib: IMAGE_INSTALL = lib32-connman require conf/multilib.conf MULTILIBS = multilib:lib32 DEFAULTTUNE_virtclass-multilib-lib32 = x86 I would be more than happy to provide necessary diagnostic message shall you request so. Let me know if you guys are able to reproduce this issue. What version of the build system are you using? What exact image are you building? What image output type are you trying this with (ext3 / live / etc.)? What is your MACHINE value? Build Configuration: BB_VERSION= 1.24.0 BUILD_SYS = x86_64-linux NATIVELSBSTRING = Ubuntu-14.04 TARGET_SYS= x86_64-poky-linux MACHINE = valleyisland-64 DISTRO= poky DISTRO_VERSION= 1.7.1 TUNE_FEATURES = m64 corei7 TARGET_FPU= meta meta-yocto meta-yocto-bsp= dizzy:ec75238f6cc2d2d8d40e0268f6d2acc070cbe9a4 meta-intel meta-valleyisland = dizzy:c39a4bf4450845fca6f1b26ccfc0db192a4567e8 The above is the build configuration. As of the image that I was trying to build, I did the hddimg and iso. I got the KP issue from using the iso image. I thought the issue might have to do with the meta-valleyisland so I switched to genericx86-64 instead. No luck. Can you attach the manifest file for the image that is broken? Attached. UPDATE: I tried disabling the multilib feature by commenting out the following in local.conf: IMAGE_INSTALL = lib32-connman The problem is that you set IMAGE_INSTALL to lib32-connman. You should use the following. IMAGE_INSTALL_append = lib32-connman (Note there's a white space before lib32-connman in the assignment above.) Regards, Chen Qi Trying that out now. Fingers crossed. Thank you sir. Chan Kit OK, it turned out that prepending the space before lib32-connman does not do any good. However, commenting out the line which contains the IMAGE_INSTALL_append does. That begs the question; what does lib32-connman do? Chan Kit -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Release Candidate Build for yocto- now available.
Hi, We are currently at fido which is 1.8. Regards, -- Alexandru Georgescu Yocto QA Engineer SSG/SSD Open Source Technology Center Romania On 03/04/15 17:37, akuster808 akuster...@gmail.com wrote: What version does that poky hash tag equate to ? dizzy, fido. I am too lazy to look it up ; ) Also the referenced url is broken. - armin On 04/02/2015 09:50 PM, Poky Build User wrote: A release candidate build for yocto- is now available at: http://autobuilder.yoctoproject.org/pub/releases/yocto- Please begin QA on this build as soon as possible. Build hash information: meta-intel : 53eea4f12311b4808b3af9695ac822eea1fc60c2 meta-fsl-arm : bfe01a0ebde407086f4a7710ea165c6beff310d7 meta-minnow : 13a5f2ab84c7284647a3e067a33109c11dae0568 meta-qt3 : 3016129d90b7ac8517a5227d819f10ad417b5b45 meta-fsl-ppc : 4c8cd553f9de56379e2b6502ceb996521e2d6a20 poky : 33558eacc8a2d3dce3396b9ab2fd0773ac5076bc This is an automated message from The Yocto Project Autobuilder Git: git://git.yoctoproject.org/yocto-autobuilder Email: elizabeth.flana...@intel.com -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Release Candidate Build for yocto- now available.
On 3 April 2015 at 15:37, akuster808 akuster...@gmail.com wrote: What version does that poky hash tag equate to ? dizzy, fido. I am too lazy to look it up ; ) fido Also the referenced url is broken. - armin Yes. Something messy occurred last night. Please utilise: http://autobuilder.yoctoproject.org/pub/releases/yocto-1.8_m4.rc2/ On 04/02/2015 09:50 PM, Poky Build User wrote: A release candidate build for yocto- is now available at: http://autobuilder.yoctoproject.org/pub/releases/yocto- Please begin QA on this build as soon as possible. Build hash information: meta-intel : 53eea4f12311b4808b3af9695ac822eea1fc60c2 meta-fsl-arm : bfe01a0ebde407086f4a7710ea165c6beff310d7 meta-minnow : 13a5f2ab84c7284647a3e067a33109c11dae0568 meta-qt3 : 3016129d90b7ac8517a5227d819f10ad417b5b45 meta-fsl-ppc : 4c8cd553f9de56379e2b6502ceb996521e2d6a20 poky : 33558eacc8a2d3dce3396b9ab2fd0773ac5076bc This is an automated message from The Yocto Project Autobuilder Git: git://git.yoctoproject.org/yocto-autobuilder Email: elizabeth.flana...@intel.com -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto -- Elizabeth Flanagan Yocto Project Build and Release -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] [kernel config]: specified values did not make it into the kernel's final configuration
Hi, During the build of a core-image-base for BeagleBone using the master branch I was presented with the following warning: WARNING: [kernel config]: specified values did not make it into the kernel's final configuration: The full list of configuration values, which did not make it into kernel's configuration can be found here: http://pastebin.com/sAvXuNC8 Most variables seem to have something to do with things which are not applicable for my particular build and device. There is no need for any graphics so values such as CONFIG_FB_CFB_REV_PIXELS_IN_BYTE and CONFIG_FRAMEBUFFER_CONSOLE_DETECT_PRIMARY seem like they are not needed anyway. But there are a few which look less innocent such as for example CONFIG_ARCH_NR_GPIO and CONFIG_LEDS_GPIO. I did a few builds with poky-dizzy-12.0.1 before moving to the master branch and the mentioned warning was not issued during those builds. The only information about the warning I was able to find on the web is this: http://patchwork.openembedded.org/patch/89289/ So it seems that this is not that critical and somewhere during the build process some kernel configuration values are dropped. Since I do not have enough knowledge about the subject I would like to ask the more knowledgeable of you to reassure me that this warning is not critical. Also, if someone could give an example of why some values are dropped and by who/what, I would be most grateful. I should probably mention that I can successfully deploy the build despite the warnings and everything works as expected. Well, there is one thing and that is that one of requested packages is not built (ntfs-3g) but that is an issue for another thread, if I am unable to find the solution myself. Thank you. FYI: I am new to Yocto and this mailing list -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] Xfce4
Has anybody had any success with Xfce4? I'm trying to roll a build for my Wandboard with Xfce4 desktop environment. Months and months ago, I had things working on the daisy branch. But I'm up to dizzy. Major issues with xfce4-settings pointing to a bad git server. Tried working around that. Generally had to remove the git from the SRC_URI, as it defaults inherits appropriately. I'm using the git.openembedded.org/meta-openembedded which has the meta-xfce layer. --Ken -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Release Candidate Build for yocto- now available.
What version does that poky hash tag equate to ? dizzy, fido. I am too lazy to look it up ; ) Also the referenced url is broken. - armin On 04/02/2015 09:50 PM, Poky Build User wrote: A release candidate build for yocto- is now available at: http://autobuilder.yoctoproject.org/pub/releases/yocto- Please begin QA on this build as soon as possible. Build hash information: meta-intel : 53eea4f12311b4808b3af9695ac822eea1fc60c2 meta-fsl-arm : bfe01a0ebde407086f4a7710ea165c6beff310d7 meta-minnow : 13a5f2ab84c7284647a3e067a33109c11dae0568 meta-qt3 : 3016129d90b7ac8517a5227d819f10ad417b5b45 meta-fsl-ppc : 4c8cd553f9de56379e2b6502ceb996521e2d6a20 poky : 33558eacc8a2d3dce3396b9ab2fd0773ac5076bc This is an automated message from The Yocto Project Autobuilder Git: git://git.yoctoproject.org/yocto-autobuilder Email: elizabeth.flana...@intel.com -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Kernel Panic: /sbin/init not found
OK, it turned out that prepending the space before lib32-connman does not do any good. However, commenting out the line which contains the IMAGE_INSTALL_append does. That begs the question; what does lib32-connman do? It's not lib32-connman that's the problem. The problem is that you were effectively setting the value of IMAGE_INSTALL to something and the default in core-image.bbclass is being set with ?= , and because it's already set at the time the ?= is parsed, the defaults (including the chain leading to sysvinit/systemd) are not being added, among many other packages. If you use IMAGE_INSTALL_append rather than IMAGE_INSTALL (or use a proper image recipe instead of appending to IMAGE_INSTALL from local.conf) you shouldn't have a problem. You can't use IMAGE_INSTALL_append from local.conf (as you already confirmed). You will have to use a proper image recipe (as Paul Eggleton also suggested). I too ran afoul of this recently. The Yocto layer/configuration composition is non-intuitive. It is easy to expect items in local.conf to 'override/extend' the configuration resulting from your layer selections in bblayers.conf, but this is not what happens. I'd personally prefer local.conf to be processed AFTER the conf/layer.conf and conf/machine/some-name.conf files, but at the very least bb needs to know the selected machine first. So to tune/tweak things you need a file up front (local.conf) and a file at the other end (a custom recipe and/or layer). Also, don't think that the ordering of layers in your bblayers.conf file (alone) determines the overlaying/replacement of matching bb/bbappend, inc, or source/patch files. Notice to recipient: This email is meant for only the intended recipient of the transmission, and may be a communication privileged by law, subject to export control restrictions or that otherwise contains proprietary information. If you receive this email by mistake, please notify us immediately by replying to this message and then destroy it and do not review, disclose, copy or distribute it. Thank you in advance for your cooperation. -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
