From ef959e61c48539837b3f501126df969ec22f4f78 Mon Sep 17 00:00:00 2001 From: Scott Rifenbark Date: Wed, 4 Feb 2015 09:02:20 -0800 Subject: [PATCH] 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 Signed-off-by: Richard Purdie --- documentation/ref-manual/faq.xml | 35 ++++++++++++++++++++++++++++++++ 1 file changed, 35 insertions(+) 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 @@ -361,6 +361,41 @@ + + + + When I try to build a native recipe, the build fails with iconv.h problems. + + + + + If you get an error message that indicates GNU + libiconv is not in use but + iconv.h has been included from + libiconv, you need to check to see if + you have a previously installed version of the header file + in /usr/local/include. + + #error GNU libiconv not in use but included iconv.h is from libiconv + + If you find a previously installed file, you should either + uninstall it or temporarily rename it and try the build again. + + + + This issue is just a single manifestation of "system + leakage" issues caused when the OpenEbedded build system + finds and uses previously installed files during a native + build. + This type of issue might not be limited to + iconv.h. + Be sure that leakage cannot occur from + /usr/local/include and + /opt locations. + + + +