* Ben Wing <ben(a)666.com> writes:
In my recent Cygwin installation, `autoconf' is actually a
wrapper
that automatically runs v2.13 or v2.59 depending on the presence
of configure.in or configure.ac. I suspect this is a general
setup for autoconf. Unfortunately, the presence of configure.ac
screws this up. I'm going to delete this unless someone protests.
No! Do not do this! Do not pass go, do not collect $200, do go
directly to jail!!
My autoconf doesn't do this, and I haven't heard of anyone else's
autoconf doing it either. It sounds to me like this is "cygwin
hackery". On the surface, what cygwin has done is a pretty good idea
and would work well in most situations and for most normal projects.
But XEmacs is _far_ from what I'd call a "normal" project.
Deleting configure.ac will hurt a lot more people than it will benefit.
Is that "protesty" enough?
Ben, if I were in your shoes, I'd delete that wrapper, symlink (or
alias) "autoconf" to the version I use most often, and then carry on
as normal.
And, just out of curiosity, what does this cygwin autoconf wrapper do
when faced with a configure.in that is for autoconf 2.5x only? I've
come across plenty of those.
--
|---<Steve Youngs>---------------<GnuPG KeyID: A94B3003>---|
| XEmacs - The only _______ you'll ever need. |
| Fill in the blank, yes, it's THAT good! |
|----------------------------------<steve(a)youngs.au.com>---|