public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: Saifi Khan <saifi.khan@nishan.io>
To: 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:24:39 +0000	[thread overview]
Message-ID: <d0f48fde1d279df3f44a593ec0734218@nishan.io> (raw)
In-Reply-To: <CAH6eHdQvnfhu9+6ua0o80FQvUtBRPxu0XdTHeK3GosLifsSubg@mail.gmail.com>

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 ?

warm regards
Saifi.

  reply	other threads:[~2022-11-14 16:24 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 [this message]
2022-11-14 16:56         ` Jonathan Wakely
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=d0f48fde1d279df3f44a593ec0734218@nishan.io \
    --to=saifi.khan@nishan.io \
    --cc=gcc-help@gcc.gnu.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).