Hi, I tried building toolchain using target for bitbake as meta-toochain with the configuration mention below:- Adding below configuration in the local.conf MACHINE = "qemux86-64" require conf/multilib.conf MULTILIBS = "multilib:lib32" DEFAULTTUNE_virtclass-multilib-lib32 = "x86" And as per my understanding multilib means it should create multiple library files supporting each variant(like fpu, big endian, 64-bit etc). But the above changes did not create multiple library files. While extarcting the toolchain it only create one libgcc.a at location $SDKTARGETSYSROOT/usr/lib/arm-poky-linux-gnueabi/4.9.0/libgcc.a Please help me with your valuable suggestion. Thanks and regards, Atul
See: http://lists.openembedded.org/pipermail/openembedded-core/2014-July/094877.html This patch has been provided by the community to attempt to resolve some of the issues. Note, the patch does not work when 'package_rpm' is selected. This is due to some limitations in the way the RPM package resolution occurs. When using IPK, the patch will select multiple packagegroup files instead of just the main system. A second patch is still needed for the packagegroups to be ARCH specific in their dependencies.
http://git.yoctoproject.org/cgit.cgi/poky/commit/?id=d8024434d4c9b6a3400ac494fa3c32d0827e42d3 has now merged and that ensures that meta-toolchain/populate_sdk have the appropriate multilib pieces. This *does* work with package_ipk, contra to what Mark mentions, no second patch is needed. There is an rpm issue remaining and it does not work with the package_rpm backend. Reassigning to Mark to find someone to resolve the remaining rpm piece.
Fixed in YP 2.0: http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?h=jethro&id=eb7b1a58ceaab7fde4dc954eb4df4247d6c7c6d8