summaryrefslogtreecommitdiffstats
path: root/meta/conf/machine
diff options
context:
space:
mode:
authorRichard Purdie <richard.purdie@linuxfoundation.org>2011-08-02 11:42:21 +0100
committerRichard Purdie <richard.purdie@linuxfoundation.org>2011-08-02 14:41:03 +0100
commite5d2249476fad3ebba648c6b7adf994cb630d1c6 (patch)
tree22e000e6564b6794a72b50c42962c3979d0165f6 /meta/conf/machine
parentbb5a3ff0b0331655b44f41d7ca3f8d13066fb083 (diff)
downloadpoky-e5d2249476fad3ebba648c6b7adf994cb630d1c6.tar.gz
eglibc: Add missing ${PN} and ${PKGSUFFIX} usages
This fixes warning messages such as: The providers found were: ['virtual:nativesdk:eglibc_2.13.bb', 'eglibc_2.13.bb'] The PREFERRED_PROVIDER entries resulting in this conflict were: ['PREFERRED_PROVIDER_virtual/libc-nativesdk = eglibc-nativesdk', 'PREFERRED_PROVIDER_virtual/libc = eglibc'] NOTE: multiple providers are available for runtime glibc-utils (eglibc, eglibc-nativesdk, external-csl-toolchain, external-poky-toolchain) NOTE: consider defining a PREFERRED_PROVIDER entry to match glibc-utils This highlights how ugly adding to PN is when using BBCLASSEXTEND. We need to do this to eglibc so the nativesdk class continues to work correctly for now and ensure consistency in how the various eglibc packages are generated. Longer term, if we switch nativesdk to use the multilib approach and MLPREFIX, we can remove all the PKGSUFFIX mess. I'd rather not get into changing nativesdk right at this time though given all the other changes that are going on. (From OE-Core rev: 3a18aa65a4c123ea922b6cd09ca6a77090f12252) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'meta/conf/machine')
0 files changed, 0 insertions, 0 deletions