On Dec 12, 2000, [EMAIL PROTECTED] wrote:
> EXEEXT and OBJEXT don't need to know $CYGWIN etc.
Ok, but I'd rather have the macros renamed to either _AC_HOST_???EXT
or _AC_CC_???EXT (and only test with the C compiler).
But I'm also a bit unsure as to whether we should use _AC_LINK_IFELSE,
given that this macro will tell the compiler to create an executable
named `conftest', and this may disable whatever default extension the
compiler might have selected. The bad side of this is that, if we
leave the decision up to the compiler, we'll get a.out or a.exe, which
is out of autoconf's file namespace.
> There remains just one question: what shall we do out of AC_CYGWIN etc.
> simply AU define them as [...]
Yep.
--
Alexandre Oliva Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/
Red Hat GCC Developer aoliva@{cygnus.com, redhat.com}
CS PhD student at IC-Unicamp oliva@{lsd.ic.unicamp.br, gnu.org}
Free Software Evangelist *Please* write to mailing lists, not to me
