[yocto] populate_sdk_ext: Unable to locate package nativesdk-buildtools-perl-dummy

Paul Eggleton paul.eggleton at linux.intel.com
Thu Nov 17 17:46:07 PST 2016

Hi Michel,

On Wed, 16 Nov 2016 11:48:21 Michel D'HOOGE wrote:
> I try to produce an extensible SDK for core-image-sato with the following
> configuration:
> BB_VERSION = "1.32.0"
> BUILD_SYS = "x86_64-linux"
> NATIVELSBSTRING = "universal"
> TARGET_SYS = "x86_64-poky-linux"
> MACHINE = "vtc7200"
> DISTRO = "poky-systemd"
> TUNE_FEATURES = "m64 corei7"
> The machine is based on an intel-corei7, with some features removed. And the
> distro is poky-based, with only systemd (as detailed in the ref manual).
> And I get the following error:
> ERROR : buildtools-tarball-1.0-r0 do_populate_sdk: Unable to install
> packages. Command '/mnt/Yocto/vedecom-x86/build/tmp/sysroots/x86_
> 64-linux/usr/bin/apt-get install --force-yes --allow-unauthenticated
> nativesdk-locale-base-en-us nativesdk-git nativesdk-make native
> sdk-ca-certificates nativesdk-tar nativesdk-python3-modules
> nativesdk-texinfo nativesdk-python3-git nativesdk-ncurses-terminfo-base n
> ativesdk-chrpath nativesdk-python3-misc nativesdk-git-perltools
> nativesdk-buildtools-perl-dummy nativesdk-pigz nativesdk-wget natives
> dk-python3-core' returned 100:
> Reading package lists...
> Building dependency tree...
> Reading state information...
> E: Unable to locate package nativesdk-buildtools-perl-dummy
> The package exists and is in:
> tmp/deploy/deb/buildtools-dummy-nativesdk/nativesdk-buildtools-perl-dummy_1.
> 0-r2_allarch.deb while the other listed packages are in
> tmp/deploy/deb/x86_64-nativesdk.
> It seems this package is empty, so maybe I should simply remove it from
> poky/meta/recipes-core/meta/buildtools-tarball.bb.

FYI the purpose of this package is to take precedence over the real nativesdk-
perl so that it doesn't get into the buildtools, since we prefer to avoid the 
issues associated with overriding the host perl there. If you remove this 
package then perl will enter buildtools and you will experience other issues.

I think the issue is this hasn't really been tested with deb packaging. You 
have hit a genuine bug though - would you mind filing a bug at 



Paul Eggleton
Intel Open Source Technology Centre

More information about the yocto mailing list