| --- orig/automake.in.orig Mon Mar 12 06:44:59 2001
| +++ automake.in Mon Mar 12 07:44:57 2001
| @@ -1048,8 +1048,17 @@
| # If OBJEXT/EXEEXT were not set in configure.in, do it, it
| # simplifies our task, and anyway starting with Autoconf 2.50, it
| # will always be defined, and this code will be dead.
| - $output_vars .= "EXEEXT =\n"
| - unless $seen_exeext;
| + unless($seen_exeext)
| + {
| + if ($^O =~ /(cygwin|MSWin32)/)
| + {
| + $output_vars .= "EXEEXT = .exe\n";
| + }
| + else
| + {
| + $output_vars .= "EXEEXT = \n";
| + }
| + }
| $output_vars .= "OBJEXT = o\n"
| unless $seen_objext;
Huh? It is still wrong. This has no reason to depend upon the
machine on which you run automake.
Rather the proper fix seems to have the failing tests include
AC_EXEEXT and AC_OBJEXT in their configure.in.
- Re: ok, new libtool for cygwin updates edward
- Re: ok, new libtool for cygwin updates Robert Collins
- Re: ok, new libtool for cygwin updates Robert Collins
- Re: ok, new libtool for cygwin updates Akim Demaille
- Re: ok, new libtool for cygwin updates edward
- Re: ok, new libtool for cygwin updates Akim Demaille
- Re: ok, new libtool for cygwin updates edward
- Re: ok, new libtool for cygwin updates Akim Demaille
- Re: ok, new libtool for cygwin updates Robert Collins
- Re: ok, new libtool for cygwin updates Alexandre Oliva
- RE: ok, new libtool for cygwin updates Robert Collins
- Re: ok, new libtool for cygwin updates Alexandre Oliva
- RE: ok, new libtool for cygwin updates Robert Collins
- Re: ok, new libtool for cygwin updates Gary V . Vaughan
- Re: ok, new libtool for cygwin updates edward
- Re: ok, new libtool for cygwin updates Gary V . Vaughan
