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] New: building pdf/dvi documentation for libgccjit fails on darwin Date: Tue, 19 Oct 2021 01:43:47 +0000 [thread overview] Message-ID: <bug-102824-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102824 Bug ID: 102824 Summary: building pdf/dvi documentation for libgccjit fails on darwin Product: gcc Version: 12.0 Status: UNCONFIRMED Keywords: documentation Severity: normal Priority: P3 Component: jit Assignee: dmalcolm at gcc dot gnu.org Reporter: egallager at gcc dot gnu.org CC: iains at gcc dot gnu.org Target Milestone: --- Build: darwin Running `make pdf` fails in gcc/jit for me with the following error: !pdfTeX error: pdfetex: cannot find image file libgccjit-figures/sum-of-squares 1. ==> Fatal error occurred, no output PDF file produced! /opt/iains/x86_64-apple-darwin19/gcc-7-5-toolchain/bin/texi2dvi: pdfetex exited with bad status, quitting. make[2]: *** [../../gcc/jit/Make-lang.in:283: doc/libgccjit.pdf] Error 1 make[2]: Leaving directory '/Users/ericgallager/gcc_newgit/abcdefghijklmnopqrstuvwxyz_01234567890.build/gcc' make[1]: *** [Makefile:5361: pdf-gcc] Error 1 make[1]: Leaving directory '/Users/ericgallager/gcc_newgit/abcdefghijklmnopqrstuvwxyz_01234567890.build' make: *** [Makefile:1280: do-pdf] Error 2 I also got a similar error with `make dvi`, the full log for which can be found here: https://github.com/cooljeanius/gcc_bugs/blob/master/doc_logs/libgccjit.log (I originally reported this on IRC while testing a patch for bug 102663)
next reply other threads:[~2021-10-19 1:43 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-10-19 1:43 egallager at gcc dot gnu.org [this message] 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
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@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: linkBe 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).