autoconf
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: AC_CYGWIN etc. (Was: AC_OBJEXT again)


From: Mo DeJong
Subject: Re: AC_CYGWIN etc. (Was: AC_OBJEXT again)
Date: Thu, 14 Dec 2000 01:48:48 -0800 (PST)

On 14 Dec 2000, Akim Demaille wrote:

> | On 14 Dec 2000, Akim Demaille wrote:
> | > | % ./i386-mingw32msvc-gcc -o run tmp.c
> | > 
> | > What happens if you don't -o?  And are there any problems with run
> | > instead of run.exe?  Why is it wrong?
> | 
> | Drum roll please ...
> | 
> | % rm *.exe
> | % ./i386-mingw32msvc-gcc tmp.c
> | mo(~/project/install/Xmingwin/bin)% ls *.exe
> | a.exe
> | 
> | % rm *.exe
> | % i586-cygwin32-gcc tmp.c
> | % ls *.exe
> | a.exe
> 
> Yipeeeeeeee|  Hey Alexandre, did you see that!?!
> 
> Wow, I think this is the first time a MingWinEMX/32 message makes me
> happy :)

Glad I could help. 
 
> Also, please Mo, for my own information, what is wrong with `run'
> instead of `run.exe'?

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

Mo DeJong
Red Hat Inc



reply via email to

[Prev in Thread] Current Thread [Next in Thread]