Peter Eisentraut <[EMAIL PROTECTED]> writes:

> [...] I mean if you do cc conftest.c -o conftest, and afterwards
> there is no file "conftest", but there is a file "conftest.exe" that
> wasn't there before, that should be pretty conclusive, no?

Not really, no. For instance, Cygwin does this funny thing where they
map all files named ``something.exe'' to also match any inquires to a
file named ``something''.

So you could do:

  $ cat > conftest.c
  int main(void) { return 0; }
  ^D
  $ gcc -o conftest.exe conftest.c
  $ ls
  conftest.exe conftest.c
  $ ls conftest
  conftest
  $

And further:

  $ rm conftest.exe
  $ ls conftest*
  conftest.c
  $ gcc -o conftest conftest.c
  $ ls
  conftest.exe conftest.c
  $

(So, in the Cygwin case it doesn't really matter whether you set the
executable suffix to ".exe" or "", I guess.)

Regards,
Morten

Reply via email to