public inbox for gcc-cvs@sourceware.org help / color / mirror / Atom feed
From: Martin Liska <marxin@gcc.gnu.org> To: gcc-cvs@gcc.gnu.org Subject: [gcc(refs/users/marxin/heads/sphinx-v6)] Local sync! Date: Tue, 15 Mar 2022 14:25:16 +0000 (GMT) [thread overview] Message-ID: <20220315142516.0681F3858D20@sourceware.org> (raw) https://gcc.gnu.org/g:fefcf018dc89172854d903e91298b76ffefa1bec commit fefcf018dc89172854d903e91298b76ffefa1bec Author: Martin Liska <mliska@suse.cz> Date: Tue Mar 15 15:25:06 2022 +0100 Local sync! Diff: --- gcc/d/doc/invoking-gdc.rst | 2 +- gcc/doc/cpp/invocation.rst | 2 +- .../the-gcc-subdirectory/anatomy-of-a-language-front-end.rst | 2 +- .../the-gcc-subdirectory/building-documentation.rst | 2 +- gcc/doc/install/final-installation.rst | 4 ++-- gcc/doc/install/prerequisites.rst | 2 +- gcc/go/doc/invoking-gccgo.rst | 2 +- 7 files changed, 8 insertions(+), 8 deletions(-) diff --git a/gcc/d/doc/invoking-gdc.rst b/gcc/d/doc/invoking-gdc.rst index 6bc0efd8d5f..d8f81658e9a 100644 --- a/gcc/d/doc/invoking-gdc.rst +++ b/gcc/d/doc/invoking-gdc.rst @@ -45,4 +45,4 @@ Options .. only:: man - .. include:: copyright.rst + .. include:: copyright.rst \ No newline at end of file diff --git a/gcc/doc/cpp/invocation.rst b/gcc/doc/cpp/invocation.rst index 6b58cd8380e..3c2d2b404ab 100644 --- a/gcc/doc/cpp/invocation.rst +++ b/gcc/doc/cpp/invocation.rst @@ -78,4 +78,4 @@ options may *not* be grouped: :option:`-dM` is very different from .. only:: man - .. include:: copyright.rst + .. include:: copyright.rst \ No newline at end of file diff --git a/gcc/doc/gccint/source-tree-structure-and-build-system/the-gcc-subdirectory/anatomy-of-a-language-front-end.rst b/gcc/doc/gccint/source-tree-structure-and-build-system/the-gcc-subdirectory/anatomy-of-a-language-front-end.rst index 276526ce8f8..3d2e226c820 100644 --- a/gcc/doc/gccint/source-tree-structure-and-build-system/the-gcc-subdirectory/anatomy-of-a-language-front-end.rst +++ b/gcc/doc/gccint/source-tree-structure-and-build-system/the-gcc-subdirectory/anatomy-of-a-language-front-end.rst @@ -219,7 +219,7 @@ standard rule in :samp:`gcc/Makefile.in` to the variable version of :command:`sphinx` is available, so does not need to check for this, and should fail if an error occurs. -``latexpdf`` +``pdf`` Build PDF documentation for the front end, in the build directory. ``html`` diff --git a/gcc/doc/gccint/source-tree-structure-and-build-system/the-gcc-subdirectory/building-documentation.rst b/gcc/doc/gccint/source-tree-structure-and-build-system/the-gcc-subdirectory/building-documentation.rst index 7902b8f58d4..5dbdf9b2822 100644 --- a/gcc/doc/gccint/source-tree-structure-and-build-system/the-gcc-subdirectory/building-documentation.rst +++ b/gcc/doc/gccint/source-tree-structure-and-build-system/the-gcc-subdirectory/building-documentation.rst @@ -12,7 +12,7 @@ The main GCC documentation uses `Sphinx`_ to generate pretty documentation from `reStructuredText`_ format. These are input for Manual pages format (:command:`make man`), Info format (:command:`make info`), HTML format (:command:`make html`), -PDF format (:command:`make latexpdf`) and EPUB format (:command:`make epub`). +PDF format (:command:`make pdf`) and EPUB format (:command:`make epub`). .. _Sphinx: http://www.sphinx-doc.org/ .. _reStructuredText: http://docutils.sourceforge.net/rst.html diff --git a/gcc/doc/install/final-installation.rst b/gcc/doc/install/final-installation.rst index ff39d441776..519987c7006 100644 --- a/gcc/doc/install/final-installation.rst +++ b/gcc/doc/install/final-installation.rst @@ -117,8 +117,8 @@ gcc@gcc.gnu.org detailing how the information should be changed. If you find a bug, please report it following the `bug reporting guidelines <https://gcc.gnu.org/bugs/>`_. -If you want to print the GCC manuals, do :samp:`cd {objdir}; make -latexpdf`. You will need to have Sphinx (version at least |needs_sphinx|) +If you want to print the GCC manuals, do :samp:`cd {objdir}; make pdf` +You will need to have Sphinx (version at least |needs_sphinx|) and XeLaTex installed. You can also `buy printed manuals from the Free Software Foundation <https://shop.fsf.org/>`_, though such manuals may not be for the most diff --git a/gcc/doc/install/prerequisites.rst b/gcc/doc/install/prerequisites.rst index 772012bdfd2..997bab08f50 100644 --- a/gcc/doc/install/prerequisites.rst +++ b/gcc/doc/install/prerequisites.rst @@ -267,7 +267,7 @@ Sphinx version |needs_sphinx| (or later) Necessary to build HTML, PDF or EPUB documentation. See more in :ref:`gccint:building_documentation`. - Necessary for running :command:`make html` or :command:`make latexpdf` to + Necessary for running :command:`make html` or :command:`make pdf` to create printable documentation in HTML or PDF format. Necessary to build GCC documentation during development because the diff --git a/gcc/go/doc/invoking-gccgo.rst b/gcc/go/doc/invoking-gccgo.rst index df63fc813c5..635312a45e3 100644 --- a/gcc/go/doc/invoking-gccgo.rst +++ b/gcc/go/doc/invoking-gccgo.rst @@ -211,4 +211,4 @@ Options .. only:: man - .. include:: copyright.rst + .. include:: copyright.rst \ No newline at end of file
reply other threads:[~2022-03-15 14:25 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20220315142516.0681F3858D20@sourceware.org \ --to=marxin@gcc.gnu.org \ --cc=gcc-cvs@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).