On Tue, 22 Nov 2016 10:44:48 Michel D'HOOGE wrote: > > From: "Paul Eggleton" <paul.eggle...@linux.intel.com> > > Sent: Monday, 21 November, 2016 10:15:16 PM > > > > I suspect it has to do with the arch mapping that goes on in > > meta/classes/package_deb.bbclass; it probably doesn't understand the > > dummy architecture we're giving it. The thing is even if it were to be > > "corrected" to fall back to "all" instead of "allarch" that probably still > > wouldn't work properly because the architecture of the perl packages would > > be a higher priority than "all" and thus the dummy package wouldn't take > > precedence. > > It seems to be OK. > The only other package with 'perl' in its name is 'nativesdk-git-perltools'.
OK, so it may only be working by chance then - if you did have the nativesdk- perl package built then I suspect you'd find it would get installed. I'm puzzled as to why it hasn't been built though, since it is a dependency of some of the other items we do include in buildtools (notably git) and does get built when you use rpm as the backend, last I checked anyway. > But I have (another) problem with the manifest files: > - all "target" manifest files are empty > - the 'poky-systemd-blah-blah-toolchain-ext-2.2.host.manifest' has a single > entry: meta-environment-extsdk-vtc7200 > So maybe I don't see everything... That's expected for the extensible SDK - it isn't built with the same kinds of packages that the standard SDK is built with. > > In any case feel free to file a bug under "OE-Core -> Core" in > > bugzilla, that> would be a reasonable category for this issue. > > Done: https://bugzilla.yoctoproject.org/show_bug.cgi?id=10700 Thanks. Cheers, Paul -- Paul Eggleton Intel Open Source Technology Centre -- _______________________________________________ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto