Danny Smith wrote:
>> MinGW's release of GCC 3.4.5 contains a large amount of local
>> patching, some
>> of which I believe addresses issues like this of finding
>> tools relative to
>> the driver executables. If you add "-v" to the command line,
>> I expect you'll
>> see that the error message immediately follows a call to "as" (the
>> assembler). I imagine that as most of the local patches were
>> ported to the
>> mainline sources, this small part didn't quite survive intact.
> You assume too much. There were no local patches relating to this.
Oops, my mistake.
>> Looking at the output of `path-to-mingw\gcc.exe
>> -print-search-dirs`, it
>> should be fairly obvious what's happening. For the programs search
>> directories, there is no path corresponding to the root "bin"
>> which is where your binutils executables live. There is,
>> however, a path
>> corresponding to "path-to-mingw\mingw32\bin", which is an
>> alternate location
>> for the binutils tools.
> This is not the alternate locatiion. This is the first place the
> compuiler looks.
> That is where binitils package is supposed to install them.
That's good to know. Does this indicate a packaging bug in the binutils
2.18.50 tech preview, since they were built with a different target triplet
(i686-pc-mingw32)? If not, I think it should at least merit a warning to the
effect of "since this build uses a newer target triplet, you have to have
the bin directory in your PATH".
-John E. / TDM