Re: Wrong as/ld picked by gcc configure

[Loren James Rittle <rittle at latour dot rsch dot comm dot mot dot com>]

> I believe the logic behind the gcc configure is flawed. Should it use
> the same approach as the gcc driver? If the gcc driver uses $PATH, why
> does the gcc configure do it differently? It doesn't make any senses
> to me.

Hi H.J.,

The Fine Manual in gcc/doc/install.texi is extremely clear on what
happens when you do not tell configure exactly which as/ld to use.  It
explicitly says that it doesn't search $PATH (nor does the gcc driver
to my knowledge unless you go well out of your way to force it to do
so).  It explicitly says where it will search.  It explicitly says what
you should do if you don't like the default rules for a given system.

>>> What is the best way to fix it?

Modify your expectations after RTFM. ;-)

All that said, I too always give explicit --with-as\=/absolute/path/as
and --with-ld\=/absolute/path/ld configure-time options (OK, a tad
different than what Daniel does; in typical gcc fashion for good or
bad, there are multiple ways to subtly affect the build process).
Anyone that wishes absolute repeatable control over the situation
would consider doing likewise.

Regards,
Loren