public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit 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, 06 Apr 2022 20:21:05 +0000 [thread overview]
Message-ID: <bug-102824-4-anPS9Qt3o9@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 #3 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by David Malcolm <dmalcolm@gcc.gnu.org>:
https://gcc.gnu.org/g:790e9814454662b6cd51d2fce1aa022ef73fedb8
commit r12-8031-g790e9814454662b6cd51d2fce1aa022ef73fedb8
Author: David Malcolm <dmalcolm@redhat.com>
Date: Wed Apr 6 16:20:10 2022 -0400
jit: fix location of .png files for "make jit.pdf" [PR102824]
"make jit.pdf" seems to be looking in
gcc/jit/docs/_build/texinfo/libgccjit-figures
for the .png files, but they were in the source tree in:
gcc/jit/docs/_build/texinfo
Fix "make jit.pdf" via:
git mv \
gcc/jit/docs/_build/texinfo/*.png \
gcc/jit/docs/_build/texinfo/libgccjit-figures
gcc/jit/ChangeLog:
PR jit/102824
* docs/_build/texinfo/factorial.png: Move to...
* docs/_build/texinfo/libgccjit-figures/factorial.png: ...here.
* docs/_build/texinfo/factorial1.png: Move to...
* docs/_build/texinfo/libgccjit-figures/factorial1.png: ...here.
* docs/_build/texinfo/sum-of-squares.png: Move to...
* docs/_build/texinfo/libgccjit-figures/sum-of-squares.png:
...here.
* docs/_build/texinfo/sum-of-squares1.png: Move to...
* docs/_build/texinfo/libgccjit-figures/sum-of-squares1.png:
...here.
Signed-off-by: David Malcolm <dmalcolm@redhat.com>
next prev parent reply other threads:[~2022-04-06 20:21 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 [this message]
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
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-anPS9Qt3o9@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).