Re: gcc 3.3.4 cross build for mipsel mischooses the `as' to run

[James E Wilson <wilson at specifixinc dot com>]

On Thu, 2004-08-05 at 12:41, Zack Weinberg wrote:
>  5) $PATH at configure time.
>  6) MD_EXEC_PREFIX.

I wouldn't choose to use the $PATH at configure time, but I don't really
care.  If others think it should work that way, then I will just adapt. 
We would need some way for configure to feed that path name back into
the gcc driver, to make sure that this path is always used
consistently.  There would be a question of whether we are recording the
entire path, or just the one directory where we found as/ld.  The latter
could be a problem if as and ld are in different directories, but that
may be too unlikely to worry about.  We might have to modify the docs to
state that it is important that the path has to be set correctly before
you configure gcc.  If you have your path pointing to an temporary
binutils install tree, then gcc will fail after installation if that
temporary install tree is removed.

I already suggested moving MD_EXEC_PREFIX later in the search path. 
This fixes the immediate problem of having to specify --with-as= when
building on solaris.  I think moving it to the end is fine.  It should
only be used as a last resort, and it should only be used when the
native as/ld are in a directory that is not expected to be on the user's
path.

Otherwise, I think we already have most of what you are looking for.  It
is just a matter of someone double checking whether we are looking for
things in the right order, and fixing it if we aren't.
-- 
Jim Wilson, GNU Tools Support, http://www.SpecifixInc.com