public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "egallager at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug jit/102824] building pdf/dvi documentation for libgccjit fails
Date: Wed, 27 Mar 2024 15:47:45 +0000 [thread overview]
Message-ID: <bug-102824-4-SccYq5YeEj@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-102824-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102824
--- Comment #13 from Eric Gallager <egallager at gcc dot gnu.org> ---
(In reply to Iain Sandoe from comment #12)
> what input is this waiting for at the moment?
From checking the bug history, it looks like Martin Liška was the one to put
this in the WAITING status, which came along with this comment:
(In reply to Martin Liška from comment #7)
> Well, running 'make latexpdf' works if you jump into gcc/jit/docs folder. Do
> I miss something?
...which I thought we'd answered, but to make it a bit more clear: we shouldn't
have to do that to get the jit docs to build properly. They should build
properly when doing `make dvi` and/or `make pdf` from the top-level, rather
than requiring their own special procedures.
prev parent reply other threads:[~2024-03-27 15:47 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-19 1:43 [Bug jit/102824] New: building pdf/dvi documentation for libgccjit fails on darwin egallager at gcc dot gnu.org
2021-10-19 6:49 ` [Bug jit/102824] building pdf/dvi documentation for libgccjit fails iains at gcc dot gnu.org
2022-04-01 22:54 ` dmalcolm at gcc dot gnu.org
2022-04-06 20:21 ` cvs-commit at gcc dot gnu.org
2022-04-06 20:33 ` dmalcolm at gcc dot gnu.org
2022-04-08 22:48 ` egallager at gcc dot gnu.org
2023-01-06 4:12 ` egallager at gcc dot gnu.org
2023-01-06 8:19 ` marxin at gcc dot gnu.org
2023-01-06 8:50 ` iains at gcc dot gnu.org
2023-10-20 8:34 ` egallager at gcc dot gnu.org
2023-12-05 8:14 ` egallager at gcc dot gnu.org
2024-03-17 3:41 ` iains at gcc dot gnu.org
2024-03-27 15:47 ` egallager 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-102824-4-SccYq5YeEj@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).