The following bug was reported against the Debian package for autoconf, presumably version 2.13-20, though the correspondent didn't note that. It seems that it's something that should be considered in upstream, rather than at the Debian level, so I am forwarding it to this list. I'd appreciate it if the CC: to [EMAIL PROTECTED] were preserved in replies. Thanks, Ben. ------- Start of forwarded message ------- Subject: Bug#58039: autoconf: AC_EXEEXT incompatible with AC_MINIX, AC_ISC_POSIX? To: [EMAIL PROTECTED] From: [EMAIL PROTECTED] Date: Sun, 13 Feb 2000 17:13:03 +0000 Message-Id: <[EMAIL PROTECTED]> Package: autoconf Version: Either I'm very confused, or it's not possible to use the autoconf tests AC_EXEEXT and AC_MINIX in the same configure.in... AC_EXEEXT sets the extension used by executables (generally "" for Unix, but ".exe" for DOS). As such it must be run before AC_PROG_CC, which tests the C compiler by compiling a trivial program and checking that the output exists. [If exeext isn't set by this point, it checks for the existence of foo when the compiler has produced foo.extension and fails claiming the compiler to be broken.] AC_PROG_CC must come before AC_MINIX, because AC_PROG_CC sets the variables defining what the C preprocessor is, and AC_MINIX uses that. Unfortunately, AC_MINIX has an explicit check that you don't call AC_TRY_COMPILE before checking AC_MINIX. And AC_EXEEXT calls AC_TRY_COMPILE, so AC_EXEEXT must come before AC_MINIX. Oops. The symptoms of this are that either autoconf refuses to create configure, giving an error message: configure.in:246: AC_TRY_COMPILE was called before AC_MINIX or autoconf runs fine but the AC_PROG_CC erroneously claims the C compiler doesn't work, depending on which order you put the tests in configure.in. There's a similar problem with AC_ISC_POSIX. Disclaimer: the target machine in my case is not actually DOS, it's an OS developed by my employer. In this case if you say "cc -o foo foo.c" the executable produced has the name "foo.00". It's possible that the DOS/win32 compilers AC_EXEEXT was originally intended to help don't have this behaviour. Nevertheless, I'd claim this is still a bug in autoconf... Peter Maydell ------- End of forwarded message -------
