Re: Five bugs (IBM-PC systems)

[Tim Van Holder]

> Pavel Jan Lastovicka <address@hidden> writes:
> 
> > the following is produced:  
> >    for ac_exec_ext in '' $ac_executable_extensions;
> > 
> > but ac_executable_extensions is nowhere defined.
> 
> Got me as to why it does that.  That change was checked in by 
> Zastai on
> 2001-09-20.  Here's the ChangeLog entry:
> 
>         2001-09-20  Tim Van Holder  <address@hidden>
> 
>                 * lib/autoconf/programs.m4: Use extensions listed in
>                 $ac_executable_extensions when looking for programs.
> 
> Perhaps Tim can comment.

This was added so a DOSish system (or any other system where it is
relevant) can set ac_executable_extensions in a config.site (as DJGPP
does).
The idea was that at some point in the future, configure would get
some magic to figure out valid values for that variable itself - but
given the 'test for feature, not for system' philosophy that hardly
seems a trivial test.  There should be a couple of threads about this
on the autoconf lists around the time of that checkin.

> >   if test "$CYGWIN" = yes || test "$MINGW32" = yes || test 
> "$DJ_GPP" = yes ; then
> 
> I don't see this in CVS Autoconf.

That seems very very old code to me - those variables were the
result of the old AC_CYGWIN etc checks (which mainly set EXEEXT);
those were obsoleted when the 'smart' EXEEXT was added to the C
compiler setup.