https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93602
--- Comment #12 from Liviu Ionescu <ilg at livius dot net> ---
--without-libiconv-prefix did not prevent configure to pick the new libiconv,
the behaviour was exactlly the same.
The only way I could make it pass was to completely remove the new libiconv.
Although I can live with this, since I fully control my environment, I think
that this is a tough workaround.
Probably a proper solution would be a configure option like:
--with-libiconv={no,gnu,native}