-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Please keep replies on list, so that others may see them in the archives, and so that you are more likely to get a decent response. I am not the official m4 maintainer, only an interested party since I maintain the cygwin distribution of m4. The maintainer, Gary Vaughn, is currently occupied with putting finishing touches on libtool 2.0 at the moment.
According to Mikhail Teterin on 12/17/2005 12:11 PM: >>Since m4 2.0 will use the gnulib regexp module by default, you will >>be missing out on all these patches to deficiencies in glibc if you >>insist on using the glibc regexp. > > > I don't, actually, insist on one over the other -- I just don't want to > see two (slightly different) versions of the same thing. Then YOU try convincing the glibc maintainers to fold in all the gnulib regexp patches (it's a tough job, as Paul Eggert already found out). > > >>Then you can offer to help by speeding up the release of libtool 2.0, >>so that the release of m4 2.0 can follow. > > > Sorry, my plate is overfilling already. That said, I don't understand, > how libtool, which is merely a tool for software building, can delay a > release of the software itself. > > Can't you put it into a README to use the compiler and linker directly? m4 2.0 depends on dynamic modules. Not all platforms support dlopen(), and even those that do have different semantics. Libtool is absolutely essential to getting sane behavior of dynamic modules across as many platforms as the current m4 1.4 targets; without libtool support, it would be impossible to just put out a README of how to compile. But you are welcome to check out the m4 CVS repository and build it yourself to see what will be available when m4 2.0 is finally released; note that CVS m4 currently requires CVS libtool, autoconf, and automake. > > Seems like in trying to make it easy for the dimmest, you are delaying > the gratification of the normal :-( > > -mi > - -- Life is short - so eat dessert first! Eric Blake [EMAIL PROTECTED] -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (Cygwin) Comment: Public key at home.comcast.net/~ericblake/eblake.gpg Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFDprCU84KuGfSFAYARAmOZAJ4hJTD7XOlee2DUdJXkt0SutjLJHQCfRjT+ qIH+gTXGJvNOxugW2U4Je18= =K/OS -----END PGP SIGNATURE----- _______________________________________________ Bug-m4 mailing list [email protected] http://lists.gnu.org/mailman/listinfo/bug-m4
