Re: We need to get rid of configure.ac stub

SY> My autoconf doesn't do this, and I haven't heard of anyone SY> else's autoconf doing it either. Debian's has done this since about ac 2.53. I believe SuSE and Red Hat both do, as well. SY> And, just out of curiosity, what does this cygwin autoconf SY> wrapper do when faced with a configure.in that is for autoconf SY> 2.5x only? I've come across plenty of those. The Debian wrapper will puke, in a rather uninformative way if there's no AC_REQUIRE. Ben, please don't remove it. The right thing to do is to update XEmacs's configure.in to 2.5x compatibility. There's a patch in the queue from SuSE, has been for a long time (I've been hoping Didier would resurrect himself and review it ...). I suspect that cp configure.in configure.ac patch -p 0 <suse.patch would be enough to make everybody happy for the moment. autoconf2.13 will ignore configure.ac, and autoconf2.5x will give configure.ac precedence over configure.in. In particular, as long as we keep configure itself in CVS, we can always unhose the bleeding edge users by reverting configure to an autoconf built from configure.in. How's that sound? -- Institute of Policy and Planning Sciences http://turnbull.sk.tsukuba.ac.jp University of Tsukuba Tennodai 1-1-1 Tsukuba 305-8573 JAPAN Ask not how you can "do" free software business; ask what your business can "do for" free software.