summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorScott Rifenbark <scott.m.rifenbark@intel.com>2015-02-04 09:02:20 -0800
committerRichard Purdie <richard.purdie@linuxfoundation.org>2015-02-17 15:16:59 +0000
commitef959e61c48539837b3f501126df969ec22f4f78 (patch)
treebd65de33222878374cc704e5bffafe56bd0d1080
parenta0999ab4dff3e0f37d071a9066f53cd01713c349 (diff)
downloadpoky-ef959e61c48539837b3f501126df969ec22f4f78.tar.gz
ref-manual: Added "leakage" FAQ entry.
Fixes [YOCTO #6852] I added a new FAQ entry to address situations where during a native build, the build fails due to previously installed stuff on the system from /usr/local/include and /opt. The entry tries to cover "leakage" issues in general but calls out the specific case involving libiconv and iconv.h. (From yocto-docs rev: 2c09c7ee0970189953bfbbdcaac49a1ebe8482fe) Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
-rw-r--r--documentation/ref-manual/faq.xml35
1 files changed, 35 insertions, 0 deletions
diff --git a/documentation/ref-manual/faq.xml b/documentation/ref-manual/faq.xml
index da6ce20eef..c53d458029 100644
--- a/documentation/ref-manual/faq.xml
+++ b/documentation/ref-manual/faq.xml
@@ -364,6 +364,41 @@
364 <qandaentry> 364 <qandaentry>
365 <question> 365 <question>
366 <para> 366 <para>
367 When I try to build a native recipe, the build fails with <filename>iconv.h</filename> problems.
368 </para>
369 </question>
370 <answer>
371 <para>
372 If you get an error message that indicates GNU
373 <filename>libiconv</filename> is not in use but
374 <filename>iconv.h</filename> has been included from
375 <filename>libiconv</filename>, you need to check to see if
376 you have a previously installed version of the header file
377 in <filename>/usr/local/include</filename>.
378 <literallayout class='monospaced'>
379 #error GNU libiconv not in use but included iconv.h is from libiconv
380 </literallayout>
381 If you find a previously installed file, you should either
382 uninstall it or temporarily rename it and try the build again.
383 </para>
384
385 <para>
386 This issue is just a single manifestation of "system
387 leakage" issues caused when the OpenEbedded build system
388 finds and uses previously installed files during a native
389 build.
390 This type of issue might not be limited to
391 <filename>iconv.h</filename>.
392 Be sure that leakage cannot occur from
393 <filename>/usr/local/include</filename> and
394 <filename>/opt</filename> locations.
395 </para>
396 </answer>
397 </qandaentry>
398
399 <qandaentry>
400 <question>
401 <para>
367 What do we need to ship for license compliance? 402 What do we need to ship for license compliance?
368 </para> 403 </para>
369 </question> 404 </question>