On 01/07/2018 12:28 PM, Lindsay Haisley wrote: > What's the proper way to run autoconf on configure.in in MM2 in order > to _not_ generate runstatedir options and code in the configure script? > I note that the distributed configure script in MM2 doesn't have them, > but simply running autoconf on configure.in produces a configure script > that does. This option is harmless enough, since MM apparently doesn't > need or use it, but for simplicity I'd like to be able to generate a > configure script without it.
In my case, my autoconf which didn't generate those options in 2014 when I generated the current configure and which then was probably debian/ubuntu version 2.69-7 is now debian/ubuntu version 2.69-9 and it does generate them. See <https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=759647>. The bottom line is this is something that newer autoconf does and if your autoconf does it, I don't know a way to turn it off. -- Mark Sapiro <m...@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan _______________________________________________ Mailman-Developers mailing list Mailman-Developers@python.org https://mail.python.org/mailman/listinfo/mailman-developers Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-developers%40python.org/ Unsubscribe: https://mail.python.org/mailman/options/mailman-developers/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
