> On Oct 11, 2016, at 4:53 PM, Stroz, Glenn wrote:
>
> 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 wh
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@yoctoproject.org'
Subject: Conflict be
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 f