Skip to contentSkip to conversation

lib32-glibc headers populated instead glibc headers in the SDK toolchain - yocto 2.2.2

DISCUSSION ravi chandran 1 participant 1 message Nov 13, 2018 1 message not in the archive

lore
Share & tools
lore

A message that is not in the archive (sent off-list or not yet received): [email protected]

#1 lore raw

Hi all,
I am working in one project where both lib32 & lib64 need to be supported. Hence, lib32-glibc & glibc both are there in yocto build. In the final toolchain, after running "bitbake <image> -c populate-sdk", it is randomly, lib32-glibc headers are getting populated instead of glibc headers.
Ex: in the toolchain, <sysroots_dir>/aarch64/usr/include/bits/endian.h - lib32-glibc header file content seen instead glibc header file content.
Please let me know if anybody has any solution/work-around for this.
Thanks in advance,Ravi