cross building ncurses with USE unicode generates alot of cc1: warning: include location "/usr/include/ncursesw" is unsafe for cross-compilation [-Wpoison-system-directories] This is because unicode enforces: use unicode && do_configure widec --enable-widec --includedir="${EPREFIX}"/usr/include/ncursesw and ncurses configure adds any non standard includedir till CPPFLAGS. This seems very wrong and adding a #Remove ${includedir} from CPPFLAGS, need for cross compile sed -i 's/-I\\${includedir}//g' configure || die "sed CPPFLAGS" to src_prepare removes the complaint and ncurses still builds Reproducible: Always
Upstream just removed -I\\${includedir} from CPPFLAGS too: http://ncurses.scripts.mit.edu/?p=ncurses.git;a=commitdiff;h=9ee3995474454b7d956885e0fe5c8cac2ae25d42
Thanks for reporting this upstream. It didn't break anything for me but the warning is always unsettling as it often does lead to breakages in other packages. I guess you can close this now.
(In reply to James Le Cuirot from comment #2) > Thanks for reporting this upstream. It didn't break anything for me but the > warning is always unsettling as it often does lead to breakages in other > packages. I guess you can close this now. Cant close because it isn't fixed in Gentoo and upstream won't relase anything soon. He "releasing" patch sets every week but no real release until he is "done". Done appears to be quite a long time ahead. He thinks dists should just pick his patch sets meanwhile which I don't think Gentoo does(does any dist?). Until this happens, the little fix I listed here should be applied. Also, he thinks keeping unicode is /usr/include/nursesw is a bad idea.
ping @base
Mike, I see you are fixing python cross compile w.r.t ncursesw. Perhaps you can address nucurses too?
Commit message: Fix from upstream for building with -I/usr/include/ncursesw http://sources.gentoo.org/sys-libs/ncurses/files/ncurses-5.9-no-I-usr-include.patch?rev=1.1 http://sources.gentoo.org/sys-libs/ncurses/ncurses-5.9-r4.ebuild?rev=1.1
