public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug other/107620] Build errors when using sphinx
Date: Sun, 13 Nov 2022 15:38:16 +0000 [thread overview]
Message-ID: <bug-107620-4-Dp3ZaXNtjx@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-107620-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107620
Martin Liška <marxin at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |FIXED
Status|ASSIGNED |RESOLVED
--- Comment #6 from Martin Liška <marxin at gcc dot gnu.org> ---
>
> I found that using that allowed me to build html documentation. However I
> seemed to need in addition a whole bunch of stuff to build latex and pdf
> documentation.
Yes, these dependencies are usually installed if you install
python3-Sphinx-latex package.
prev parent reply other threads:[~2022-11-13 15:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-10 16:45 [Bug other/107620] New: " vvinayag at arm dot com
2022-11-11 15:56 ` [Bug other/107620] " marxin at gcc dot gnu.org
2022-11-12 18:38 ` vvinayag at arm dot com
2022-11-13 10:38 ` ramana at gcc dot gnu.org
2022-11-13 15:36 ` cvs-commit at gcc dot gnu.org
2022-11-13 15:37 ` marxin at gcc dot gnu.org
2022-11-13 15:38 ` marxin at gcc dot gnu.org [this message]
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=bug-107620-4-Dp3ZaXNtjx@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@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).