>>>>> "Mo" == Mo DeJong <[EMAIL PROTECTED]> writes:

Mo> Beats me, looks like a bug in the compiler. It really should check
Mo> to see if there is a .exe extension on the -o argument and add one
Mo> if not found. But, since there is no way to rely on this being
Mo> fixed in autoconf, me thinks we need to check for the a.out or
Mo> a.exe. Is there going to be a problem with compilers other than
Mo> gcc? Do they also use a.out or a.exe as the default output name?

I plan to have the two tests: the a.exe one (in a conftestdir as was
to be suggested by Alexandre), and the -o conftest$ac_exeext one.

As for the other cross compilers, let them receive our signal: we are
setting a standard they have to follow :)

Reply via email to