public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Stephane Wirtel <stephane.wirtel@belgacom.net>
To: Sam Ravnborg <sam@ravnborg.org>,
	Stephane Wirtel <stephane.wirtel@belgacom.net>,
	Pekka Enberg <penberg@gmail.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [Documentation] Use doxygen or another tool to generate a documentation ?
Date: Sun, 21 Aug 2005 20:32:42 +0200	[thread overview]
Message-ID: <20050821183242.GA18020@localhost.localdomain> (raw)
In-Reply-To: <20050821151231.GE9530@admingilde.org>

\b

> On Sat, Aug 20, 2005 at 07:37:06PM +0200, Sam Ravnborg wrote:
> > > In make_docs.log.tar.bz2, you can find log files from make htmldocs,
> > > make psdocs and make pdfdocs.
> > 
> > From your log-files I could not see what went wrong. It seems to be
> > error in the generated files.
> 
> kerneldoc could not understand a macro definition.
> 
> please try
> http://tali.admingilde.org/patches/linux-docbook/docbook-fixes.patch
Martin, your patch works for the htmldocs target, but not for the
pdfdocs, I think there is a bug in a latex package. I don't know which
one, but it's the same error.

Thanks for your patch, 

Stephane

-- 
Stephane Wirtel <stephane.wirtel@belgacom.net>
                <stephane.wirtel@gmail.com>



  reply	other threads:[~2005-08-21 21:34 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-19 21:34 [Documentation] Use doxygen or another tool to generate a documentation ? Stephane Wirtel
2005-08-19 21:46 ` Pekka Enberg
2005-08-19 23:23   ` Stephane Wirtel
2005-08-20  7:41     ` Sam Ravnborg
2005-08-20  9:19       ` Stephane Wirtel
2005-08-20 17:37         ` Sam Ravnborg
2005-08-21 12:28           ` Stephane Wirtel
2005-08-21 15:12           ` Martin Waitz
2005-08-21 18:32             ` Stephane Wirtel [this message]
2005-08-22  7:45               ` Martin Waitz

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20050821183242.GA18020@localhost.localdomain \
    --to=stephane.wirtel@belgacom.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=penberg@gmail.com \
    --cc=sam@ravnborg.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox