|--==> "JJ" == Jerry James <james(a)xemacs.org> writes:
JJ> And here is another clue. You shouldn't be getting these
JJ> warnings. Let's figure out why you are. There is a
JJ> configure.ac in the modules/postgresql directory. Has that been
JJ> instantiated? That is, is there a configure script in that
JJ> directory? If so, has it been run (e.g., is there a config.log
JJ> there)?
Ah! That's gotta be the problem. Two questions: Why is there a
configure.ac in there in the first place? And why is it
'AC_PREREQ(2.53)'?
The reasons I asked those two questions are:
a) There are a _lot_ of subdirectories in core and the _only_ place
apart from toplevel that any configure scripts are is in the
modules...
,----[ find ./ -regex "^.*configure\.\(ac\|in\)$" ]
| ./configure.in
| ./modules/ldap/configure.ac
| ./modules/sample/external/configure.ac
| ./modules/sample/internal/configure.ac
| ./modules/postgresql/configure.ac
| ./configure.ac
`----
b) XEmacs' autoconf requirement is 2.13, we've got too much home
grown magic voodoo chicken spells in our configure that give
autoconf 2.5x bad indigestion...
,----[ ./configure.ac ]
| AC_FATAL([
|
| #### Autoconf 2.5x is not yet supported by XEmacs.
| #### Our configure script is known *not* to work with these versions of
| #### Autoconf. Please continue using Autoconf 2.13 for now.
| ])
`----
I think the modules should be configured from the toplevel configure
script, no? Feel free to shoot me down in flames if you think I'm
wrong.
--
|---<Steve Youngs>---------------<GnuPG KeyID: 10D5C9C5>---|
| XEmacs - It's not just an editor. |
| It's a way of life. |
|------------------------------------<youngs(a)xemacs.org>---|