summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
-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>