From: Mark Hatle <mark.hatle@windriver.com>
To: poky@yoctoproject.org
Subject: Re: sysroot question
Date: Mon, 17 Jan 2011 14:01:51 -0600 [thread overview]
Message-ID: <4D34A02F.7080507@windriver.com> (raw)
In-Reply-To: <9AFCD584B0B67B48AE8D8585BE30BA9504E1482C@orsmsx504.amr.corp.intel.com>
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
next prev parent reply other threads:[~2011-01-17 20:01 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-17 19:46 sysroot question Zhang, Jessica
2011-01-17 20:01 ` Mark Hatle [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-02-08 10:42 Gary Thomas
2017-02-08 11:12 ` Gary Thomas
2017-02-08 13:57 ` Joshua Lock
2017-02-08 19:36 ` Paul Eggleton
2017-02-09 4:23 ` Gary Thomas
2017-02-09 7:49 ` Anders Darander
2017-02-09 8:04 ` Gary Thomas
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4D34A02F.7080507@windriver.com \
--to=mark.hatle@windriver.com \
--cc=poky@yoctoproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.