Why was the name 'i586-mingw32msvc' choosen? To me this implies that this build was compiled with Microsoft Visual C Compiler. I'm very much assuming it was not.
The (official?) mingw cross-compiler build scripts by Keith Marshall use 'i386-mingw32' and this is statically defined in the build scripts. The README states that the resulting cross compiler should be invoked as 'i386-mingw32-gcc', but it does also create a directory full of binary stubs for gcc, ld, ar, etc. as this original bug report suggests doing. I do a bit of cross compiling using mingw and I find it quite annoying at the scattered naming conventions that different distros use. As a comprimise, why not just create symbolic links with some more standard names? For example: mingw32-gcc would be a symlink to i586-mingw32msvc-gcc or whatever wonky prefix of choice is. -Tony -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
