[yocto] Conflict between multilib glibc and non-multlib glibc

[Stroz, Glenn]

I wanted to add that it's specifically the glibc development packages which have this fpu_control.h file conflict.

IMAGE_INSTALL += "glibc-dev"
IMAGE_INSTALL += "lib32-glibc-dev"

-Glenn

From: Stroz, Glenn
Sent: Tuesday, October 11, 2016 4:54 PM
To: 'yocto at yoctoproject.org' <yocto at yoctoproject.org>
Subject: Conflict between multilib glibc and non-multlib glibc

Hi,

We have a project running an aarch64 compatible processor. For backward compatibility with some internal software packages, we're using the armv7a-vfp machine type as a multilib lib32 variant. However, we have found that when attempting to install both lib32-glibc and glibc we encounter a file conflict in the root image.

ERROR: Multilib check error: duplicate files /local/mnt/workspace2/gstroz/LE-UM-yocto2/poky/build/tmp-glibc/work/apq8096-oe-linux/machine-image/1.0-r0/multilib/lib32/usr/include/fpu_control.h /local/mnt/workspace2/gstroz/LE-UM-yocto2/poky/build/tmp-glibc/work/apq8096-oe-linux/machine- -image/1.0-r0/rootfs/usr/include/fpu_control.h is not the same

This is because the fpu_control.h file varies based on the machine architecture (in this case armv7-vfp and aarch64). Is this a known bug? If so, what is the suggested solution? We would like to keep both 32 and 64 bit libraries if possible.

-Glenn

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.yoctoproject.org/pipermail/yocto/attachments/20161012/1d365dc9/attachment.html>