public inbox for kawa@sourceware.org
 help / color / mirror / Atom feed
From: Per Bothner <per@bothner.com>
To: Sudarshan S Chawathe <chaw@eip10.org>
Cc: kawa <kawa@sourceware.org>
Subject: Re: Building documentation, chunkfast.xsl URL in doc/style/kawa.xsl
Date: Sun, 30 Apr 2017 22:46:00 -0000	[thread overview]
Message-ID: <463dce7a-7804-6411-6efd-a646215ac18d@bothner.com> (raw)
In-Reply-To: <10604.1493583901@vereq.eip10.org>

On 04/30/2017 01:25 PM, Sudarshan S Chawathe wrote:
> So based on the above, the correct path to give to configure's
> --with-docbook-stylesheets option on Debian would be
> 
>    /usr/share/xml/docbook/stylesheet/docbook-xsl-ns

I noted that in the instructions.

> To test it all, I just did a fresh build starting from git pull and
> everything worked great, except for building kawa.pdf.
> 
> The 'make' also built kawa-manual.epub by default, which I'm guessing is
> a side effect of using the --with-docbook-stylesheets option, as I don't
> recall that happening on my earlier builds.  I was also able to build
> the "fancy" and "plain" HTML docs properly.

Yep.

I tweaked the instructions for building the documentation
to hopefully make tings clearer.

> The only minor problem seems to be building kawa.pdf, which is likely
> something outdated on my system. I did use a newish version of texinfo
> (6.3) since I know that's needed by Kawa.  Not sure if it's worth
> chasing, but I'm including the error from 'make kawa.pdf' (in the doc
> subdirectory) below for reference.

I made a minor fix to kawa.texi that avoids the problem.

Thanks for your testing!
-- 
	--Per Bothner
per@bothner.com   http://per.bothner.com/

  reply	other threads:[~2017-04-30 22:46 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-30 17:26 Sudarshan S Chawathe
2017-04-30 17:56 ` Per Bothner
2017-04-30 18:38   ` Sudarshan S Chawathe
2017-04-30 18:54     ` Per Bothner
2017-04-30 20:25       ` Sudarshan S Chawathe
2017-04-30 22:46         ` Per Bothner [this message]
2017-04-30 23:21           ` Sudarshan S Chawathe

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=463dce7a-7804-6411-6efd-a646215ac18d@bothner.com \
    --to=per@bothner.com \
    --cc=chaw@eip10.org \
    --cc=kawa@sourceware.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).