|--==> "JJ" == Jerry James <james(a)xemacs.org> writes:
JJ> Steve Youngs <youngs(a)xemacs.org> wrote:
>Ah! That's gotta be the problem. Two questions: Why is there
>configure.ac in there in the first place? And why is it
JJ> It's there because I made the modules buildable in any of these 3
JJ> a) as part of the core in a --without-modules XEmacs;
JJ> b) as modules built at the same time as the core in a --with-modules
JJ> XEmacs; and
JJ> c) as modules built independently of the core XEmacs distribution.
OK, fair enough.
JJ> I keep hearing noises about people working on autoconf 2.5x
JJ> support for the core, so I hope that the core will catch up at
JJ> some point.
Yes, me too.
JJ> So now we need to figure out why it isn't working that way for you.
JJ> Here's a shot in the dark: is the cvs checkout procedure automatically
JJ> running autoconf for you on the module configure.ac files? If so, I can
JJ> well imagine that there is top-level configure or makefile magic that
JJ> says, "run all configure scripts in subdirectories".
I wouldn't think so. I normally:
(cvs-update "/some/path/" t)
Or just plain 'cvs up' from the command line.
|---<Steve Youngs>---------------<GnuPG KeyID: 10D5C9C5>---|
| XEmacs - It's not just an editor. |
| It's a way of life. |