gcc produces foo.exe, not foo

Ben Elliston bje@cygnus.com
Wed Sep 23 07:15:00 GMT 1998

> What is the standard way of circumventing this problem? Simply writing
>           mv foo.exe bar.exe
> is not a full solution, because that is not portable. Is it necessary to
> write some autoconf stuff to check what the extension of the executable
> resulting from calling gcc is?

Yes, that's right.  The next version of autoconf will have a new macro
called `AC_EXEEXT' which will probe your system and make a subsitution
variable available for your Makefile.in called @EXEEXT@.  It typically has
the value "" or ".exe".


For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request@cygnus.com" with one line of text: "help".

More information about the Cygwin mailing list