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 other/102663] New: add an install-dvi Makefile target to the toplevel Makefile and all subdirectories
Date: Sat, 09 Oct 2021 14:18:30 +0000 [thread overview]
Message-ID: <bug-102663-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102663
Bug ID: 102663
Summary: add an install-dvi Makefile target to the toplevel
Makefile and all subdirectories
Product: gcc
Version: 12.0
URL: https://gcc.gnu.org/legacy-ml/gcc-patches/2016-10/msg0
0380.html
Status: UNCONFIRMED
Keywords: documentation, patch
Severity: normal
Priority: P3
Component: other
Assignee: unassigned at gcc dot gnu.org
Reporter: egallager at gcc dot gnu.org
Target Milestone: ---
Some subdirectories have dvi targets that allow building of dvi-formatted
documentation, but they don't have install-dvi targets, meaning the dvi files
have to be copied to the docdir manually. I had a patch for this at one point,
but it never got reviewed, and I'm not sure if it applies any longer:
https://gcc.gnu.org/legacy-ml/gcc-patches/2016-10/msg00380.html
next reply other threads:[~2021-10-09 14:18 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-09 14:18 egallager at gcc dot gnu.org [this message]
2021-10-11 10:42 ` [Bug other/102663] " marxin at gcc dot gnu.org
2021-10-14 16:28 ` law at gcc dot gnu.org
2021-10-15 8:16 ` marxin at gcc dot gnu.org
2021-10-16 4:40 ` egallager at gcc dot gnu.org
2021-10-19 1:33 ` egallager at gcc dot gnu.org
2021-10-22 22:43 ` cvs-commit at gcc dot gnu.org
2021-10-22 22: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-102663-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: 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).