Your message dated Sun, 3 Jan 2016 09:28:18 -0800 with message-id <[email protected]> and subject line Bug #100150: no longer relevant with automake still in Debian has caused the Debian Bug report #100150, regarding autoconf2.13 breaks on previously-working configure.in 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 [email protected] immediately.) -- 100150: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=100150 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: autoconf2.13 This bug has been reported a few times, I think, but doesn't appear to have been fixed yet, and the last incidence of it I see in the Debian bug logs wasn't exactly for the same thing. AC_EXEEXT gets set to ".C" when configuring c++ programs in many cases, where as recently as a couple of weeks ago it did not. This causes lots of problems with using AC_TRY_RUN to test for the sanity of c++ libraries. This isn't just an academic problem. Programs using the current Debian libsigc++-dev package will not configure any more using the current Debian autoconf packages. Attached is a trivial autoconf package using sigc++ that demonstrates the problem. Thanks, Bill Gribble
--- End Message ---
--- Begin Message ---The example test.tar.gz attached to this script no longer works with the oldest Automake still in Debian (which is 1.11): blp@sigabrt:~/debian/autoconf/test(0)$ automake-1.11 -a automake-1.11: no `Makefile.am' found for any configure output automake-1.11: Did you forget AC_CONFIG_FILES([Makefile]) in configure.in? I don't think autoconf2.13 is the weakest link here, so I'm closing the bug. If anyone disagrees, please feel free to reopen the bug (but please also explain what you'd like to happen to fix it). Thanks, Ben.
--- End Message ---
