diff options
| author | Richard Purdie <rpurdie@linux.intel.com> | 2010-05-06 10:25:59 +0100 |
|---|---|---|
| committer | Richard Purdie <rpurdie@linux.intel.com> | 2010-05-06 10:29:14 +0100 |
| commit | 37858f5fac7491484ce48e6f74995bb45fe80090 (patch) | |
| tree | 7f0d738b0343bf41f8620c925b3859359ad7e18c | |
| parent | d37f26525bbf5251a9d746bb9694f87c259a1903 (diff) | |
| download | openembedded-core-37858f5fac7491484ce48e6f74995bb45fe80090.tar.gz openembedded-core-37858f5fac7491484ce48e6f74995bb45fe80090.tar.bz2 openembedded-core-37858f5fac7491484ce48e6f74995bb45fe80090.tar.xz openembedded-core-37858f5fac7491484ce48e6f74995bb45fe80090.zip | |
handbook: Add new FAQs
Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
| -rw-r--r-- | handbook/faq.xml | 36 |
1 files changed, 36 insertions, 0 deletions
diff --git a/handbook/faq.xml b/handbook/faq.xml index 6e105d189..150ed58dd 100644 --- a/handbook/faq.xml +++ b/handbook/faq.xml @@ -270,6 +270,42 @@ </para> </answer> </qandaentry> + <qandaentry> + <question> + <para> + Whats the difference between foo and foo-native? + </para> + </question> + <answer> + <para> + The *-native targets are designed to run on the system the buil is running on. These are usually tools that are needed to assist the build in some way such as quilt-native which is used to apply patches. The non-native version is the one that would run on the target device. + </para> + </answer> + </qandaentry> + <qandaentry> + <question> + <para> + I'm seeing random build failures. Help?! + </para> + </question> + <answer> + <para> + If the same build is failing in totally different and random ways the most likely explaination is that either the hardware you're running it on has some problem or if you are running it under virtualisation, the virtualisation probably has bugs. Poky processes a massive amount of data causing lots of network, disk and cpu activity and is senstive to even single bit failure in any of these areas. Totally random failures have always been traced back to hardware or virtualisation issues. + </para> + </answer> + </qandaentry> + <qandaentry> + <question> + <para> + What do we need to ship for licence complience? + </para> + </question> + <answer> + <para> + This is a difficult question and you need to consult your lawyer for the answer for your specific case. Its worth bearing in mind that for GPL complience there needs to be enough information shipped to allow someone else to rebuild the same end result as you are shipping. This means sharing the source code, any patches applied to it but also any configuration information about how that package was configured and built. + </para> + </answer> + </qandaentry> </qandaset> </appendix> <!-- |