Re: makeinfo --xml output not well-formed

[Oleg Katsitadze]

On Fri, Jul 13, 2007 at 05:41:19PM -0500, Karl Berry wrote:
>     I've had the same problem with today's checkout.  After I ran
> 
> I think this is to be expected if you start with autogen.sh, since
> gnulib is so dynamic.

Ok, then maybe we can mention this in README.dev.  Currently it says
"If you want to update from the current gnulib".  Well, I certainly
didn't want to update, and the error messages are not particularly
indicative that I _should_ update.  Granted, I'm a complete newbie in
autotools, but maybe we don't want to drive off dummies like me.
Maybe something like this:

--- README.dev  12 Aug 2006 16:38:10 +0300      1.11
+++ README.dev  14 Jul 2007 12:23:47 +0300      
@@ -34,3 +34,5 @@
 After getting the CVS sources, and installing the tools above, you can run
   ./autogen.sh
 to do a fresh build.  After that first time, running make should suffice.
+If you encounter problems running autogen.sh, try updating from the
+current gnulib as described above.

> I keep gnulib and various other autotools files in CVS precisely so
> autogen.sh should not be necessary -- it should suffice to simply run
> configure.

But there's no configure in the repository.  If you mean running only
autoconf, it doesn't work either -- warnings about possibly undefined
macros, and the produced configure is unusable.

> I'll update gnulib in due course.  It would cause more trouble than it
> would solve to try to track it completely.

As far as I'm concerned, it's fine as it is now, if only README.dev is
clearer on the possibly necessary gnulib update.

Cheers,
Oleg