[yocto] morty populate_sdk_ext fails for recipes inherit bin_package
richard_allen at keysight.com
richard_allen at keysight.com
Thu Jan 5 12:12:13 PST 2017
Appreciate your suggestions.
The ipk's are there
$ find tmp/deploy/ipk/ -name hals*
tmp/deploy/ipk/cortexa9hf-neon/hals-tests_5.0.0-r0_cortexa9hf-neon.ipk
tmp/deploy/ipk/cortexa9hf-neon/hals_5.0.0-r0_cortexa9hf-neon.ipk
tmp/deploy/ipk/cortexa9hf-neon/hals-dev_5.0.0-r0_cortexa9hf-neon.ipk
tmp/deploy/ipk/cortexa9hf-neon/hals-doc_5.0.0-r0_cortexa9hf-neon.ipk
tmp/deploy/ipk/cortexa9hf-neon/hals-dbg_5.0.0-r0_cortexa9hf-neon.ipk
But error persist (no issues with -c populate_sdk)..
$ bitbake core-image-minimal -R cfgs/add-hals.conf -c populate_sdk_ext
NOTE: Executing RunQueue Tasks
ERROR: uninative-tarball-1.0-r0 do_populate_sdk: Unable to install packages. Command '/home/rcallen/proto/morty/tmp/sysroots/x86_64-linux/usr/bin/opkg --volatile-cache -f /home/rcallen/proto/morty/tmp/work/x86_64-nativesdk-keysight-linux/uninative-tarball/1.0-r0/opkg.conf -t /home/rcallen/proto/morty/tmp/work/x86_64-nativesdk-keysight-linux/uninative-tarball/1.0-r0/temp/ipktemp/ -o /home/rcallen/proto/morty/tmp/work/x86_64-nativesdk-keysight-linux/uninative-tarball/1.0-r0/sdk/image/opt/tlo/2.2/sysroots/none --force_postinstall --prefer-arch-to-version install hals-doc hals' returned 255:
Collected errors:
* opkg_prepare_url_for_install: Couldn't find anything to satisfy 'hals-doc'.
* rm_r: Failed to open dir /home/rcallen/proto/morty/tmp/work/x86_64-nativesdk-keysight-linux/uninative-tarball/1.0-r0/temp/ipktemp//opkg-HSRjMc: No such file or directory.
ERROR: uninative-tarball-1.0-r0 do_populate_sdk: Function failed: do_populate_sdk
ERROR: Logfile of failure stored in: /home/rcallen/proto/morty/tmp/work/x86_64-nativesdk-keysight-linux/uninative-tarball/1.0-r0/temp/log.do_populate_sdk.39088
ERROR: Task (/opt/yocto/morty/poky/meta/recipes-core/meta/uninative-tarball.bb:do_populate_sdk) failed with exit code '1'
ERROR: buildtools-tarball-1.0-r0 do_populate_sdk: Unable to install packages. Command '/home/rcallen/proto/morty/tmp/sysroots/x86_64-linux/usr/bin/opkg --volatile-cache -f /home/rcallen/proto/morty/tmp/work/x86_64-nativesdk-keysight-linux/buildtools-tarball/1.0-r0/opkg.conf -t /home/rcallen/proto/morty/tmp/work/x86_64-nativesdk-keysight-linux/buildtools-tarball/1.0-r0/temp/ipktemp/ -o /home/rcallen/proto/morty/tmp/work/x86_64-nativesdk-keysight-linux/buildtools-tarball/1.0-r0/sdk/image/opt/tlo/2.2/sysroots/none --force_postinstall --prefer-arch-to-version install hals-doc hals' returned 255:
Collected errors:
* opkg_prepare_url_for_install: Couldn't find anything to satisfy 'hals-doc'.
* rm_r: Failed to open dir /home/rcallen/proto/morty/tmp/work/x86_64-nativesdk-keysight-linux/buildtools-tarball/1.0-r0/temp/ipktemp//opkg-eTg08o: No such file or directory.
ERROR: buildtools-tarball-1.0-r0 do_populate_sdk: Function failed: do_populate_sdk
ERROR: Logfile of failure stored in: /home/rcallen/proto/morty/tmp/work/x86_64-nativesdk-keysight-linux/buildtools-tarball/1.0-r0/temp/log.do_populate_sdk.39087
ERROR: Task (/opt/yocto/morty/poky/meta/recipes-core/meta/buildtools-tarball.bb:do_populate_sdk) failed with exit code '1'
-----Original Message-----
From: Stephano Cetola [mailto:stephano.cetola at linux.intel.com]
Sent: Thursday, January 05, 2017 10:58 AM
To: ALLEN,RICHARD (K-SantaClara,ex1) <richard_allen at keysight.com>
Cc: yocto at yoctoproject.org
Subject: Re: [yocto] morty populate_sdk_ext fails for recipes inherit bin_package
On 01/05, richard_allen at keysight.com wrote:
> Hi
> 1) I had just successfully built an image with all the recipes ( hals,
> hals-doc) [and yes, there these are non-empty]
> 2) I had then successfully built image with -c populate_sdk
> 3) The bitbake image -c populate_sdk_ext is what is failing [ The
> above works with Krogoth, only on Morty am I getting the errors during
> populate_sdk_ext
>
> May be the recipe is wrong for Morty? ( I have several other recipes,
> same thing, same structure)
Nothing jumps out about that recipe. If you do a `find` in tmp/deploy/ipk for hals*, does anything show up? That's where opkg will be looking for the packages, so I assume it is not there.
>
> inherit bin_package
>
> SUMMARY = "HALs "
> DESCRIPTION = "HALs"
>
> LICENSE = "CLOSED"
> LIC_FILES_CHKSUM = ""
>
> # this can be overridden in local.conf HALS_TARBALL_URI ?=
> "file:///opt/packages/${PN}-${PV}-arm.tar.gz"
>
> SRC_URI = "${HALS_TARBALL_URI}"
>
> # the tar has a root directory , which has the files under
> HALS_TAR_ROOT_DIR_NAME ?= "${PN}-${PV}-arm"
>
> #make the source directory start in this directory S =
> "${WORKDIR}/${HALS_TAR_ROOT_DIR_NAME}"
>
> #runtime depends
> RDEPENDS_${PN} = " libgcc \
> libstdc++ \
> dtc \
> "
> DEPENDS_${PN} = " gtest"
>
> #bring in all to build toolchain
> DEPENDS_${PN}-dev += " ${PN}-doc ${PN}-tests ${PN}-samples"
>
> PACKAGES =+ "${PN}-tests ${PN}-samples "
>
> FILES_${PN}-staticdev += " ${libdir}/*/*.a"
> FILES_${PN}-dev += "${includedir} ""
> FILES_${PN}-samples += "${bindir}/*"
> FILES_${PN}-tests += "${bindir}/*[tT]est"
> FILES_${PN}-doc += "${prefix}/src/doc"
>
>
> # this stops an QA issue
>
> INSANE_SKIP_hals += "dev-so"
> BBCLASSEXTEND = "native nativesdk"
>
>
More information about the yocto
mailing list