Poky Project Discussions
 help / color / mirror / Atom feed
* sysroot question
@ 2011-01-17 19:46 Zhang, Jessica
  2011-01-17 20:01 ` Mark Hatle
  0 siblings, 1 reply; 2+ messages in thread
From: Zhang, Jessica @ 2011-01-17 19:46 UTC (permalink / raw)
  To: Purdie, Richard; +Cc: poky@yoctoproject.org


[-- Attachment #1.1: Type: text/plain, Size: 1074 bytes --]

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@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@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?
 
Thanks,
Jessica

[-- Attachment #1.2: Type: text/html, Size: 2567 bytes --]

[-- Attachment #2: smime.p7s --]
[-- Type: application/x-pkcs7-signature, Size: 8455 bytes --]

^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: sysroot question
  2011-01-17 19:46 sysroot question Zhang, Jessica
@ 2011-01-17 20:01 ` Mark Hatle
  0 siblings, 0 replies; 2+ messages in thread
From: Mark Hatle @ 2011-01-17 20:01 UTC (permalink / raw)
  To: poky

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@jzhang-desktop:/opt/poky/0.9+snapshot$
> <mailto:jzhang@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@jzhang-desktop:~/qemu-x86$ <mailto:jzhang@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@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/poky



^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2011-01-17 20:01 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2011-01-17 19:46 sysroot question Zhang, Jessica
2011-01-17 20:01 ` Mark Hatle

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox