> Am 10.09.2018 um 21:09 schrieb Martin Jansa <martin.ja...@gmail.com>: > > pn-buildlist isn't really useful in this case, building both coreutils and > busybox doesn't imply that both will be actually included in the image.. > > If you compare installed-package-names.txt in buildhistory you'll see that > only the core-image-minimal-dev has coreutils installed. > > docker-shr qemux86-64@ ~/build/oe-core/buildhistory/images/qemux86_64/glibc $ > grep busybox core-image-minimal*/installed-package-names.txt > core-image-minimal-dev/installed-package-names.txt:busybox > core-image-minimal-dev/installed-package-names.txt:busybox-dev > core-image-minimal-dev/installed-package-names.txt:busybox-syslog > core-image-minimal-dev/installed-package-names.txt:busybox-udhcpc > core-image-minimal/installed-package-names.txt:busybox > core-image-minimal/installed-package-names.txt:busybox-syslog > core-image-minimal/installed-package-names.txt:busybox-udhcpc > docker-shr qemux86-64@ ~/build/oe-core/buildhistory/images/qemux86_64/glibc $ > grep coreutils core-image-minimal*/installed-package-names.txt > core-image-minimal-dev/installed-package-names.txt:coreutils > core-image-minimal-dev/installed-package-names.txt:coreutils-dev > > That's why the issue is shown only in core-image-minimal-dev.
The files "installed-package-names.txt" are not available in my setup (IIRC one has to enable that explicitly). > Do you have custom busybox defconfig which enables nice applet? It's not > enabled in default config: > meta/recipes-core/busybox/busybox/defconfig:# CONFIG_NICE is not set You're right. Ages ago - in April 2015 - I added that to my busybox configuration, since I need a nice for some scripts on target. And since you figured out, coreutils is (likely with reason) not available in general for some images, others might have that, too. So I created a small patch for corutils ;) Thanks for figuring that out. Cheers, Jens > On Mon, Sep 10, 2018 at 8:15 PM Jens Rehsack <rehs...@gmail.com > <mailto:rehs...@gmail.com>> wrote: > > >> Am 09.09.2018 um 20:56 schrieb Martin Jansa <martin.ja...@gmail.com >> <mailto:martin.ja...@gmail.com>>: >> >> Does core-image-minimal include both busybox and coreutils? Maybe only -dev >> include both. > > Unfortunately both include coreutils, see attached pn-buildlist (I can send > you the recipe-depends and the task-depends, either if you need them). > >> I'll send fix for attr soon, waiting for some builds to finish testing it. > > Seems similar to my kind of soon :-) > >> On Sun, Sep 9, 2018 at 8:47 PM Jens Rehsack <rehs...@gmail.com >> <mailto:rehs...@gmail.com>> wrote: >> So far, so good. >> >> They way to fix that seems either to check why busybox uses ${base_bindir} >> nowadays in favor of ${bindir} and fix either busybox or coreutils or attr. >> >> What drives me nuts is not only the failure after the busybox update - why >> does core-image-minimal builds successful while core-image-minimal-dev fails? >> >> Cheers, >> Jens >> >>> Am 09.09.2018 um 19:27 schrieb Martin Jansa <martin.ja...@gmail.com >>> <mailto:martin.ja...@gmail.com>>: >>> >>> busybox is most likely the one providing it in ${base_bindir} >>> >>> Recent busybox upgrade probably moved this file. >>> >>> There is also conflict on /usr/bin/setfattr between busybox and attr now. >>> >>> On Sun, Sep 9, 2018 at 7:22 PM Martin Jansa <martin.ja...@gmail.com >>> <mailto:martin.ja...@gmail.com>> wrote: >>> There are 2 packages using u-a for nice, but one is using {bindir} and 2nd >>> one is using {base_bindir} >>> >>> coreutils is using bindir, find what's using ${base_bindir} and change one >>> of them to use the same u-a link as the other one. >>> >>> On Sun, Sep 9, 2018 at 5:59 PM Jens Rehsack <rehs...@gmail.com >>> <mailto:rehs...@gmail.com>> wrote: >>> >>> >>>> Am 09.09.2018 um 13:15 schrieb Alexander Kanavin <alex.kana...@gmail.com >>>> <mailto:alex.kana...@gmail.com>>: >>>> >>>> It's right in the message? >>>> >>>> ERROR: Logfile of failure stored in: >>>> /home/sno/gpw-community-bsp/mops-yocto-platform/tmp/work/fischer-poky-linux/core-image-minimal-dev/1.0-r0/temp/log.do_rootfs.27709 >>>> >>>> Alex >>> >>> >>> It's not much what stands there: >>> >>> Downloading >>> file:/home/sno/gpw-community-bsp/mops-yocto-platform/tmp/work/fischer-poky-linux/core-image-minimal-dev/1.0-r0/oe-rootfs-repo/core2-64/libcap-dev_2.25-r0_core2-64.ipk. >>> Installing coreutils-dev (8.30) on root >>> [...] >>> Configuring update-rc.d-deupdate-alternatives: Linking >>> /home/sno/gpw-community-bsp/mops-yocto-platform/tmp/work/fischer-poky-linux/core-image-minimal-dev/1.0-r0/rootfs/usr/bin/diff >>> to /usr/bin/diff.diffutils >>> update-alternatives: Linking >>> /home/sno/gpw-community-bsp/mops-yocto-platform/tmp/work/fischer-poky-linux/core-image-minimal-dev/1.0-r0/rootfs/usr/bin/cmp >>> to /usr/bin/cmp.diffutils >>> update-alternatives: Linking >>> /home/sno/gpw-community-bsp/mops-yocto-platform/tmp/work/fischer-poky-linux/core-image-minimal-dev/1.0-r0/rootfs/bin/umount >>> to /bin/umount.util-linux >>> update-alternatives: Linking >>> /home/sno/gpw-community-bsp/mops-yocto-platform/tmp/work/fischer-poky-linux/core-image-minimal-dev/1.0-r0/rootfs/usr/bin/[ >>> to /usr/bin/lbracket.coreutils >>> update-alternatives: Linking >>> /home/sno/gpw-community-bsp/mops-yocto-platform/tmp/work/fischer-poky-linux/core-image-minimal-dev/1.0-r0/rootfs/usr/bin/arch >>> to /usr/bin/arch.coreutils >>> update-alternatives: Linking >>> /home/sno/gpw-community-bsp/mops-yocto-platform/tmp/work/fischer-poky-linux/core-image-minimal-dev/1.0-r0/rootfs/usr/bin/basename >>> to /usr/bin/basename.coreutils >>> update-alternatives: Linking >>> /home/sno/gpw-community-bsp/mops-yocto-platform/tmp/work/fischer-poky-linux/core-image-minimal-dev/1.0-r0/rootfs/usr/bin/chcon >>> to /usr/bin/chcon.coreutils >>> update-alternatives: Linking >>> /home/sno/gpw-community-bsp/mops-yocto-platform/tmp/work/fischer-poky-linux/core-image-minimal-dev/1.0-r0/rootfs/usr/bin/cksum >>> to /usr/bin/cksum.coreutils >>> update-alternatives: Linking >>> /home/sno/gpw-community-bsp/mops-yocto-platform/tmp/work/fischer-poky-linux/core-image-minimal-dev/1.0-r0/rootfs/usr/bin/comm >>> to /usr/bin/comm.coreutils >>> update-alternatives: Linking >>> /home/sno/gpw-community-bsp/mops-yocto-platform/tmp/work/fischer-poky-linux/core-image-minimal-dev/1.0-r0/rootfs/usr/bin/csplit >>> to /usr/bin/csplit.coreutils >>> update-alternatives: Linking >>> /home/sno/gpw-community-bsp/mops-yocto-platform/tmp/work/fischer-poky-linux/core-image-minimal-dev/1.0-r0/rootfs/usr/bin/cut >>> to /usr/bin/cut.coreutils >>> [...] >>> update-alternatives: Linking >>> /home/sno/gpw-community-bsp/mops-yocto-platform/tmp/work/fischer-poky-linux/core-image-minimal-dev/1.0-r0/rootfs/usr/bin/mkfifo >>> to /usr/bin/mkfifo.coreutils >>> update-alternatives: renaming nice link from /bin/nice to /usr/bin/nice >>> mv: cannot stat '/bin/nice': No such file or directory >>> update-alternatives: Linking >>> /home/sno/gpw-community-bsp/mops-yocto-platform/tmp/work/fischer-poky-linux/core-image-minimal-dev/1.0-r0/rootfs/bin/bash >>> to /bin/bash.bash >>> [...] >>> Configuring libgmp10. >>> Configuring coreutils. >>> coreutils.postinst returned 1, marking as unpacked only, configuration >>> required on target. >>> Configuring acl. >>> [...] >>> >>> The postinst file of coreutils contains only a long list of >>> update-alternatives, as many other packages do either. >>> >>> core-image-minimal contains coreutils as well, but it doesn't fail the same >>> way. >>> >>> Any ideas? >>> >>>> 2018-09-09 10:58 GMT+02:00 Jens Rehsack <rehs...@gmail.com >>>> <mailto:rehs...@gmail.com>>: >>>>> Hi, >>>>> >>>>> I got following issue when building an image for live-debugging: >>>>> >>>>> ERROR: updatable-app-dev-image-1.0-r0 do_rootfs: Postinstall scriptlets >>>>> of ['coreutils'] have failed. If the intention is to defer them to first >>>>> boot, >>>>> then please place them into pkg_postinst_ontarget_${PN} (). >>>>> Deferring to first boot via 'exit 1' is no longer supported. >>>>> Details of the failure are in >>>>> /home/sno/gpw-community-bsp/mops-yocto-platform/tmp/work/fischer-poky-linux/updatable-app-dev-image/1.0-r0/temp/log.do_rootfs. >>>>> ERROR: updatable-app-dev-image-1.0-r0 do_rootfs: Function failed: >>>>> do_rootfs >>>>> ERROR: Logfile of failure stored in: >>>>> /home/sno/gpw-community-bsp/mops-yocto-platform/tmp/work/fischer-poky-linux/updatable-app-dev-image/1.0-r0/temp/log.do_rootfs.14358 >>>>> ERROR: Task >>>>> (/home/sno/gpw-community-bsp/sources/meta-jens/recipes-images/images/updatable-app-dev-image.bb:do_rootfs) >>>>> failed with exit code '1' >>>>> >>>>> I can reproduce it using core-image-minimal-dev >>>>> >>>>> WARNING: core-image-minimal-dev-1.0-r0 do_rootfs: coreutils.postinst >>>>> returned 1, marking as unpacked only, configuration required on target. >>>>> ERROR: core-image-minimal-dev-1.0-r0 do_rootfs: Postinstall scriptlets of >>>>> ['coreutils'] have failed. If the intention is to defer them to first >>>>> boot, >>>>> then please place them into pkg_postinst_ontarget_${PN} (). >>>>> Deferring to first boot via 'exit 1' is no longer supported. >>>>> Details of the failure are in >>>>> /home/sno/gpw-community-bsp/mops-yocto-platform/tmp/work/fischer-poky-linux/core-image-minimal-dev/1.0-r0/temp/log.do_rootfs. >>>>> ERROR: core-image-minimal-dev-1.0-r0 do_rootfs: Function failed: do_rootfs >>>>> ERROR: Logfile of failure stored in: >>>>> /home/sno/gpw-community-bsp/mops-yocto-platform/tmp/work/fischer-poky-linux/core-image-minimal-dev/1.0-r0/temp/log.do_rootfs.27709 >>>>> ERROR: Task >>>>> (/home/sno/gpw-community-bsp/sources/poky/meta/recipes-core/images/core-image-minimal-dev.bb:do_rootfs) >>>>> failed with exit code '1' >>>>> >>>>> Any idea where to start debugging? >>>>> >>>>> Best regards >>>>> -- >>>>> Jens Rehsack - rehs...@gmail.com <mailto:rehs...@gmail.com> >>>>> >>>>> >>>>> -- >>>>> _______________________________________________ >>>>> yocto mailing list >>>>> yocto@yoctoproject.org <mailto:yocto@yoctoproject.org> >>>>> https://lists.yoctoproject.org/listinfo/yocto >>>>> <https://lists.yoctoproject.org/listinfo/yocto> >>>>> >>> >>> -- >>> Jens Rehsack - rehs...@gmail.com <mailto:rehs...@gmail.com> >>> -- >>> _______________________________________________ >>> yocto mailing list >>> yocto@yoctoproject.org <mailto:yocto@yoctoproject.org> >>> https://lists.yoctoproject.org/listinfo/yocto >>> <https://lists.yoctoproject.org/listinfo/yocto> >> >> -- >> Jens Rehsack - rehs...@gmail.com <mailto:rehs...@gmail.com> > > -- > Jens Rehsack - rehs...@gmail.com <mailto:rehs...@gmail.com> -- Jens Rehsack - rehs...@gmail.com
signature.asc
Description: Message signed with OpenPGP
-- _______________________________________________ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
