You run with

PATH=.:$PATH

?

That's

1. Asking for security problems galore. If you honestly beleive having .
   anywhere in your path is somehow not a security problem.....
2. Impossible for the build stuff to accurately deal with. 

I guess just adding a note to BUILDING which states that we presume a sane
path with all the system dirs are before any uses of . and that . in the path
is never recommended anyways.

JAmes


>>> 2) compiling with '.' or '::' in your path will cause the host tools
>>>    (toolchain) to fail, since the host gcc invokes the cross-gas in
>>>    the object directory as the host assembler.
>
>> Only if it's at the front of your path or before your system dirs
>> (ala /usr/bin, /bin, etc).  That's gonna break much much more than
>> just your toolchain build long run.
>
>Like what?  I have a machine or two on which I run that way routinely,
>and haven't noticed any particular breakage.  (To be sure, I reset my
>path before doing any in-tree builds, but when I forget it usually runs
>fine until it trips over <md5.h>, which is to be expected.)
>
>/~\ The ASCII				der Mouse
>\ / Ribbon Campaign
> X  Against HTML	       mouse@rodents.montreal.qc.ca
>/ \ Email!	     7D C8 61 52 5D E7 2D 39  4E F1 31 3E E8 B3 27 4B
>
>
>
>