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

Bug#58039: marked as done (autoconf: AC_EXEEXT incompatible with AC_MINIX, AC_ISC_POSIX?)

Your message dated Mon, 22 Dec 2025 18:02:22 +0000
with message-id <[🔎] E1vXkEg-00GKT8-2W@fasolo.debian.org>
and subject line Bug#1081135: Removed package(s) from unstable
has caused the Debian Bug report #58039,
regarding autoconf: AC_EXEEXT incompatible with AC_MINIX, AC_ISC_POSIX?
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
58039: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=58039
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
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 Message ---
--- Begin Message --- 
Version: 2.13-69+rm

Dear submitter,

as the package autoconf2.13 has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/1081135

The version of this package that was in Debian prior to this removal
can still be found using https://snapshot.debian.org/.

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmaster@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Thorsten Alteholz (the ftpmaster behind the curtain)

--- End Message ---
Reply to: