https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93602
--- Comment #8 from Liviu Ionescu <ilg at livius dot net> ---
> I would guess either /usr/local/include or ${INSTALL_FOLDER_PATH}/include
Yes, but I have exactly the same configuration when I build GCC 8.x and 7.x,
and GCC does not get confused, the problem occurred only when I tried to use
9.x.
Is there any way to prevent GCC from picking the freshly compiled libiconv and
use the system one? (I'm not even sure there is a system one).
