prefer in-tree as and ld over pre-installed ones

[Alexandre Oliva]

If you happen to have a pre-installed assembler or linker in the
compiler search path, or if top-level configure happens to find an
assembler or linker for the host (if cross building) or a linker for
the target (we missed the assembler for the target), gcc would use
that for the configure tests, even when it knows we're building an
assembler and/or a linker alongside itself, that it's going to use at
run time.  That's bad.

I fixed the most visible part of this problem some time ago, but only
now did I finally get the logic in such a way that I think it actually
makes sense.  So I'm checking this in.

It works fine for natives, crosses and Canadians, with the expected
semantics, and gets the compiler to prefer what's in the build tree
regardless of what the top-level might have found already installed at
the time it ran.

I'm checking this in.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: gcc-use-in-tree-ld-as.patch
Type: text/x-patch
Size: 3013 bytes
Desc: not available
URL: <http://gcc.gnu.org/pipermail/gcc-patches/attachments/20040525/d1f5ac4d/attachment.bin>
-------------- next part --------------

-- 
Alexandre Oliva             http://www.ic.unicamp.br/~oliva/
Red Hat Compiler Engineer   aoliva@{redhat.com, gcc.gnu.org}
Free Software Evangelist  oliva@{lsd.ic.unicamp.br, gnu.org}