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.
-- Lindsay Haisley | "I felt a great disturbance in the Force, FMP Computer Services | as if millions of voices suddenly cried out 512-259-1190 | in terror and were suddenly silenced." http://www.fmp.com | - Obi-Wan Kenobi _______________________________________________ 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
