autoconf-patches
[Top][All Lists]
Advanced

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

RE: [PATCH] A better (?) _AC_EXEEXT


From: Bernard Dautrevaux
Subject: RE: [PATCH] A better (?) _AC_EXEEXT
Date: Thu, 12 Oct 2000 10:25:54 +0200

> -----Original Message-----
> From: Bernard Dautrevaux 
> Sent: Thursday, October 12, 2000 10:13 AM
> To: 'Akim Demaille'; Pavel Roskin
> Cc: Morten Eriksen; address@hidden
> Subject: RE: [PATCH] A better (?) _AC_EXEEXT
> 
> 
> > -----Original Message-----
> > From: Akim Demaille [mailto:address@hidden
> > Sent: Wednesday, October 11, 2000 6:31 PM
> > To: Pavel Roskin
> > Cc: Morten Eriksen; address@hidden
> > Subject: Re: [PATCH] A better (?) _AC_EXEEXT
> > 
> > 
>       ...
> > 
> > | > Aha. How about the attached patch, then?
> > | 
> > | > +  if (test conftest -ef conftest.exe) >/dev/null 2>&1; then
> > | 
> > | Why do you want to set ac_exeext to ".exe" is conftest is 
> > the same as
> > | conftest.exe? 
> > 
> > No idea, I guess Morten has his own idea about that :)
> > 
> 
> Probably because quite a lot of native Win32 (and probably 
> also DOS or OS/2) programs will not recognize "conftest" as 
> an executable, while "conftest.exe" will be :-)
> 

Oops; I've clicked "send" a bit too fast:

I have another problem with the patch (I just re-read the whole thread): It
is well possible the compiler accepts to create an executable without any
suffix on Win32 (I think I remember that "gcc -o conftest conftest.c" will
create conftest only), but in a lot of cases "conftest" will *not* be
recognized as an executable (for example by cmd.exe...). This is especially
a problem if you use MinGW32, as cygwin bash will accept to run "conftest"
without any problem...

I don't think there is *any* way to automatically detect this "feature" of
the Win32 target system other than *knowing* it; the worst think being that
it's almost impossible to setup a true native Win32 environment on which to
run the configure script: you need a true bourne shell, with all associated
utilities and even if cygwin is not the only viable solution (although I
doubt there is another one), we will in fact always be cross-compiling
native Win32 programs... 

Testing we're able to create "conftest" and there is no "conftest.exe"
created is not enough usually and I'm afraid we can't get rid of the
explicit check for Win32-DOS-OS/2 platforms (at least for Win32).

Sorry to only react today; I were not able to follow the thread as it was
discussed.

Regards,

        Bernard

PS: OK I know Win32 will be able to execute "conftest" without extension:
the problem is that you may need to ask it to execute "conftest." (note the
trailing dot), so that does not help so much :-)

--------------------------------------------
Bernard Dautrevaux
Microprocess Ingenierie
97 bis, rue de Colombes
92400 COURBEVOIE
FRANCE
Tel:    +33 (0) 1 47 68 80 80
Fax:    +33 (0) 1 47 88 97 85
e-mail: address@hidden
                address@hidden
-------------------------------------------- 



reply via email to

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