Re: [yocto] Enabling the recipe from menuconfig
you want to see in kernel menuconfig?? From: yocto-boun...@yoctoproject.org [mailto:yocto-boun...@yoctoproject.org] On Behalf Of Ugesh Reddy Sent: Friday, May 18, 2018 7:52 AM To: 'Yocto-mailing-list'; chandrasekhar Subject: Re: [yocto] Enabling the recipe from menuconfig Hi, Thanks for the response, This will add the recipe as a part of image but I want to build and add the recipe when it has been selected from the menuconfig. How to make visible the recipe in menuconfig? On Thursday, 17 May, 2018, 9:32:15 AM IST, chandrasekharwrote: Hi You can use IMAGE_INSTALL += "Package Name/Recipes name" Regards, Chandrasekhar From: yocto-boun...@yoctoproject.org [mailto:yocto-boun...@yoctoproject.org] On Behalf Of Ugesh Reddy Sent: Wednesday, May 16, 2018 9:57 PM To: Yocto-mailing-list Subject: [yocto] Enabling the recipe from menuconfig Hello Team, I have a list of recipes in my custom layer. The recipes in this layer shall be enabled/selected through the menuconfig, once it is enabled then it shall be the part of image. is it possible to achieve it ? do we have any references? Regards, Ugesh -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [OE-core] [RFT] GCC 8.1
On Thu, May 17, 2018 at 3:46 AM, Martin Jansawrote: > On Thu, May 10, 2018 at 09:11:45PM +0200, Martin Jansa wrote: >> > > 5) nativesdk-libxcrypt fails to build (not sure which change caused >> > > this, it build OK with sumo since the -std=gnu99 addition. >> > > ../git/crypt-sunmd5.c:189:13: error: 'snprintf' output may be truncated >> > > before the last format character [-Werror=format-truncation=] >> > > "$" CRYPT_ALGNAME "," ROUNDS "%u$%s$", >> > > ^~~ >> > > >> > >> > something new, I will look into reproducing this. > > The fix from you worked for me, thanks! There is a followup here which now doesnt need local patch http://git.openembedded.org/openembedded-core-contrib/commit/?h=kraj/master=0924a69244892097f60adbf6c7f576375bea7870 > Just FYI if someone needs similar fix, backporting this: > https://patchwork.kernel.org/patch/9170055/ > > fixed the issue for me, now I have successful kernel build. > > The failing code was always in put_user calls, e.g. kernel/exit.s was showing: > @ 1581 "kernel-source/kernel/exit.c" 1 > .ifnc r0,r0; .ifnc r0r0,fpr11; .ifnc r0r0,r11fp; .ifnc r0r0,ipr12; > .ifnc r0r0,r12ip; .err; .endif; .endif; .endif; .endif; .endif > .ifnc r5,r2; .ifnc r5r2,fpr11; .ifnc r5r2,r11fp; .ifnc r5r2,ipr12; > .ifnc r5r2,r12ip; .err; .endif; .endif; .endif; .endif; .endif > .ifnc r1,r1; .ifnc r1r1,fpr11; .ifnc r1r1,r11fp; .ifnc r1r1,ipr12; > .ifnc r1r1,r12ip; .err; .endif; .endif; .endif; .endif; .endif > bl __put_user_4 > @ 0 "" 2 > > with the error triggered on the middle line. > /tmp/ccHq8ugv.s: Assembler messages: > /tmp/ccHq8ugv.s:1179: Error: .err encountered > /tmp/ccHq8ugv.s:1331: Error: .err encountered > /tmp/ccHq8ugv.s:4617: Error: .err encountered > /tmp/ccHq8ugv.s:6222: Error: .err encountered > /tmp/ccHq8ugv.s:8705: Error: .err encountered > /tmp/ccHq8ugv.s:14486: Error: .err encountered > /tmp/ccHq8ugv.s:14646: Error: .err encountered > /tmp/ccHq8ugv.s:14806: Error: .err encountered > /tmp/ccHq8ugv.s:14966: Error: .err encountered > /tmp/ccHq8ugv.s:15126: Error: .err encountered > /tmp/ccHq8ugv.s:15286: Error: .err encountered > > That leaves only few issues in our internal components and strange failure > with perf which fails to include various header files: perf is building file for qemux86 on o-core I wonder if this is an issue related to your kernel version. > > Cheers, -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] [Yocto][meta-raspberrypi] troubling warning "postinstall intercept hook 'update_gio_module_cache-nativesdk' failed"
I am trying to build for raspberrypi3 near head of sumo. I get the following troublesome warning fairly often since I started doing some builds in sumo and master the past week.: WARNING: core-image-minimal-1.0-r0 do_populate_sdk: The postinstall intercept hook 'update_gio_module_cache-nativesdk' failed, details in /data/development/lfs/yocto/build/spark/raspberrypi3/tmp/work/raspberrypi3-poky-linux-gnueabi/core-image-minimal/1.0-r0/temp/log.do_populate_sdk Here is the detail of the warning is. It basically reports "Invalid ELF image for this architecture": NOTE: > Executing update_gio_module_cache-nativesdk intercept ... WARNING: The postinstall intercept hook 'update_gio_module_cache-nativesdk' failed, details in /data/development/lfs/yocto/build/spark/raspb errypi3/tmp/work/raspberrypi3-poky-linux-gnueabi/core-image-minimal/1.0-r0/temp/log.do_populate_sdk NOTE: Exit code 255. Output: /data/development/lfs/yocto/build/spark/raspberrypi3/tmp/work/raspberrypi3-poky-linux-gnueabi/core-image-minimal/1.0-r0/sdk/image/opt/poky/2 .5/sysroots/x86_64-pokysdk-linux/usr/libexec/nativesdk-gio-querymodules: Invalid ELF image for this architecture Question: How serious is this warning, and what should I do about it? - Steve Pavao Korg R -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Configuration network from qt5
On 17 May 2018 at 14:18, Mauro Zilianiwrote: > Hi all. > > Which the betst choice to perform the network configuration in Yocto Krogoth > from a qt5 application? > > The configuration should be made without external script, using dbus. Well you probably need to use a network manager that you can control trough D-Bus. NetworkManager, ConnMan, systemd-networkd etc. If you are using ConnMan you can use this: https://git.merproject.org/mer-core/libconnman-qt There might exist similar libraries for other network managers but I am not aware of any. -- Med Vänliga Hälsningar / Best Regards Mirza Krak email: mi...@mkrak.org web: https://mkrak.org -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] [meta-raspberrypi] raspberrypi3 at head of sumo has broken console
I just built raspberrypi3 at head of sumo. The attached keyboard and mouse don’t work in the console, although a window and the prompt is displayed. The mouse and keyboard work fine when booting Raspbian or other raspberrypi3 images I’ve built in other branches in the past. Build info below: parallels@ubuntu:/data/development/lfs/yocto/build/spark/raspberrypi3$ bitbake core-image-minimal Parsing recipes: 100% |##| Time: 0:01:15 Parsing of 1935 .bb files complete (0 cached, 1935 parsed). 2790 targets, 120 skipped, 0 masked, 0 errors. NOTE: Resolving any missing task queue dependencies Build Configuration: BB_VERSION = "1.37.0" BUILD_SYS= "x86_64-linux" NATIVELSBSTRING = "ubuntu-16.04" TARGET_SYS = "arm-poky-linux-gnueabi" MACHINE = "raspberrypi3" DISTRO = "poky" DISTRO_VERSION = "2.5" TUNE_FEATURES= "arm armv7ve vfp thumb neon vfpv4 callconvention-hard cortexa7" TARGET_FPU = "hard" meta meta-poky meta-yocto-bsp = "sumo:f0ec7c8b2dc1797ba22c45653a5f182b63354092" meta-oe meta-python meta-multimedia = "sumo:a19aa29f7fa336cd075b72c496fe1102e6e5422b" meta-raspberrypi = "sumo:f2e2a4376e84dec6e5efeabaa86a4406fddf7dcd" NOTE: Fetching uninative binary shim from http://downloads.yoctoproject.org/releases/uninative/1.9/x86_64-nativesdk-libc.tar.bz2;sha256sum=c26622a1f27dbf5b25de986b11584b5c5b2f322d9eb367f705a744f58a5561ec Initialising tasks: 100% |###| Time: 0:00:03 NOTE: Executing SetScene Tasks NOTE: Executing RunQueue Tasks WARNING: libdaemon-0.14-r0 do_fetch: Failed to fetch URL http://0pointer.de/lennart/projects/libdaemon/libdaemon-0.14.tar.gz, attempting MIRRORS if available WARNING: libnss-mdns-0.10-r7 do_fetch: Failed to fetch URL http://0pointer.de/lennart/projects/nss-mdns/nss-mdns-0.10.tar.gz, attempting MIRRORS if available WARNING: apt-1.2.24-r0 do_fetch: Failed to fetch URL http://archive.ubuntu.com/ubuntu/pool/main/a/apt/apt_1.2.24.tar.xz, attempting MIRRORS if available NOTE: Tasks Summary: Attempted 5203 tasks of which 5 didn't need to be rerun and all succeeded. Summary: There were 3 WARNING messages shown. - Steve Pavao Korg R -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Configuration network from qt5
Thanks for the answer. I start with connman because in meta-qt5 there the recipe for it. I keep on with connman. MZ Il 17/05/2018 15:00, Mirza Krak ha scritto: On 17 May 2018 at 14:18, Mauro Zilianiwrote: Hi all. Which the betst choice to perform the network configuration in Yocto Krogoth from a qt5 application? The configuration should be made without external script, using dbus. Well you probably need to use a network manager that you can control trough D-Bus. NetworkManager, ConnMan, systemd-networkd etc. If you are using ConnMan you can use this: https://git.merproject.org/mer-core/libconnman-qt There might exist similar libraries for other network managers but I am not aware of any. -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [Yocto][meta-raspberrypi] troubling warning "postinstall intercept hook 'update_gio_module_cache-nativesdk' failed"
On 05/17/2018 12:17 PM, Steve Pavao wrote: I am trying to build for raspberrypi3 near head of sumo. I get the following troublesome warning fairly often since I started doing some builds in sumo and master the past week.: WARNING: core-image-minimal-1.0-r0 do_populate_sdk: The postinstall intercept hook 'update_gio_module_cache-nativesdk' failed, details in /data/development/lfs/yocto/build/spark/raspberrypi3/tmp/work/raspberrypi3-poky-linux-gnueabi/core-image-minimal/1.0-r0/temp/log.do_populate_sdk Here is the detail of the warning is. It basically reports "Invalid ELF image for this architecture": NOTE: > Executing update_gio_module_cache-nativesdk intercept ... WARNING: The postinstall intercept hook 'update_gio_module_cache-nativesdk' failed, details in /data/development/lfs/yocto/build/spark/raspb errypi3/tmp/work/raspberrypi3-poky-linux-gnueabi/core-image-minimal/1.0-r0/temp/log.do_populate_sdk NOTE: Exit code 255. Output: /data/development/lfs/yocto/build/spark/raspberrypi3/tmp/work/raspberrypi3-poky-linux-gnueabi/core-image-minimal/1.0-r0/sdk/image/opt/poky/2 .5/sysroots/x86_64-pokysdk-linux/usr/libexec/nativesdk-gio-querymodules: Invalid ELF image for this architecture Question: How serious is this warning, and what should I do about it? Thanks for reporting! This is mostly harmless, but I'll make a patch to address it. Alex -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] Configuration network from qt5
Hi all. Which the betst choice to perform the network configuration in Yocto Krogoth from a qt5 application? The configuration should be made without external script, using dbus. Best regards, MZ -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [OE-core] [RFT] GCC 8.1
On Thu, May 10, 2018 at 09:11:45PM +0200, Martin Jansa wrote: > > > 5) nativesdk-libxcrypt fails to build (not sure which change caused > > > this, it build OK with sumo since the -std=gnu99 addition. > > > ../git/crypt-sunmd5.c:189:13: error: 'snprintf' output may be truncated > > > before the last format character [-Werror=format-truncation=] > > > "$" CRYPT_ALGNAME "," ROUNDS "%u$%s$", > > > ^~~ > > > > > > > something new, I will look into reproducing this. The fix from you worked for me, thanks! > > > I didn't get very far in testing, because our old kernel fails to build > > > with gcc8 and there are some other issues caused by other master > > > changes. But it doesn't look too bad (in my small test, lets see what > > > bitbake world will show), thanks a lot for new gcc. > > > > > > > yes, older kernel needs fixes, especially to disable new warnings. > > the mips/ppc fixes that I put out there might be helpful to cook up > > fixes for older kernels if running into same issues. > > In this case it fails with Error: .err encountered for many drivers. It's not > the same case as in: > http://lists.infradead.org/pipermail/linux-arm-kernel/2015-February/325615.html > nor arm version of this change, both are already applied in our > 4.4.3 based kernel. > > I've tried to reproduce with vanilla 4.4.143 and it doesn't fail like this, > vanilla 4.4.3 doesn't > fail, so it's caused by one of our 1 commits on top of 4.4.3 or the > config, need to dig a bit more. Just FYI if someone needs similar fix, backporting this: https://patchwork.kernel.org/patch/9170055/ fixed the issue for me, now I have successful kernel build. The failing code was always in put_user calls, e.g. kernel/exit.s was showing: @ 1581 "kernel-source/kernel/exit.c" 1 .ifnc r0,r0; .ifnc r0r0,fpr11; .ifnc r0r0,r11fp; .ifnc r0r0,ipr12; .ifnc r0r0,r12ip; .err; .endif; .endif; .endif; .endif; .endif .ifnc r5,r2; .ifnc r5r2,fpr11; .ifnc r5r2,r11fp; .ifnc r5r2,ipr12; .ifnc r5r2,r12ip; .err; .endif; .endif; .endif; .endif; .endif .ifnc r1,r1; .ifnc r1r1,fpr11; .ifnc r1r1,r11fp; .ifnc r1r1,ipr12; .ifnc r1r1,r12ip; .err; .endif; .endif; .endif; .endif; .endif bl __put_user_4 @ 0 "" 2 with the error triggered on the middle line. /tmp/ccHq8ugv.s: Assembler messages: /tmp/ccHq8ugv.s:1179: Error: .err encountered /tmp/ccHq8ugv.s:1331: Error: .err encountered /tmp/ccHq8ugv.s:4617: Error: .err encountered /tmp/ccHq8ugv.s:6222: Error: .err encountered /tmp/ccHq8ugv.s:8705: Error: .err encountered /tmp/ccHq8ugv.s:14486: Error: .err encountered /tmp/ccHq8ugv.s:14646: Error: .err encountered /tmp/ccHq8ugv.s:14806: Error: .err encountered /tmp/ccHq8ugv.s:14966: Error: .err encountered /tmp/ccHq8ugv.s:15126: Error: .err encountered /tmp/ccHq8ugv.s:15286: Error: .err encountered That leaves only few issues in our internal components and strange failure with perf which fails to include various header files: perf/1.0-r9/perf-1.0/tools/perf/util/include/asm/byteorder.h:2:10: fatal error: ../../../../include/uapi/linux/swab.h: No such file or directory perf/1.0-r9/perf-1.0/tools/perf/util/include/asm/byteorder.h:2:10: fatal error: ../../../../include/uapi/linux/swab.h: No such file or directory perf/1.0-r9/perf-1.0/tools/perf/util/include/asm/byteorder.h:2:10: fatal error: ../../../../include/uapi/linux/swab.h: No such file or directory perf/1.0-r9/perf-1.0/tools/perf/util/include/../../../include/linux/list.h:1:28: error: #include nested too deeply perf/1.0-r9/perf-1.0/tools/perf/util/include/../../../include/linux/list.h:2:26: error: #include nested too deeply perf/1.0-r9/perf-1.0/tools/perf/util/include/../../../include/linux/list.h:3:25: error: #include nested too deeply perf/1.0-r9/perf-1.0/tools/perf/util/include/../../../include/linux/list.h:5:41: error: #include nested too deeply perf/1.0-r9/perf-1.0/tools/perf/util/include/asm/byteorder.h:2:10: fatal error: ../../../../include/uapi/linux/swab.h: No such file or directory perf/1.0-r9/perf-1.0/tools/perf/util/include/asm/byteorder.h:2:10: fatal error: ../../../../include/uapi/linux/swab.h: No such file or directory perf/1.0-r9/perf-1.0/tools/perf/util/include/../../../include/linux/list.h:1:28: error: #include nested too deeply perf/1.0-r9/perf-1.0/tools/perf/util/include/../../../include/linux/list.h:2:26: error: #include nested too deeply perf/1.0-r9/perf-1.0/tools/perf/util/include/../../../include/linux/list.h:3:25: error: #include nested too deeply perf/1.0-r9/perf-1.0/tools/perf/util/include/../../../include/linux/list.h:5:41: error: #include nested too deeply perf/1.0-r9/perf-1.0/tools/perf/util/include/../../../include/linux/list.h:1:28: error: #include nested too deeply perf/1.0-r9/perf-1.0/tools/perf/util/include/../../../include/linux/list.h:2:26: error: #include nested too deeply perf/1.0-r9/perf-1.0/tools/perf/util/include/../../../include/linux/list.h:3:25: error: #include nested too
[yocto] Using yocto as a build system
Hi, Apologies if these are basic questions but thought this will be the best place to find answers to the point So our requirement is to build open source packages in Linux, windows and Mac on a build system. Currently we have an internal build system which is quite cumbersome to manage. Hence we are looking for outside options Given our situation, is Yocto our best solution? Does it even provide for building windows and Mac open source packages? Thanks, Mamta -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] [meta-systemdev][PATCH] turbostat: pass in LDFLAGS when building the recipe
issue: do_package_qa: QA Issue: No GNU_HASH in the elf binary do_package_qa: QA run found fatal errors. Please consider fixing them. do_package_qa: Function failed: do_package_qa This indicates that binaries produced when building the recipe have not been linked with the LDFLAGS options provided by the build system. Passing in LDFLAGS using TARGET_CC_ARCH can fix it. Signed-off-by: Hongzhi.Song--- recipes-kernel/turbostat/turbostat.bb | 2 ++ 1 file changed, 2 insertions(+) diff --git a/recipes-kernel/turbostat/turbostat.bb b/recipes-kernel/turbostat/turbostat.bb index e55ec72..f4614b4 100644 --- a/recipes-kernel/turbostat/turbostat.bb +++ b/recipes-kernel/turbostat/turbostat.bb @@ -49,3 +49,5 @@ do_install() { python do_package_prepend() { d.setVar('PKGV', d.getVar("KERNEL_VERSION", True).split("-")[0]) } + +TARGET_CC_ARCH += "${LDFLAGS}" -- 2.11.0 -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[linux-yocto] LIC_FILES_CHKSUM error
Hi Bruce, We're experiencing the following error for linux-yocto-dev. ERROR: linux-yocto-dev-4.16-rc++gitAUTOINC+7c8016b5a8_731190752b-r0 do_populate_lic: QA Issue: linux-yocto-dev: The LIC_FILES_CHKSUM does not match for file://COPYING;md5=d7810fab7487fb0aad327b76f1be7cd7linux-yocto-dev: The new md5 checksum is bbea815ee2795b2f4230826c0c6b8814 This is because mainline COPYING has changed but LIC_FILES_CHKSUM in http://git.openembedded.org/openembedded-core/tree/meta/recipes-kernel/linux/linux-yocto.inc have not been updated. As linux-yocto.inc would impact linux-yocto, linux-yocto-dev and linux-yocto-VERSION, can we overwrite LIC_FILES_CHKSUM only in meta/recipes-kernel/linux/linux-yocto-dev.bb? Thanks, Zhe -- ___ linux-yocto mailing list linux-yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/linux-yocto