>The document is valid. It just built successfully today. You probably
>specified the wrong dtd version, or have xml catalog issues. The other
>possible issue is xincludes. Regardless, the xml docbook _set_ is
>valid.
I don't know XML. That makes no sense to me.
>PDF generation was part of our
Hi Mike,
> -Original Message-
> From: Mike Noyes [mailto:[EMAIL PROTECTED]
> PDF generation was part of our old documentation build
> process. It did work, but wasn't what I'd call acceptable.
> The wiki install was in my to-do list much longer than you
> realize (around three years).
On Wed, 2006-07-05 at 01:55, Luis.F.Correia wrote:
> Please do not consider this comment as another direct assault to
> your private decisions on how to schedule your work.
Luis,
Understood.
> PDF generation is already waiting for some time, while preparing
> and installing a wiki is relatively a
Hi everybody
some of you may have seen my odyssey getting a buildenv for uClibc up
and running. With lots of help and patience by Eric Spakman I finally
got the CVS HEAD to compile without barfing on my SuSE 9.2 .
Now the 2.4.2 tagged release is not as gentle, as it still contains some
of the
Hi!
> -Original Message-
> From: Mike Noyes [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, July 04, 2006 9:48 PM
> To: leaf-devel@lists.sourceforge.net
> Subject: Re: [leaf-devel] Docs
>
> On Tue, 2006-07-04 at 02:24, Eric Spakman wrote:
> > I fully agree, but unfortuanatly I can't do anyth
Hi Erich,
I will take a look at it, although I can't remember seeing this in my test...
Eric
> Eric
>
>
> some more information. Although wlan-ng appears to compile correctly, not
> all is well in config.mk
>
> CROSS_COMPILE=/data/leaf/bering-uclibc/devel/latest/src/bering-uclibc/bui
> ldtool/st
