[poky] sysroot question

[Mark Hatle]

On 1/17/11 1:46 PM, Zhang, Jessica wrote:
> Hi Richard,
>  
> While testing the sysroot setup, I noticed there're some variation between the
> sysroot that built by meta-toolchain and qemu-image-sdk.  For example, limits.h,
> if I search for it under the meta-toolchain sysroot, I got the following:
>  
> jzhang at jzhang-desktop:/opt/poky/0.9+snapshot$
> <mailto:jzhang at jzhang-desktop:/opt/poky/0.9+snapshot$> find . -name limits.h
> ./sysroots/i586-poky-linux/usr/include/limits.h
> ./sysroots/i586-poky-linux/usr/include/linux/limits.h
> ./sysroots/i586-poky-linux/usr/include/c++/tr1/limits.h
> ./sysroots/i686-pokysdk-linux/usr/lib/i586-poky-linux/gcc/i586-poky-linux/4.5.1/include-fixed/limits.h
> ./sysroots/i686-pokysdk-linux/usr/include/limits.h
>  
> and the sysroot extract from qemu-image-sdk, gave me this:
>  
> jzhang at jzhang-desktop:~/qemu-x86$ <mailto:jzhang at jzhang-desktop:~/qemu-x86$>
> find . -name limits.h
> ./usr/lib/gcc/i586-poky-linux/4.5.1/include-fixed/limits.h
> ./usr/include/c++/tr1/limits.h
> ./usr/include/limits.h
> This caused problem in test programs of suduku which looking for
> <linux/limits.h>.  The question is where should I look that cause the sysroot
> content variation?

It is almost always a bug in an application to include <linux/*>.  The ONLY
valid exceptions are when they need an ioctl, syscall or similar definition that
is not available via the standard set of includes.

I highly doubt suduku fits this, so it's a bug in the test program.

(but yes, I also suspect that /usr/include/linux/... will be needed in the SDK,
so thats ALSO likely a defect..)

--Mark

> Thanks,
> Jessica
> 
> 
> 
> _______________________________________________
> poky mailing list
> poky at yoctoproject.org
> https://lists.yoctoproject.org/listinfo/poky