Hello,
For the multilib package like lib32-bash, its rpm package name is bash-4.3.30-r0.lib32_x86.rpm, but for ipk and deb, its name is lib32-bash.ipk and lib32-bash.deb, there is a side effect for the naming of rpm, for example, if packagegroup-xx rdepends on bash, the lib32-packagegroup-xx should rdepend on lib32-bash, but the its rpm pkg knows nothing about lib32-bash, so it still rdepends on bash, this causes 32bit toolchain libs not installed when export multilib sdk, for example: Configured multilib: MACHINE ?= "qemux86-64" require conf/multilib.conf MULTILIBS = "multilib:lib32" DEFAULTTUNE_virtclass-multilib-lib32 = "x86" $ bitbake core-image-minimal -cpopulate_sdk When PACKAGE_CLASSES = "package_rpm", the lib32-libgcc, lib32-libgcc-dev or other lib32-xx packages are not installed, so that the 32bit toolchain doesn't work in SDK, this is because lib32-packagegroup-core-standalone-sdk-target can't pull in the lib32-xx correctly. When PACKAGE_CLASSES = "package_ipk", it works well. Does anyone why we don't use the name like lib32-bash.rpm, please ? Can we use lib32-bash, please ? -- Thanks Robert -- _______________________________________________ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
