> IMHO, you should *never* update gcc's configure to force the issue. To do > so would be unprecedented.
I'm not in favor of this either, but aren't there precedents with either automake, autoconf, or both?
> IMHO, you should *never* update gcc's configure to force the issue. To do > so would be unprecedented.
I'm not in favor of this either, but aren't there precedents with either automake, autoconf, or both?