yocto@lists.yoctoproject.org

Home Messages Hashtags Subgroups

Expanded

Between

and

Generating a genericx86_64 - bad hddimg #yocto fnx_qt #49532 Hello, I'm trying to generate a simple genericx86_64 with Yocto 2.7 Warrior. Problem is that my hddimg is completely messed up upon generation. I have not made any particular configuration apart from adding layers and modiying the local.conf file. Here is the content of the hddimg file: % fdisk -l core-image-minimal-genericx86-64.hddimg images/genericx86-64 wagner Disk core-image-minimal-genericx86-64.hddimg: 535.4 MiB, 561386496 bytes, 1096458 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: dos Disk identifier: 0x20ac7dda Device Boot Start End Sectors Size Id Type core-image-minimal-genericx86-64.hddimg1 3224498923 3657370039 432871117 206.4G 7 HPFS/NTFS/exFAT core-image-minimal-genericx86-64.hddimg2 3272020941 5225480974 1953460034 931.5G 16 Hidden FAT16 core-image-minimal-genericx86-64.hddimg3 0 0 0 0B 6f unknown core-image-minimal-genericx86-64.hddimg4 50200576 974536369 924335794 440.8G 0 Empty Here is the bblayers.conf file: % cat bblayers.conf build/conf wagner # POKY_BBLAYERS_CONF_VERSION is increased each time build/conf/bblayers.conf # changes incompatibly POKY_BBLAYERS_CONF_VERSION = "2" BBPATH = "${TOPDIR}" BBFILES ?= "" BBLAYERS ?= " \ ${TOPDIR}/../sources/poky/meta \ ${TOPDIR}/../sources/poky/meta-poky \ ${TOPDIR}/../sources/poky/meta-yocto-bsp \ ${TOPDIR}/../sources/meta-openembedded/meta-oe \ ${TOPDIR}/../sources/meta-openembedded/meta-python \ ${TOPDIR}/../sources/meta-openembedded/meta-networking \ ${TOPDIR}/../sources/meta-openembedded/meta-filesystems \ ${TOPDIR}/../sources/meta-intel \ ${TOPDIR}/../sources/meta-virtualization \ " And here is the local.conf file (only the uncommented lines): MACHINE ??= "genericx86-64" DL_DIR ?= "/home/username/workspace/downloads" SSTATE_DIR ?= "/home/username/workspace/sstate-cache" DISTRO ?= "poky" PACKAGE_CLASSES ?= "package_rpm" EXTRA_IMAGE_FEATURES ?= "debug-tweaks" USER_CLASSES ?= "buildstats image-mklibs image-prelink" PATCHRESOLVE = "noop" BB_DISKMON_DIRS ??= "\ STOPTASKS,${TMPDIR},1G,100K \ STOPTASKS,${DL_DIR},1G,100K \ STOPTASKS,${SSTATE_DIR},1G,100K \ STOPTASKS,/tmp,100M,100K \ ABORT,${TMPDIR},100M,1K \ ABORT,${DL_DIR},100M,1K \ ABORT,${SSTATE_DIR},100M,1K \ ABORT,/tmp,10M,1K" PACKAGECONFIG_append_pn-qemu-system-native = " sdl" PACKAGECONFIG_append_pn-nativesdk-qemu = " sdl" CONF_VERSION = "1" # Include SystemD and SystemCTL DISTRO_FEATURES_append = " systemd virtualization" VIRTUAL-RUNTIME_init_manager = "systemd" VIRTUAL-RUNTIME_initscripts = "systemd-compat-units" DISTRO_FEATURES_BACKFILL_CONSIDERED = "sysvinit" # Added Docker container to the image IMAGE_INSTALL_append = " docker python3-docker-compose" Do anyone have an idea of what the problem is ?
More All Messages By This Member
Re: Yocto,core-image-minimal for RPI4 #linux #yocto Siddhartha V #49531 Am soory paul, But i was actually trying to check if sdimage is generated or not. I was unaware of . wic. bz2 image. So suggested the above commands. Sorry pankaj. Thanks Siddhartha V toggle quoted message Show quoted text On Fri, 29 May, 2020, 2:13 PM Paul Barker, <pbarker@...> wrote: On Fri, 29 May 2020 at 09:23, Siddhartha V <Siddhuvgowda.18695@...> wrote: > > Please follow below steps to check the image. > > In build directory : > to check the sdimage for installing on SD card. > > $: ls tmp/deploy/images/raspberrypi3/core-image-base-raspberrypi3.rpi-sdimg > > Check the image by running above command and then follow the steps i mentioned previously. Siddhartha, you're confusing the issue here by giving inaccurate advice. The original command posted by Pankaj was nearly correct: `sudo dd if=core-image-minimal-raspberrypi4.wic.bz2 of=/dev/sdb`. The only issue is that the data in the wic.bz2 file needs to be de-compressed before writing to an SD card. I recommend installing bmap-tools and using that to copy the data, it handles decompression automatically and uses the block map in the wic.bmap file to allow it to only write blocks which actually contain data (saving lots of time that would be otherwise wasted writing blocks of zeros). You can run `sudo bmaptool copy core-image-minimal-raspberrypi4.wic.bz2 /dev/sdb`. Thanks, Paul -- Paul Barker Konsulko Group
More All Messages By This Member
Re: Yocto,core-image-minimal for RPI4 #linux #yocto Paul Barker #49530 On Fri, 29 May 2020 at 09:23, Siddhartha V <Siddhuvgowda.18695@...> wrote: Please follow below steps to check the image. In build directory : to check the sdimage for installing on SD card. $: ls tmp/deploy/images/raspberrypi3/core-image-base-raspberrypi3.rpi-sdimg Check the image by running above command and then follow the steps i mentioned previously. Siddhartha, you're confusing the issue here by giving inaccurate advice. The original command posted by Pankaj was nearly correct: `sudo dd if=core-image-minimal-raspberrypi4.wic.bz2 of=/dev/sdb`. The only issue is that the data in the wic.bz2 file needs to be de-compressed before writing to an SD card. I recommend installing bmap-tools and using that to copy the data, it handles decompression automatically and uses the block map in the wic.bmap file to allow it to only write blocks which actually contain data (saving lots of time that would be otherwise wasted writing blocks of zeros). You can run `sudo bmaptool copy core-image-minimal-raspberrypi4.wic.bz2 /dev/sdb`. Thanks, Paul -- Paul Barker Konsulko Group
More All Messages By This Member
Re: Yocto,core-image-minimal for RPI4 #linux #yocto Siddhartha V #49529 Please follow below steps to check the image. In build directory : to check the sdimage for installing on SD card. $: ls tmp/deploy/images/raspberrypi3/core-image-base-raspberrypi3.rpi-sdimg Check the image by running above command and then follow the steps i mentioned previously. Regards, Siddhartha V toggle quoted message Show quoted text On Fri, 29 May, 2020, 1:17 PM Pankaj Vinadrao Joshi, <Pankaj.VJ@...> wrote: Hi, i dont have image with .rpi-sdimg i have image with core-image-minimal-raspberrypi4.wic.bz2 core-image-minimal-raspberrypi4.wic.bmap core-image-minimal-raspberrypi4.testdata.json core-image-minimal-raspberrypi4.tar.bz2 core-image-minimal-raspberrypi4.manifest core-image-minimal-raspberrypi4.ext3 dont have core-image-base-raspberrypi3.rpi-sdimg From: siddhartha v <siddhuvgowda.18695@...> Sent: Friday, May 29, 2020 1:07 PM To: Pankaj Vinadrao Joshi <Pankaj.VJ@...> Cc: yocto@... <yocto@...> Subject: Re: [yocto] Yocto,core-image-minimal for RPI4 #linux #yocto Hello Pankaj, Try below mentioned steps, Hope it helps you, (there my image was"core-image-base-raspberrypi3.rpi-sdimg" replace it by your image ) plug sd card to pc then $: lsblk $: sudo umount /dev/sdb* $: sudo dd if=tmp/deploy/images/raspberrypi3/core-image-base-raspberrypi3.rpi-sdimg of=/dev/sdb bs=4M >> This task will take some time and at the end we will get the output something similar(not exact it depends on build files) to below : 46+0 records in 46+0 records out 192937984 bytes (193 MB, 184 MiB) copied, 10.2155 s, 18.9 MB/s $: sync $: sudo umount /dev/sdb* Best Regards, Siddhartha V On Fri, May 29, 2020 at 12:48 PM Pankaj Vinadrao Joshi <pankaj.vj@...> wrote: Hi, I have built the image for raspberrypi4 and i have got the following images core-image-minimal.env rpi-ft5406-1-4.19.120+git0+9da67d7329-r0-raspberrypi4-20200521111428.dtbo core-image-minimal-raspberrypi4-20200518130120.rootfs.ext3 rpi-ft5406.dtbo core-image-minimal-raspberrypi4-20200518130120.rootfs.manifest rpi-ft5406-raspberrypi4.dtbo core-image-minimal-raspberrypi4-20200518130120.rootfs.tar.bz2 rpi-hwup-image.env core-image-minimal-raspberrypi4-20200518130120.rootfs.wic.bmap rpi-hwup-image- raspberrypi4-20200521111428.rootfs.ext3 core-image-minimal-raspberrypi4-20200518130120.rootfs.wic.bz2 rpi-hwup-image- raspberrypi4-20200521111428.rootfs.manifest core-image-minimal-raspberrypi4-20200518130120.testdata.json rpi-hwup-image- raspberrypi4-20200521111428.rootfs.tar.bz2 core-image-minimal-raspberrypi4.ext3 rpi-hwup-image-raspberrypi4- 20200521111428.rootfs.wic.bmap core-image-minimal-raspberrypi4.manifest rpi-hwup-image-raspberrypi4- 20200521111428.rootfs.wic.bz2 core-image-minimal-raspberrypi4.tar.bz2 core-image-minimal-raspberrypi4.testdata.json core-image-minimal-raspberrypi4.wic.bmap core-image-minimal-raspberrypi4.wic.bz2 and i am trying to copy core-image-minimal-raspberrypi4.wic.bz2 by using $sudo dd if=core-image-minimal-raspberrypi4.wic.bz2 of=/dev/sdb but my image is not getting copied into sd card(used two sd cards ,tried formatting with FAT,Linux),i am missing anything ,do i need to copy anything else with this core-image-minimal. which extension of image i should use to bringup my RPI4?? Thanks! -- Thanks and Regards. Siddhartha V. [EXT]
More All Messages By This Member
Re: Yocto,core-image-minimal for RPI4 #linux #yocto Pankaj Vinadrao Joshi #49528 Hi, i dont have image with .rpi-sdimg i have image with core-image-minimal-raspberrypi4.wic.bz2 core-image-minimal-raspberrypi4.wic.bmap core-image-minimal-raspberrypi4.testdata.json core-image-minimal-raspberrypi4.tar.bz2 core-image-minimal-raspberrypi4.manifest core-image-minimal-raspberrypi4.ext3 dont have core-image-base-raspberrypi3.rpi-sdimg toggle quoted message Show quoted text From: siddhartha v <siddhuvgowda.18695@...> Sent: Friday, May 29, 2020 1:07 PM To: Pankaj Vinadrao Joshi <Pankaj.VJ@...> Cc: yocto@... <yocto@...> Subject: Re: [yocto] Yocto,core-image-minimal for RPI4 #linux #yocto Hello Pankaj, Try below mentioned steps, Hope it helps you, (there my image was"core-image-base-raspberrypi3.rpi-sdimg" replace it by your image ) plug sd card to pc then $: lsblk $: sudo umount /dev/sdb* $: sudo dd if=tmp/deploy/images/raspberrypi3/core-image-base-raspberrypi3.rpi-sdimg of=/dev/sdb bs=4M >> This task will take some time and at the end we will get the output something similar(not exact it depends on build files) to below : 46+0 records in 46+0 records out 192937984 bytes (193 MB, 184 MiB) copied, 10.2155 s, 18.9 MB/s $: sync $: sudo umount /dev/sdb* Best Regards, Siddhartha V On Fri, May 29, 2020 at 12:48 PM Pankaj Vinadrao Joshi <pankaj.vj@...> wrote: Hi, I have built the image for raspberrypi4 and i have got the following images core-image-minimal.env rpi-ft5406-1-4.19.120+git0+9da67d7329-r0-raspberrypi4-20200521111428.dtbo core-image-minimal-raspberrypi4-20200518130120.rootfs.ext3 rpi-ft5406.dtbo core-image-minimal-raspberrypi4-20200518130120.rootfs.manifest rpi-ft5406-raspberrypi4.dtbo core-image-minimal-raspberrypi4-20200518130120.rootfs.tar.bz2 rpi-hwup-image.env core-image-minimal-raspberrypi4-20200518130120.rootfs.wic.bmap rpi-hwup-image- raspberrypi4-20200521111428.rootfs.ext3 core-image-minimal-raspberrypi4-20200518130120.rootfs.wic.bz2 rpi-hwup-image- raspberrypi4-20200521111428.rootfs.manifest core-image-minimal-raspberrypi4-20200518130120.testdata.json rpi-hwup-image- raspberrypi4-20200521111428.rootfs.tar.bz2 core-image-minimal-raspberrypi4.ext3 rpi-hwup-image-raspberrypi4- 20200521111428.rootfs.wic.bmap core-image-minimal-raspberrypi4.manifest rpi-hwup-image-raspberrypi4- 20200521111428.rootfs.wic.bz2 core-image-minimal-raspberrypi4.tar.bz2 core-image-minimal-raspberrypi4.testdata.json core-image-minimal-raspberrypi4.wic.bmap core-image-minimal-raspberrypi4.wic.bz2 and i am trying to copy core-image-minimal-raspberrypi4.wic.bz2 by using $sudo dd if=core-image-minimal-raspberrypi4.wic.bz2 of=/dev/sdb but my image is not getting copied into sd card(used two sd cards ,tried formatting with FAT,Linux),i am missing anything ,do i need to copy anything else with this core-image-minimal. which extension of image i should use to bringup my RPI4?? Thanks! -- Thanks and Regards. Siddhartha V. [EXT]
More All Messages By This Member
Re: Yocto,core-image-minimal for RPI4 #linux #yocto Siddhartha V #49527 You should have core-image-base-raspberrypi3.rpi-sdimg this should be written to to the SD card. Please check it by following below steps. Hope this help you. then follow below steps to write the image on SD card. SD_image writing In build directory : to check the sdimage for installing on SD card. ls tmp/deploy/images/raspberrypi3/core-image-base-raspberrypi3.rpi-sdimg plug sd card to pc then $: lsblk $: sudo umount /dev/sdb* $: sudo dd if=tmp/deploy/images/raspberrypi3/core-image-base-raspberrypi3.rpi-sdimg of=/dev/sdb bs=4M >> This task will take some time and at the end we will get the output something similar to below : 46+0 records in 46+0 records out 192937984 bytes (193 MB, 184 MiB) copied, 10.2155 s, 18.9 MB/s $: sync $: sudo umount /dev/sdb* Best Regards, Siddhartha V toggle quoted message Show quoted text On Fri, May 29, 2020 at 12:48 PM Pankaj Vinadrao Joshi <pankaj.vj@...> wrote: Hi, I have built the image for raspberrypi4 and i have got the following images core-image-minimal.env rpi-ft5406-1-4.19.120+git0+9da67d7329-r0-raspberrypi4-20200521111428.dtbo core-image-minimal-raspberrypi4-20200518130120.rootfs.ext3 rpi-ft5406.dtbo core-image-minimal-raspberrypi4-20200518130120.rootfs.manifest rpi-ft5406-raspberrypi4.dtbo core-image-minimal-raspberrypi4-20200518130120.rootfs.tar.bz2 rpi-hwup-image.env core-image-minimal-raspberrypi4-20200518130120.rootfs.wic.bmap rpi-hwup-image- raspberrypi4-20200521111428.rootfs.ext3 core-image-minimal-raspberrypi4-20200518130120.rootfs.wic.bz2 rpi-hwup-image- raspberrypi4-20200521111428.rootfs.manifest core-image-minimal-raspberrypi4-20200518130120.testdata.json rpi-hwup-image- raspberrypi4-20200521111428.rootfs.tar.bz2 core-image-minimal-raspberrypi4.ext3 rpi-hwup-image-raspberrypi4- 20200521111428.rootfs.wic.bmap core-image-minimal-raspberrypi4.manifest rpi-hwup-image-raspberrypi4- 20200521111428.rootfs.wic.bz2 core-image-minimal-raspberrypi4.tar.bz2 core-image-minimal-raspberrypi4.testdata.json core-image-minimal-raspberrypi4.wic.bmap core-image-minimal-raspberrypi4.wic.bz2 and i am trying to copy core-image-minimal-raspberrypi4.wic.bz2 by using $sudo dd if=core-image-minimal-raspberrypi4.wic.bz2 of=/dev/sdb but my image is not getting copied into sd card(used two sd cards ,tried formatting with FAT,Linux),i am missing anything ,do i need to copy anything else with this core-image-minimal. which extension of image i should use to bringup my RPI4?? Thanks! -- Thanks and Regards. Siddhartha V.
More All Messages By This Member
Re: Yocto,core-image-minimal for RPI4 #linux #yocto Siddhartha V #49526 Hello Pankaj, Try below mentioned steps, Hope it helps you, (there my image was"core-image-base-raspberrypi3.rpi-sdimg" replace it by your image ) plug sd card to pc then $: lsblk $: sudo umount /dev/sdb* $: sudo dd if=tmp/deploy/images/raspberrypi3/core-image-base-raspberrypi3.rpi-sdimg of=/dev/sdb bs=4M >> This task will take some time and at the end we will get the output something similar(not exact it depends on build files) to below : 46+0 records in 46+0 records out 192937984 bytes (193 MB, 184 MiB) copied, 10.2155 s, 18.9 MB/s $: sync $: sudo umount /dev/sdb* Best Regards, Siddhartha V toggle quoted message Show quoted text On Fri, May 29, 2020 at 12:48 PM Pankaj Vinadrao Joshi <pankaj.vj@...> wrote: Hi, I have built the image for raspberrypi4 and i have got the following images core-image-minimal.env rpi-ft5406-1-4.19.120+git0+9da67d7329-r0-raspberrypi4-20200521111428.dtbo core-image-minimal-raspberrypi4-20200518130120.rootfs.ext3 rpi-ft5406.dtbo core-image-minimal-raspberrypi4-20200518130120.rootfs.manifest rpi-ft5406-raspberrypi4.dtbo core-image-minimal-raspberrypi4-20200518130120.rootfs.tar.bz2 rpi-hwup-image.env core-image-minimal-raspberrypi4-20200518130120.rootfs.wic.bmap rpi-hwup-image- raspberrypi4-20200521111428.rootfs.ext3 core-image-minimal-raspberrypi4-20200518130120.rootfs.wic.bz2 rpi-hwup-image- raspberrypi4-20200521111428.rootfs.manifest core-image-minimal-raspberrypi4-20200518130120.testdata.json rpi-hwup-image- raspberrypi4-20200521111428.rootfs.tar.bz2 core-image-minimal-raspberrypi4.ext3 rpi-hwup-image-raspberrypi4- 20200521111428.rootfs.wic.bmap core-image-minimal-raspberrypi4.manifest rpi-hwup-image-raspberrypi4- 20200521111428.rootfs.wic.bz2 core-image-minimal-raspberrypi4.tar.bz2 core-image-minimal-raspberrypi4.testdata.json core-image-minimal-raspberrypi4.wic.bmap core-image-minimal-raspberrypi4.wic.bz2 and i am trying to copy core-image-minimal-raspberrypi4.wic.bz2 by using $sudo dd if=core-image-minimal-raspberrypi4.wic.bz2 of=/dev/sdb but my image is not getting copied into sd card(used two sd cards ,tried formatting with FAT,Linux),i am missing anything ,do i need to copy anything else with this core-image-minimal. which extension of image i should use to bringup my RPI4?? Thanks! -- Thanks and Regards. Siddhartha V.
More All Messages By This Member
Yocto,core-image-minimal for RPI4 #linux #yocto Pankaj Vinadrao Joshi #49525 Hi, I have built the image for raspberrypi4 and i have got the following images core-image-minimal.env rpi-ft5406-1-4.19.120+git0+9da67d7329-r0-raspberrypi4-20200521111428.dtbo core-image-minimal-raspberrypi4-20200518130120.rootfs.ext3 rpi-ft5406.dtbo core-image-minimal-raspberrypi4-20200518130120.rootfs.manifest rpi-ft5406-raspberrypi4.dtbo core-image-minimal-raspberrypi4-20200518130120.rootfs.tar.bz2 rpi-hwup-image.env core-image-minimal-raspberrypi4-20200518130120.rootfs.wic.bmap rpi-hwup-image- raspberrypi4-20200521111428.rootfs.ext3 core-image-minimal-raspberrypi4-20200518130120.rootfs.wic.bz2 rpi-hwup-image- raspberrypi4-20200521111428.rootfs.manifest core-image-minimal-raspberrypi4-20200518130120.testdata.json rpi-hwup-image- raspberrypi4-20200521111428.rootfs.tar.bz2 core-image-minimal-raspberrypi4.ext3 rpi-hwup-image-raspberrypi4- 20200521111428.rootfs.wic.bmap core-image-minimal-raspberrypi4.manifest rpi-hwup-image-raspberrypi4- 20200521111428.rootfs.wic.bz2 core-image-minimal-raspberrypi4.tar.bz2 core-image-minimal-raspberrypi4.testdata.json core-image-minimal-raspberrypi4.wic.bmap core-image-minimal-raspberrypi4.wic.bz2 and i am trying to copy core-image-minimal-raspberrypi4.wic.bz2 by using $sudo dd if=core-image-minimal-raspberrypi4.wic.bz2 of=/dev/sdb but my image is not getting copied into sd card(used two sd cards ,tried formatting with FAT,Linux),i am missing anything ,do i need to copy anything else with this core-image-minimal. which extension of image i should use to bringup my RPI4?? Thanks!
More All Messages By This Member
[ANNOUNCEMENT] Yocto Project 3.0.3 (zeus 22.0.3) Released Vineela #49524 Hello, We are pleased to announce the Yocto Project 3.0.3 (zeus-22.0.3) Release is now available for download. http://downloads.yoctoproject.org/releases/yocto/yocto-3.0.3/poky-zeus-22.0.3.tar.bz2 http://mirrors.kernel.org/yocto/yocto/yocto-3.0.3/poky-zeus-22.0.3.tar.bz2 A gpg signed version of these release notes is available at: http://downloads.yoctoproject.org/releases/yocto/yocto-3.0.3/RELEASENOTES Full Test Report: http://downloads.yoctoproject.org/releases/yocto/yocto-3.0.3/testreport.txt Thank you for everyone's contributions to this release. Sincerely, Vineela Tummalapalli Yocto Project Build and Release vineela.tummalapalli@... -------------------------- yocto-3.0.3 Release Notes -------------------------- -------------------------- Repositories/Downloads -------------------------- Repository Name: poky Repository Location: https://git.yoctoproject.org/git/poky Branch: zeus Tag: yocto-3.0.3 Git Revision: eac84e73e8d94610173c3bb3b6c6d74b58e44f60 Release Arefact: poky-zeus-22.0.3 sha: dc963c04e2a0658f8c1dff859b020611bf36bf4cde2f939f6cb7675ed19f834b Download Locations: http://downloads.yoctoproject.org/releases/yocto/yocto-3.0.3/poky-zeus-22.0.3.tar.bz2 http://mirrors.kernel.org/yocto/yocto/yocto-3.0.3/poky-zeus-22.0.3.tar.bz2 Repository Name: openembedded-core Repository Location: https://git.openembedded.org/openembedded-core Branch: zeus Tag: yocto-3.0.3 Git Revision: 9bab7c1a29a58ba7f97e253e4e0ac167b77d0e65 Release Arefact: oecore-zeus-22.0.3 sha: 8389b9795dca3580a123e58353fd508778eed741d60bb820cc075554b4944b03 Download Locations: http://downloads.yoctoproject.org/releases/yocto/yocto-3.0.3/oecore-zeus-22.0.3.tar.bz2 http://mirrors.kernel.org/yocto/yocto/yocto-3.0.3/oecore-zeus-22.0.3.tar.bz2 Repository Name: meta-mingw Repository Location: https://git.yoctoproject.org/git/meta-mingw Branch: zeus Tag: yocto-3.0.3 Git Revision: 756963cc28ebc163df7d7f4b4ee004c18d3d3260 Release Arefact: meta-mingw-zeus-22.0.3 sha: 538fc3b098ac3b8727c1f612cb3b5cba81bb2ed32d61d3beeccdea8c94cf4932 Download Locations: http://downloads.yoctoproject.org/releases/yocto/yocto-3.0.3/meta-mingw-zeus-22.0.3.tar.bz2 http://mirrors.kernel.org/yocto/yocto/yocto-3.0.3/meta-mingw-zeus-22.0.3.tar.bz2 Repository Name: meta-gplv2 Repository Location: https://git.yoctoproject.org/git/meta-gplv2 Branch: zeus Tag: yocto-3.0.3 Git Revision: 0f4eecc000f66d114ad258fa31aed66afa292166 Release Arefact: meta-gplv2-zeus-22.0.3 sha: 01d9ad212536b2ac1993aa94d84d83d710bde5910b6dcc71767f9a34d23b3810 Download Locations: http://downloads.yoctoproject.org/releases/yocto/yocto-3.0.3/meta-gplv2-zeus-22.0.3.tar.bz2 http://mirrors.kernel.org/yocto/yocto/yocto-3.0.3/meta-gplv2-zeus-22.0.3.tar.bz2 Repository Name: bitbake Repository Location: https://git.openembedded.org/bitbake Branch: zeus Tag: yocto-3.0.3 Git Revision: 6836184ef5220488a1127413c7d2e523fc37e2e9 Release Arefact: bitbake-zeus-22.0.3 sha: 6225331c9c2f85b978d15cc8f72e4b794423919ccd24f6df7988012c8e4c2262 Download Locations: http://downloads.yoctoproject.org/releases/yocto/yocto-3.0.3/bitbake-zeus-22.0.3.tar.bz2 http://mirrors.kernel.org/yocto/yocto/yocto-3.0.3/bitbake-zeus-22.0.3.tar.bz2 -------------- Contributors -------------- Adrian Bunk akuster Alexander Kanavin Alex Kiernan Anuj Mittal Armin Kuster Bruce Ashfield Changqing Li Chee Yang Lee Daisuke Yamane Denys Dmytriyenko haiqing Jan Luebbe Jeremy Puhlman Joshua Watt Julius Hemanth Pitti Jain Sangeeta Kevin Hao Khem Raj Lee Chee Yang Li Zhou Marek Vasut Mark Hatle Martin Jansa Michael Halstead Nathan Rossi Nicolas Dechesne Ovidiu Panait Paul Barker Rahul Chauhan Richard Purdie Ross Burton Stefan Ghinea Stephen Jolley Tim Orling Tom Hochstein Trevor Gamblin Vineela Tummalapalli Wang Mingyu Wenlin Kang wenlin.kang@... Yi Zhao Zhixiong Chi --------------- Known Issues --------------- Bug 13905: strace ptest failed. Bug 13906: valgrind ptest failed. Bug 13907: zlib ptest failed. These bugs were single ptest failures which appear to be intermittent in nature. In a rerun those test passed. As such we don't believe they are regressions affecting the release but runtime testing issues. --------------- Security Fixes --------------- systemd: Fix CVE-2020-1712 qemu/slirp: fix CVE-2020-7211 qemu: fix CVE-2020-7039 git: Security Advisory - git - CVE-2020-11008 git: Security Advisory - git - CVE-2020-5260 glibc: CVE-2020-1751 glib-2.0: fix CVE-2020-6750 e2fsprogs: fix CVE-2019-5188 screen: fix CVE-2020-9366 icu: fix CVE-2020-10531 bluez: fix CVE-2020-0556 libarchive: Fix CVE-2020-9308 aspell: CVE-2019-20433 sqlite: fix numerous CVEs libpcre2: fix CVE-2019-20454 qemu: fix CVE-2019-20382 glibc: CVE-2020-10029 virglrenderer: fix multiple CVEs ruby: fix CVE-2019-16254 libxml2: Fix CVE-2019-20388 libxml2: fix CVE-2020-7595 ppp: Security fix CVE-2020-8597 ncurses: add CVE_VERSION qemu: Fix CVE-2020-1711 --------------- Fixes --------------- Documentation: Prepared for 3.0.3 release resulttool/resultutils: Fix unicode error handling build-appliance-image: Update to zeus head revision poky.conf: Bump version for 3.0.3 zeus release openssl: upgrade 1.1.1f -> 1.1.1g gnutls: upgrade 3.6.12 -> 3.6.13 gnutls: upgrade 3.6.11.1 -> 3.6.12 gnutls: upgrade 3.6.8 -> 3.6.11.1 python: Upgrade 2.7.17 -> 2.17.18 gnupg: upgrade 2.2.17 -> 2.2.19 qemu: Add PACKAGECONFIG for glusterfs cve-update-db-native: clean DB if temporary file exist apt-native: don't let dpkg overwrite files by default prservice.py: fix do_package with newer Python in Ubuntu 20.04 qemu: Replace stime() API with clock_settime python3-native: Should not search the system for headers/libraries. openssl: update to 1.1.1f openssl: Upgrade 1.1.1d -> 1.1.1e openssl: recommend cryptodev-module for corresponding PACKAGECONFIG inetutils: Use alternatives to avoid manpage conflict wic: align layer plugin path pseudo: Ensure we use our own libsqlite cve-check: CPE version '-' as all version kernelsrc.bbclass: Fix externalsrc support perf: Fix externalsrc support kernel-yocto.bbclass: Support config fragments with externalsrc lib/oe/package_manager: don't try to rm /var/lib/opkg lib/oe/package_manager: avoid installing provided packages via apt lib/oe/package_manager: collect provided package names when using debs lib/oe/package_manager: fix handling of last package lib/oe/package_manager: make sure to not remove packages in apt install busybox: on upgrade save busybox if it is the last shell lttng-modules: update to 2.10.14 waffle: no need to depend on target python3 u-boot-tools: Split out inc file wic/direct: reserve 2 sector for extended partition linux-yocto/4.19: update to v4.19.107 security_flags.inc: fix flags missing from SDK toolchain e2fsprogs: backport upstream patch nfs-utils: Disable statx if using glibc emulation sanity: check for more bits of Python python3: Upgrade 3.7.6 -> 3.7.7 cve-check: fix ValueError cve-check: show whitelisted status maintainers: Add entry for buildtools-extended-tarball dhcp: Fix REQUIRE(ctx->running) assertion triggered on SIGTERM/SIGINT gcc-target.inc: Prevent sysroot from leaking into configargs.h gcc-cross.inc: Prevent native sysroot from leaking into configargs.h gcc-cross-canadian: A missing space in an append caused an invalid option wic/engine: lets display an error not a traceback dummy-sdk-package: Add DUMMYPROVIDES_PACKAGES cve-check: fail gracefully when file not found linux-yocto/5.2: backport perf build fix for latest binutils yocto-uninative.inc: version 2.8 updates glibc to 2.31 linux-yocto/5.2: update to v5.2.32 toolchain-shar-extract: ignore timestamp on decompress liberror-perl: upgrade 0.17028 -> 0.17029 perl: Fix makefile race causing configuration differences perl: Fix encode module reproducibility issues perl: fix failing ptests perl: improve reproducibility libmodule-build-perl: fix ptests perl: install typemap and other extutils metadata as part of perl-core perl: package Config.pm from arch directory into the main perl package perl: update to 5.30.1 linux-yocto/5.2: update to v5.2.29 openssh: backport patch to fix "cert not yet valid" test xserver-nodm-init: Fix the start failure for non-root user qemurunner.py: add try/except for pid handling race glibc-testsuite: Exclude this recipe from world builds glibc-testsuite: Remove the do_install task bitbake: lib/bb/utils.py: Preserve ownership of symlink
More All Messages By This Member
Re: QA notification for completed autobuilder build (yocto-2.7.4.rc2) Richard Purdie #49523 On Thu, 2020-05-28 at 00:28 -0400, William Mills via lists.yoctoproject.org wrote: On 5/27/20 6:42 PM, Michael Halstead wrote: I've rebuilt the fancyindex module and enabled it. The full filenames are displayed now. The module is disabled automatically when new versions of EPEL are released. Hopefully the change in html output doesn't break any script you've started writing. Thanks Michael. Its funny because I had switched machines in the meantime and I was scratching my head. "how does Firefox know how to do that when Chrome did not"? But I figured out you had made a change :) I also remembered "wget -r -np <url>". I have not used that is so long I forgot about it. It downloads too much but it is a quick start. (It downloads each symlink as a unique file.) So for the real solution I think I am only going to download the files that have a <file>.md5sum. I suppose I could recreate the symlinks based on heuristics of the filename but I probably won't bother. It would still be nice to have an intentionally machine readable directory of the full release content in one file in the root. md5sum and crew won't show symlink vs real files. I'll keep thinking about any existing format that might work. We do have a place we can hook in such a thing: http://git.yoctoproject.org/cgit.cgi/yocto-autobuilder-helper/tree/scripts/send-qa-email Ignore the name, its purpose has changed since it was written, its now about summarising things at the end the build and the qa email is one possible outcome. So if someone wants to have a go at summarising the release output into a file we can plug it in there. Cheers, Richard
More All Messages By This Member
[yocto-autobuilder2][master][dunfell] config.py: Add Ubuntu 20.04 workers Steve Sakoman #49522 Signed-off-by: Steve Sakoman <steve@...> --- config.py \| 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/config.py b/config.py index ab0f825..8133a29 100644 --- a/config.py +++ b/config.py @@ -101,7 +101,7 @@ publish_dest = "/srv/autobuilder/autobuilder.yoctoproject.org/pub" web_port = 8010 # List of workers in the cluster -workers_ubuntu = ["ubuntu1904-ty-1", "ubuntu1804-ty-1", "ubuntu1804-ty-2", "ubuntu1804-ty-3", "ubuntu1604-ty-1"] +workers_ubuntu = ["ubuntu2004-ty-1", "ubuntu2004-ty-2", "ubuntu1804-ty-1", "ubuntu1804-ty-2", "ubuntu1804-ty-3", "ubuntu1604-ty-1"] workers_centos = ["centos7-ty-1", "centos7-ty-2", "centos7-ty-3", "centos7-ty-4", "centos8-ty-1", "centos8-ty-2"] workers_fedora = ["fedora29-ty-1", "fedora30-ty-1", "fedora30-ty-2"] workers_debian = ["debian8-ty-1", "debian9-ty-2", "debian10-ty-1", "debian10-ty-2", "debian10-ty-3"] @@ -121,7 +121,7 @@ all_workers = workers + workers_bringup + workers_buildperf + workers_arm # Worker filtering for older releases workers_prev_releases = { - "dunfell" : ("centos7", "centos8", "debian8", "debian9", "debian10", "fedora29", "fedora30", "fedora31", "opensuse150", "opensuse151", "ubuntu1604", "ubuntu1804", "ubuntu1904", "perf-"), + "dunfell" : ("centos7", "centos8", "debian8", "debian9", "debian10", "fedora29", "fedora30", "fedora31", "opensuse150", "opensuse151", "ubuntu1604", "ubuntu1804", "ubuntu1904", "ubuntu2004", "perf-"), "zeus" : ("centos7", "debian8", "debian9", "debian10", "fedora28", "fedora29", "fedora30", "opensuse150", "opensuse151", "ubuntu1604", "ubuntu1804", "ubuntu1904", "perf-"), "warrior" : ("centos7", "debian8", "debian9", "debian10", "fedora28", "fedora29", "fedora30", "opensuse150", "opensuse151", "ubuntu1604", "ubuntu1804", "ubuntu1904", "perf-"), "thud" : ("centos7", "debian8", "debian9", "debian10", "fedora28", "fedora29", "fedora30", "opensuse150", "opensuse151", "ubuntu1604", "ubuntu1804", "ubuntu1904", "perf-"), -- 2.17.1
More All Messages By This Member
debug makefile based c-helloworld application Christian Schmidt #49521 I try to debug a simple helloworld program but i can't see the source code. My approach: hello.c ``` #include<stdio.h> int main() { printf("Hello World\n"); return 0; } ``` hellome.bb ``` # # This file was derived from the 'Hello World!' example recipe in the # Yocto Project Development Manual. # SUMMARY = "Simple helloworld application" LICENSE = "CLOSED" SRC_URI = "file://hello.c" S = "${WORKDIR}" TARGET_CC_ARCH += "${LDFLAGS}" do_compile() { ${CC} hello.c -o -g -O0 hello } do_install() { install -d ${D}${bindir} install -m 0755 hello ${D}${bindir} } ``` Makefile ``` SOURCES=hello.c OBJECTS=$(SOURCES:.c=.o) EXEC=hello #EXTRACFLAGS=-ansi all: $(SOURCES) $(EXEC) $(EXEC): $(OBJECTS) $(CC) $(CFLAGS) $(EXTRACFLAGS) $(OBJECTS) -o $@ %.o : %c $(CC) $(CFLAGS) $(EXTRACFLAGS) -c $< install: install $(EXEC) $(DESTDIR)/usr/bin clean: rm -rf *.o $(EXEC) ``` local.conf ``` .... IMAGE_INSTALL_append = " hellome hellome-dbg hellome-dev" EXTRA_IMAGE_FEATURES += "\ dbg-pkgs \ tools-debug \ debug-tweaks \ dev-pkgs" # Specifies to build packages with debugging information DEBUG_BUILD = "1" # Do not remove debug symbols INHIBIT_PACKAGE_STRIP = "1" ``` on the target: ``` root@qemuarm:~# hello Hello World root@qemuarm:~# gdb /usr/bin/hello Reading symbols from /usr/bin/hello... (gdb) b main Breakpoint 1 at 0x518 (gdb) r Starting program: /usr/bin/hello Breakpoint 1, 0x00400518 in main () (gdb) list 1 longjmp.c: No such file or directory. (gdb) list 1 file: "../setjmp/longjmp.c", line number: 1, symbol: "???" 1 ../setjmp/longjmp.c: No such file or directory. file: "longjmp.c", line number: 1, symbol: "???" 1 longjmp.c: No such file or directory. ```
More All Messages By This Member
Re: #yocto #raspberrypi #linux . Failure to build xen-image-minimal. Yocto bitbake failed @99% while building xen-minimal-image. #yocto #raspberrypi #linux Siddhartha V #49520 hello sir, Thanks for the reply. I searched for what you have suggested, but it looks like I am missing something here. I didn't see kernel.conf file I have shared my bblayers.conf details also , please let me know what I am missing here. I am using the yocto for the first time for kernel build. Please suggest me if I am doing anything wrong here. Below is the bblayers.conf file details: # POKY_BBLAYERS_CONF_VERSION is increased each time build/conf/bblayers.conf # changes incompatibly POKY_BBLAYERS_CONF_VERSION = "2" BBPATH = "${TOPDIR}" BBFILES ?= "" BBLAYERS ?= " \ /home/siddhu/Documents/yocto/sources/poky/meta \ /home/siddhu/Documents/yocto/sources/poky/meta-poky \ /home/siddhu/Documents/yocto/sources/poky/meta-yocto-bsp \ /home/siddhu/Documents/yocto/sources/meta-openembedded/meta-oe \ /home/siddhu/Documents/yocto/sources/meta-openembedded/meta-multimedia \ /home/siddhu/Documents/yocto/sources/meta-openembedded/meta-python \ /home/siddhu/Documents/yocto/sources/meta-openembedded/meta-networking \ /home/siddhu/Documents/yocto/sources/meta-openembedded/meta-filesystems \ /home/siddhu/Documents/yocto/sources/meta-cloud-services \ /home/siddhu/Documents/yocto/sources/meta-selinux \ /home/siddhu/Documents/yocto/sources/meta-virtualization\ /home/siddhu/Documents/yocto/sources/meta-raspberrypi \ " Am I missing any layers here? Please suggest me Regards, Siddhartha V toggle quoted message Show quoted text On Thu, 28 May, 2020, 9:12 PM Khem Raj, <raj.khem@...> wrote: On 5/27/20 3:37 AM, Siddhartha V wrote: > Hello, > > I am building the xen minimal image using yocto warrior* ("bitbake > xen-image-minimal") by giving the target machine as "raspberrypi4". > It reached 99% but at last I got below error and the whole process > terminated with error. > > ERROR: xen-image-minimal-1.0-r0 do_rootfs: Could not invoke dnf. Command > '/home/siddhu/Documents/yocto/build/tmp/work/raspberrypi4-poky-linux-gnueabi/xen-image-minimal/1.0-r0/recipe-sysroot-native/usr/bin/dnf > -v --rpmverbosity=info -y -c > /home/siddhu/Documents/yocto/build/tmp/work/raspberrypi4-poky-linux-gnueabi/xen-image-minimal/1.0-r0/rootfs/etc/dnf/dnf.conf > --setopt=reposdir=/home/siddhu/Documents/yocto/build/tmp/work/raspberrypi4-poky-linux-gnueabi/xen-image-minimal/1.0-r0/rootfs/etc/yum.repos.d > --installroot=/home/siddhu/Documents/yocto/build/tmp/work/raspberrypi4-poky-linux-gnueabi/xen-image-minimal/1.0-r0/rootfs > --setopt=logdir=/home/siddhu/Documents/yocto/build/tmp/work/raspberrypi4-poky-linux-gnueabi/xen-image-minimal/1.0-r0/temp > --repofrompath=oe-repo,/home/siddhu/Documents/yocto/build/tmp/work/raspberrypi4-poky-linux-gnueabi/xen-image-minimal/1.0-r0/oe-rootfs-repo > --nogpgcheck install kernel-module-xen-blkback > kernel-module-xen-gntalloc kernel-module-xen-gntdev > kernel-module-xen-netback kernel-module-xen-wdt packagegroup-core-boot > packagegroup-core-ssh-dropbear packagegroup-core-ssh-openssh qemu > run-postinsts xen-base locale-base-en-us locale-base-en-gb' returned 1: > > DNF version: 4.1.0 > > cachedir: > /home/siddhu/Documents/yocto/build/tmp/work/raspberrypi4-poky-linux-gnueabi/xen-image-minimal/1.0-r0/rootfs/var/cache/dnf > > Added oe-repo repo from > /home/siddhu/Documents/yocto/build/tmp/work/raspberrypi4-poky-linux-gnueabi/xen-image-minimal/1.0-r0/oe-rootfs-repo > > repo: using cache for: oe-repo > > not found other for: > > not found modules for: > > not found deltainfo for: > > not found updateinfo for: > > oe-repo: using metadata from Wed 27 May 2020 06:15:39 AM UTC. > > Last metadata expiration check: 0:00:01 ago on Wed 27 May 2020 06:15:45 > AM UTC. > > No module defaults found > > No match for argument: kernel-module-xen-blkback > > No match for argument: kernel-module-xen-gntalloc > > No match for argument: kernel-module-xen-gntdev > > No match for argument: kernel-module-xen-netback > > No match for argument: kernel-module-xen-wdt > it seems XEN related options are missing from kernel config. Perhaps you can add a config fragment adding them and stitch it to linux-raspberrypi recipe via bbappend. > Error: Unable to find a match > > ERROR: xen-image-minimal-1.0-r0 do_rootfs: > > ERROR: xen-image-minimal-1.0-r0 do_rootfs: Function failed: do_rootfs > > ERROR: Logfile of failure stored in: > /home/siddhu/Documents/yocto/build/tmp/work/raspberrypi4-poky-linux-gnueabi/xen-image-minimal/1.0-r0/temp/log.do_rootfs.14256 > > ERROR: Task > (/home/siddhu/Documents/yocto/sources/meta-virtualization/recipes-extended/images/xen-image-minimal.bb:do_rootfs) > failed with exit code '1' > > NOTE: Tasks Summary: Attempted 2605 tasks of which 2152 didn't need to > be rerun and 1 failed. > > Summary: 1 task failed: > > > /home/siddhu/Documents/yocto/sources/meta-virtualization/recipes-extended/images/xen-image-minimal.bb:do_rootfs > > Summary: There were 3 ERROR messages shown, returning a non-zero exit code. > > May I know what mistake I am doing here please. I have attached > screenshot also. > > > My bblayer.conf file is as below:* > > # POKY_BBLAYERS_CONF_VERSION is increased each time build/conf/bblayers.conf > # changes incompatibly > POKY_BBLAYERS_CONF_VERSION = "2" > BBPATH = "${TOPDIR}" > > BBFILES ?= "" > BBLAYERS ?= " \ > > /home/siddhu/Documents/yocto/sources/poky/meta \ > /home/siddhu/Documents/yocto/sources/poky/meta-poky \ > /home/siddhu/Documents/yocto/sources/poky/meta-yocto-bsp \ > /home/siddhu/Documents/yocto/sources/meta-openembedded/meta-oe \ > /home/siddhu/Documents/yocto/sources/meta-openembedded/meta-multimedia \ > /home/siddhu/Documents/yocto/sources/meta-openembedded/meta-python \ > /home/siddhu/Documents/yocto/sources/meta-openembedded/meta-networking \ > /home/siddhu/Documents/yocto/sources/meta-openembedded/meta-filesystems \ > /home/siddhu/Documents/yocto/sources/meta-cloud-services \ > /home/siddhu/Documents/yocto/sources/meta-selinux \ > /home/siddhu/Documents/yocto/sources/meta-virtualization\ > /home/siddhu/Documents/yocto/sources/meta-raspberrypi \ > " > > My local.conf file I have added the below details: > > MACHINE ??= "raspberrypi4" > DISTRO_FEATURES += "virtualization xen" > PACKAGE_CLASSES ?= "package_rpm" > CONF_VERSION = "1" > IMAGE_FEATURES += "ssh-server-dropbear" > > > I have tried the same for "cubieboard2" also even there I faced the same > issue.Eagerly waiting for the response. > > Regards, > Siddhartha V > > > >
More All Messages By This Member
Re: #yocto #raspberrypi #linux . Failure to build xen-image-minimal. Yocto bitbake failed @99% while building xen-minimal-image. #yocto #raspberrypi #linux Khem Raj #49519 On 5/27/20 3:37 AM, Siddhartha V wrote: Hello, I am building the xen minimal image using yocto warrior* ("bitbake xen-image-minimal") by giving the target machine as "raspberrypi4". It reached 99% but at last I got below error and the whole process terminated with error. ERROR: xen-image-minimal-1.0-r0 do_rootfs: Could not invoke dnf. Command '/home/siddhu/Documents/yocto/build/tmp/work/raspberrypi4-poky-linux-gnueabi/xen-image-minimal/1.0-r0/recipe-sysroot-native/usr/bin/dnf -v --rpmverbosity=info -y -c /home/siddhu/Documents/yocto/build/tmp/work/raspberrypi4-poky-linux-gnueabi/xen-image-minimal/1.0-r0/rootfs/etc/dnf/dnf.conf --setopt=reposdir=/home/siddhu/Documents/yocto/build/tmp/work/raspberrypi4-poky-linux-gnueabi/xen-image-minimal/1.0-r0/rootfs/etc/yum.repos.d --installroot=/home/siddhu/Documents/yocto/build/tmp/work/raspberrypi4-poky-linux-gnueabi/xen-image-minimal/1.0-r0/rootfs --setopt=logdir=/home/siddhu/Documents/yocto/build/tmp/work/raspberrypi4-poky-linux-gnueabi/xen-image-minimal/1.0-r0/temp --repofrompath=oe-repo,/home/siddhu/Documents/yocto/build/tmp/work/raspberrypi4-poky-linux-gnueabi/xen-image-minimal/1.0-r0/oe-rootfs-repo --nogpgcheck install kernel-module-xen-blkback kernel-module-xen-gntalloc kernel-module-xen-gntdev kernel-module-xen-netback kernel-module-xen-wdt packagegroup-core-boot packagegroup-core-ssh-dropbear packagegroup-core-ssh-openssh qemu run-postinsts xen-base locale-base-en-us locale-base-en-gb' returned 1: DNF version: 4.1.0 cachedir: /home/siddhu/Documents/yocto/build/tmp/work/raspberrypi4-poky-linux-gnueabi/xen-image-minimal/1.0-r0/rootfs/var/cache/dnf Added oe-repo repo from /home/siddhu/Documents/yocto/build/tmp/work/raspberrypi4-poky-linux-gnueabi/xen-image-minimal/1.0-r0/oe-rootfs-repo repo: using cache for: oe-repo not found other for: not found modules for: not found deltainfo for: not found updateinfo for: oe-repo: using metadata from Wed 27 May 2020 06:15:39 AM UTC. Last metadata expiration check: 0:00:01 ago on Wed 27 May 2020 06:15:45 AM UTC. No module defaults found No match for argument: kernel-module-xen-blkback No match for argument: kernel-module-xen-gntalloc No match for argument: kernel-module-xen-gntdev No match for argument: kernel-module-xen-netback No match for argument: kernel-module-xen-wdt it seems XEN related options are missing from kernel config. Perhaps you can add a config fragment adding them and stitch it to linux-raspberrypi recipe via bbappend. Error: Unable to find a match ERROR: xen-image-minimal-1.0-r0 do_rootfs: ERROR: xen-image-minimal-1.0-r0 do_rootfs: Function failed: do_rootfs ERROR: Logfile of failure stored in: /home/siddhu/Documents/yocto/build/tmp/work/raspberrypi4-poky-linux-gnueabi/xen-image-minimal/1.0-r0/temp/log.do_rootfs.14256 ERROR: Task (/home/siddhu/Documents/yocto/sources/meta-virtualization/recipes-extended/images/xen-image-minimal.bb:do_rootfs) failed with exit code '1' NOTE: Tasks Summary: Attempted 2605 tasks of which 2152 didn't need to be rerun and 1 failed. Summary: 1 task failed: /home/siddhu/Documents/yocto/sources/meta-virtualization/recipes-extended/images/xen-image-minimal.bb:do_rootfs Summary: There were 3 ERROR messages shown, returning a non-zero exit code. May I know what mistake I am doing here please. I have attached screenshot also. My bblayer.conf file is as below:* # POKY_BBLAYERS_CONF_VERSION is increased each time build/conf/bblayers.conf # changes incompatibly POKY_BBLAYERS_CONF_VERSION = "2" BBPATH = "${TOPDIR}" BBFILES ?= "" BBLAYERS ?= " \ /home/siddhu/Documents/yocto/sources/poky/meta \ /home/siddhu/Documents/yocto/sources/poky/meta-poky \ /home/siddhu/Documents/yocto/sources/poky/meta-yocto-bsp \ /home/siddhu/Documents/yocto/sources/meta-openembedded/meta-oe \ /home/siddhu/Documents/yocto/sources/meta-openembedded/meta-multimedia \ /home/siddhu/Documents/yocto/sources/meta-openembedded/meta-python \ /home/siddhu/Documents/yocto/sources/meta-openembedded/meta-networking \ /home/siddhu/Documents/yocto/sources/meta-openembedded/meta-filesystems \ /home/siddhu/Documents/yocto/sources/meta-cloud-services \ /home/siddhu/Documents/yocto/sources/meta-selinux \ /home/siddhu/Documents/yocto/sources/meta-virtualization\ /home/siddhu/Documents/yocto/sources/meta-raspberrypi \ " My local.conf file I have added the below details: MACHINE ??= "raspberrypi4" DISTRO_FEATURES += "virtualization xen" PACKAGE_CLASSES ?= "package_rpm" CONF_VERSION = "1" IMAGE_FEATURES += "ssh-server-dropbear" I have tried the same for "cubieboard2" also even there I faced the same issue.Eagerly waiting for the response. Regards, Siddhartha V
More All Messages By This Member
Re: #yocto #yocto Khem Raj #49518 On 5/24/20 8:22 AM, msrinivasan@... wrote: Hi, I am cross compile nodejs 12.16 recipe for ARM v7 target using Yocto 2.2. I can built nodejs as a individual task (i.e. bitbake -c compile) (with some changes in recipe) with dependency over openssl 1.1.1b recipe from Yocto 2.6. But further build (i.e. bitbake nodejs) fails with dependency rpm-native's compile which depend on default openssl 1.0.2j from sysroot folder (STAGING_DIR) (currently has openssl 1.1.1b's header files at sysroot folder). My aim to have quiet build of nodejs with dependency on openssl 1.1.1b only and rest of build depend over openssl 1.0.2q. Finally with reference from sysroot (STAGING_DIR), image must contains both openssl versions (1.1.1b, 1.0.2q) share libraries. Please let me know your inputs. they can live together, but you need to tweak the linking pieces, however, I wonder why rpm-native is coming into play for a target package Thanks & Regards Manjunatha Srinivasan N
More All Messages By This Member
Re: QA notification for completed autobuilder build (yocto-2.7.4.rc2) Armin Kuster #49517 On 5/27/20 8:34 PM, Jain, Sangeeta wrote: Hello All, Intel and WR YP QA is planning for QA execution for YP build yocto-2.7.4.rc2. We are planning to execute following tests for this cycle: OEQA-manual tests for following module: 1. OE-Core 2. BSP-hw Runtime auto test for following platforms: 1. MinnowTurbot 32-bit 2. Coffee Lake 3. NUC 7 4. NUC 6 5. Edgerouter 6. MPC8315e-rdb 7. Beaglebone ETA for completion is Monday, June 01. Sounds good. Thanks, - armin Thanks, Sangeeta -----Original Message----- From: yocto@... <yocto@...> On Behalf Of pokybuild@... Sent: Wednesday, 27 May, 2020 8:09 PM To: yocto@... Cc: otavio@...; yi.zhao@...; Sangal, Apoorv <apoorv.sangal@...>; Yeoh, Ee Peng <ee.peng.yeoh@...>; Chan, Aaron Chun Yew <aaron.chun.yew.chan@...>; richard.purdie@...; akuster808@...; sjolley.yp.pm@...; Jain, Sangeeta <sangeeta.jain@...> Subject: [yocto] QA notification for completed autobuilder build (yocto- 2.7.4.rc2) A build flagged for QA (yocto-2.7.4.rc2) was completed on the autobuilder and is available at: https://autobuilder.yocto.io/pub/releases/yocto-2.7.4.rc2 Build hash information: bitbake: 7f7126211170439ac1d7d72e980786ce0edb7bb7 meta-gplv2: d5d9fc9a4bbd365d6cd6fe4d6a8558f7115c17da meta-intel: 29ee4852a05931dcf856670d9d8a3c3077a40fe8 meta-mingw: 10695afe8cd406844e0d0dd868c11677e07557d4 oecore: db3ce703d03b18e8a4120969d32ff7f344f34fe9 poky: f65b24e9ca0918a4ede70ea48ed8b7cc4620f07f This is an automated message from the Yocto Project Autobuilder Git: git://git.yoctoproject.org/yocto-autobuilder2 Email: richard.purdie@...
More All Messages By This Member
Re: #apt #linux #yocto #raspberrypi., apt, gcc, sudo not present #apt #linux #yocto Ross Burton <ross@...> #49516 On Wed, 27 May 2020 at 11:06, Siddhartha V <Siddhuvgowda.18695@...> wrote: Hello, I built the image for Raspberrypi3B+ board. But when boot the board gcc, apt, sudo were not there. Actually only the poweron and poweroff and few basic commnds like, ls, mkdir, whoami were working. May I konw what wrong I did while building please. I am using yocto warrior. I used "bitbake core-image-base" command for building. You did nothing wrong, precisely. core-image-base is a base image that doesn’t do much beyond boot into a working command line environment. If you want a working toolchain (gcc and friends) on the image then add “tools-sdl” to IMAGE_FEATURES. By default toolchains are not included because they’re huge and not needed. If you want apt then first change the package manager to deb by changing your explicit assignment of PACKAGE_CLASSES. This builds the image with apt, and if you also want a working apt and package database in the image then add package-management to IMAGE_FEATURES. To add sudo, simple add sudo to IMAGE_INSTALL. I recommend looking up those variables in the documentation to understand what they do. Ross
More All Messages By This Member
Re: #apt #linux #yocto #raspberrypi., apt, gcc, sudo not present #apt #linux #yocto Josef Holzmayr <holzmayr@...> #49515 Howdy! Am 27.05.2020 um 12:06 schrieb Siddhartha V: Hello, I built the image for Raspberrypi3B+ board. But when boot the board gcc, apt, sudo were not there. Actually only the poweron and poweroff and few basic commnds like, ls, mkdir, whoami were working. May I konw what wrong I did while building please. This sounds like you actually want an ubuntu. Why not just use it, then? Beating a yocto build into shape will always just leave you wanting and complaining, unless you are willing to get rid of your assumptions. Hint: The frist things you have to get out of your head are expecting apt, sudo and gcc on the board. Reasoning: - no apt, because the images are usually constructed at build time including all expected software. Runtime package management is actually rarely needed. - no sudo, because you can just log in as whatever user you want to. And in the product case it has no use because usually people do not login, hence no need for its security means. - no gcc, because all compilation is meant to happen at image building time, or at least on the development host. Of course this is only a very generic, top-level explanation and use cases diffee. But If the mindset does not fit right from the beginning, then there only lies trouble ahead. Greetz -- _____________________________________________________________ R-S-I Elektrotechnik GmbH & Co. KG Woelkestrasse 11 D-85301 Schweitenkirchen Fon: +49 8444 9204-0 Fax: +49 8444 9204-50 www.rsi-elektrotechnik.de _____________________________________________________________ Amtsgericht Ingolstadt - GmbH: HRB 191328 - KG: HRA 170363 Geschäftsführer: Dr.-Ing. Michael Sorg, Dipl.-Ing. Franz Sorg USt-IdNr.: DE 128592548
More All Messages By This Member
Re: #apt #linux #yocto #raspberrypi., apt, gcc, sudo not present #apt #linux #yocto Mark Van De Vyver <mark@...> #49514 Hi Siddhartha, Caveat: This is generally what I've done, and not specific to any rpi or rhel setup.... If you run `bitbake -e core-image-base \| grep "^IMAGE_FEATURES" you'll be able to see what was configured. You can also filter _FEATURES to get a better idea of what went on in terms of machine and compatible features. Next, with that data in mind you can read the ./<build-folder>/bitbake-cookerdaemon.log When reading this you will see various files are loaded - opening each of them in turn you might see some code that turns off what you expected to have installed. Or you might notice that the packages you expected to be installed were never put forward for installation. Not sure if that helps. I've run into some wrinkles where a package wasn't available, and became so only after adding a 'seemingly' (to me that is) unrelated layer - but in those cases I got a warning the package could not be found. Sounds like that is not* happening here. Sorry I can't be of better assistance. HTH?
More All Messages By This Member
Re: QA notification for completed autobuilder build (yocto-2.7.4.rc2) William Mills <wmills@...> #49513 On 5/27/20 6:42 PM, Michael Halstead wrote: I've rebuilt the fancyindex module and enabled it. The full filenames are displayed now. The module is disabled automatically when new versions of EPEL are released. Hopefully the change in html output doesn't break any script you've started writing. Thanks Michael. Its funny because I had switched machines in the meantime and I was scratching my head. "how does Firefox know how to do that when Chrome did not"? But I figured out you had made a change :) I also remembered "wget -r -np <url>". I have not used that is so long I forgot about it. It downloads too much but it is a quick start. (It downloads each symlink as a unique file.) So for the real solution I think I am only going to download the files that have a <file>.md5sum. I suppose I could recreate the symlinks based on heuristics of the filename but I probably won't bother. It would still be nice to have an intentionally machine readable directory of the full release content in one file in the root. md5sum and crew won't show symlink vs real files. I'll keep thinking about any existing format that might work. I found and closed a few old <https://bugzilla.yoctoproject.org/show_bug.cgi?id=12416>bugs <https://bugzilla.yoctoproject.org/show_bug.cgi?id=11249> about this. I think the issue has been fixed and returned a few times since these bugs were filed. Nice. Thanks, Bill
More All Messages By This Member

10661 - 10680 of 60181

Home Hashtags Subgroups Terms