Created attachment 411862 [details] Build log [..] -- One (and only one) of the ICONV_ACCEPTS_... tests must pass -- Performing Test ICONV_ACCEPTS_NONCONST_INPUT -- Performing Test ICONV_ACCEPTS_NONCONST_INPUT - Success -- Performing Test ICONV_ACCEPTS_CONST_INPUT -- Performing Test ICONV_ACCEPTS_CONST_INPUT - Success CMake Error at cmake/FindIconv.cmake:123 (MESSAGE): Unable to determine iconv() signature - both test cases passed! Call Stack (most recent call first): CMakeLists.txt:64 (find_package) [..]
Through debugging I found that: leftover -fpermissive in CXXFLAGS is causing configure to fail. CMake is trying to compile #include <iconv.h> int main() { char const *p = 0; iconv(iconv_t(-1), &p, 0, 0, 0); } and expects it to fail with an error. With -fpermissive it passes (with a warning) which is where the "both test cases passed!" error is originating from. Fixes could be: * Filtering -fpermissive * Asking upstream to remove the test (as the results do not seem to be used for real) and there are other tests covering iconv, see ICONV_COMPILES. * Ignoring as a rare case What do you think?
i can't see any reason you'd ever want to put -fpermissive into CXXFLAGS. i'd just reject such configurations as invalid and pointless.
I fail to see the purpose of special (per package) support for -fpermissive too. I suggest that you disable -fpermissive for app-doc/doxygen via package.env.
*** Bug 566108 has been marked as a duplicate of this bug. ***
