From: Jonathan Wakely <jwakely.gcc@gmail.com>
To: saifi.khan@nishan.io
Cc: gcc-help <gcc-help@gcc.gnu.org>
Subject: Re: top-level build target that triggers 'make doc-html-doxygen'
Date: Mon, 14 Nov 2022 16:56:23 +0000 [thread overview]
Message-ID: <CAH6eHdS9fZE=rn1qjSmOJVRrpx8MzTXkt=VFxqQKus8UqUnNzg@mail.gmail.com> (raw)
In-Reply-To: <d0f48fde1d279df3f44a593ec0734218@nishan.io>
On Mon, 14 Nov 2022 at 16:25, Saifi Khan <saifi.khan@nishan.io> wrote:
>
> On 2022-11-13 09:29, Jonathan Wakely via Gcc-help wrote:
> >
> > There is a doc-install-html target in the $target/libstdc++-v3 dir, but
> > that will also try to build the main manual as well as the doxygen
> > pages.
> >
>
> yes, this seems even better. So, i tried to build the 'doc-install-html'
> target
>
> xsltproc --param toc.section.depth 4 --param generate.consistent.ids 1
> --nonet --xinclude -o
> /opt/gcc/build/x86_64-pc-linux-gnu/libstdc++-v3/doc/docbook/html/ \
> --stringparam chunker.output.encoding UTF-8 \
> /xhtml/chunk.xsl \
> ../../../../src/libstdc++-v3/doc/xml/spine.xml
> warning: failed to load external entity "/xhtml/chunk.xsl"
> cannot parse /xhtml/chunk.xsl
> make[1]: *** [Makefile:1046: stamp-html-docbook] Error 4
> make[1]: Leaving directory
> '/opt/gcc/build/x86_64-pc-linux-gnu/libstdc++-v3/doc'
> make: *** [Makefile:784: doc-install-html] Error 2
> make: Leaving directory
> '/opt/gcc/build/x86_64-pc-linux-gnu/libstdc++-v3'
>
> There isn't any 'chunk.xsl' in the entire source tree.
>
> Am i missing something ?
Yes, you're missing a docbook installation.
https://gcc.gnu.org/onlinedocs/libstdc++/manual/documentation_hacking.html#doc.docbook
next prev parent reply other threads:[~2022-11-14 16:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-13 7:28 Saifi Khan
2022-11-13 8:29 ` Jonathan Wakely
2022-11-13 9:10 ` Saifi Khan
2022-11-13 9:29 ` Jonathan Wakely
2022-11-14 16:24 ` Saifi Khan
2022-11-14 16:56 ` Jonathan Wakely [this message]
2022-11-14 17:10 ` Saifi Khan
2022-11-22 14:04 Saifi Khan
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='CAH6eHdS9fZE=rn1qjSmOJVRrpx8MzTXkt=VFxqQKus8UqUnNzg@mail.gmail.com' \
--to=jwakely.gcc@gmail.com \
--cc=gcc-help@gcc.gnu.org \
--cc=saifi.khan@nishan.io \
/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).