typo refusing = reusing.

-----Original Message-----
From: David Nyström [david.nyst...@enea.com]
Received: Friday, 06 Jul 2012, 12:49
To: yocto@yoctoproject.org [yocto@yoctoproject.org]; raj.k...@gmail.com 
[raj.k...@gmail.com]
Subject: Re: [yocto] [meta-fsl-ppc][PATCH 2/2] fsl.conf:        Let     
linux-qoriq-sdk-headers-nativesdk       provide linux-libc-headers-nativesdk



So that about a disto refusing this and possibly other BSP layers ?
Should the disto.conf  select of nativesdk be made machine specific on all 
machines in meta-fsl-ppc ? And one added target after a meta-fsl-ppc rebase 
would break stuff, I guess.


Br
David

Sent from Android


-----Original Message-----
From: Khem Raj [raj.k...@gmail.com]
Received: Friday, 06 Jul 2012, 6:52
To: yocto@yoctoproject.org [yocto@yoctoproject.org]
Subject: [yocto] [meta-fsl-ppc][PATCH 2/2] fsl.conf: Let        
linux-qoriq-sdk-headers-nativesdk provide       linux-libc-headers-nativesdk



If not set by user then let distro policy be to use
linux-qoriq-sdk-headers-nativesdk for linux-libc-headers-nativesdk

Signed-off-by: Khem Raj <raj.k...@gmail.com>
---
 conf/distro/fsl.conf |    1 +
 1 file changed, 1 insertion(+)

diff --git a/conf/distro/fsl.conf b/conf/distro/fsl.conf
index 6d4dc34..8bfb272 100644
--- a/conf/distro/fsl.conf
+++ b/conf/distro/fsl.conf
@@ -83,6 +83,7 @@ IMAGE_CLASSES = "image_types_uboot"

 PREFERRED_VERSION_u-boot-mkimage-native_powerpc = "2011.06"
 PREFERRED_PROVIDER_virtual/libx11 = "libx11"
+PREFERRED_PROVIDER_linux-libc-headers-nativesdk ?= 
"linux-qoriq-sdk-headers-nativesdk"

 SYSVINIT_ENABLED_GETTYS = ""
 USE_VT = ""
--
1.7.9.5

_______________________________________________
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
_______________________________________________
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
_______________________________________________
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Reply via email to