Re: A couple of problems with new module code.

Steve Youngs <youngs(a)xemacs.org&gt; wrote: It's there because I made the modules buildable in any of these 3 situations: a) as part of the core in a --without-modules XEmacs; b) as modules built at the same time as the core in a --with-modules XEmacs; and c) as modules built independently of the core XEmacs distribution. Situation (c) means that the module code has to determine certain things for itself, a task for which autoconf is well suited. The reason for the autoconf 2.53 prerequisite is that (1) the module autoconf stuff is completely independent from the core XEmacs autoconf stuff, so it might as well use the latest and greatest, and (2) I keep hearing noises about people working on autoconf 2.5x support for the core, so I hope that the core will catch up at some point. Actually, that is the way it is supposed to work in cases (a) and (b). So now we need to figure out why it isn't working that way for you. Here's a shot in the dark: is the cvs checkout procedure automatically running autoconf for you on the module configure.ac files? If so, I can well imagine that there is top-level configure or makefile magic that says, "run all configure scripts in subdirectories". -- Jerry James http://www.ittc.ku.edu/~james/