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-v7)] sphinx: fix cross manual references Date: Thu, 28 Jul 2022 01:04:22 +0000 (GMT) [thread overview] Message-ID: <20220728010422.2CC4B3856DE4@sourceware.org> (raw) https://gcc.gnu.org/g:96f50242b64ebe446c507d3ecf2de6bf4a2ed480 commit 96f50242b64ebe446c507d3ecf2de6bf4a2ed480 Author: Martin Liska <mliska@suse.cz> Date: Thu Jul 28 02:09:54 2022 +0200 sphinx: fix cross manual references Diff: --- doc/baseconf.py | 1 - gcc/ada/doc/gnat_rm/index.rst | 3 ++- .../gcc/gcc-command-options/options-controlling-the-kind-of-output.rst | 2 +- .../references-for-other-languages.rst | 2 +- 4 files changed, 4 insertions(+), 4 deletions(-) diff --git a/doc/baseconf.py b/doc/baseconf.py index 1e212170c42..87cda64329b 100644 --- a/doc/baseconf.py +++ b/doc/baseconf.py @@ -131,7 +131,6 @@ man_pages = [] # FIXME: handle WARNINGs: unknown option issues and cross refs suppress_warnings = [ 'ref.option', - 'ref.ref' ] # Use xelatex by default diff --git a/gcc/ada/doc/gnat_rm/index.rst b/gcc/ada/doc/gnat_rm/index.rst index 6c2616a0f1c..372c2100e51 100644 --- a/gcc/ada/doc/gnat_rm/index.rst +++ b/gcc/ada/doc/gnat_rm/index.rst @@ -1,6 +1,7 @@ +.. _top: + GNAT Reference Manual ===================== - .. only:: not latex *GNAT, The GNU Ada Development Environment* diff --git a/gcc/doc/gcc/gcc-command-options/options-controlling-the-kind-of-output.rst b/gcc/doc/gcc/gcc-command-options/options-controlling-the-kind-of-output.rst index dab61402b45..798aadb32f0 100644 --- a/gcc/doc/gcc/gcc-command-options/options-controlling-the-kind-of-output.rst +++ b/gcc/doc/gcc/gcc-command-options/options-controlling-the-kind-of-output.rst @@ -704,7 +704,7 @@ one of the options :option:`-c`, :option:`-S`, or :option:`-E` to say where .. option:: -fdump-ada-spec[-slim] For C and C++ source and include files, generate corresponding Ada specs. - See :ref:`gnat_ugn:generating-ada-bindings-for-c-and-c++-headers`, which provides detailed documentation on this feature. + See :ref:`gnat_ugn:Generating_Ada_Bindings_for_C_and_C++_headers`, which provides detailed documentation on this feature. .. option:: -fada-spec-parent={unit} diff --git a/gcc/doc/gcc/language-standards-supported-by-gcc/references-for-other-languages.rst b/gcc/doc/gcc/language-standards-supported-by-gcc/references-for-other-languages.rst index c0434cb4357..fdb6c96358b 100644 --- a/gcc/doc/gcc/language-standards-supported-by-gcc/references-for-other-languages.rst +++ b/gcc/doc/gcc/language-standards-supported-by-gcc/references-for-other-languages.rst @@ -9,5 +9,5 @@ References for Other Languages See :ref:`gnat_rm:top`, for information on standard conformance and compatibility of the Ada compiler. -See :ref:`gfortran:standards`, for details +See :ref:`fortran:standards`, for details of standards supported by GNU Fortran. \ No newline at end of file
next reply other threads:[~2022-07-28 1:04 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-07-28 1:04 Martin Liska [this message] -- strict thread matches above, loose matches on Subject: below -- 2022-08-01 11:52 Martin Liska 2022-08-01 4:03 Martin Liska 2022-07-28 13:19 Martin Liska 2022-07-28 12:40 Martin Liska 2022-07-28 12:39 Martin Liska 2022-07-28 12:24 Martin Liska 2022-07-28 12:23 Martin Liska 2022-07-28 0:10 Martin Liska
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=20220728010422.2CC4B3856DE4@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).