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-final)] fixup! sphinx: copy files from texi2rst-generated repository
Date: Mon,  7 Nov 2022 12:42:21 +0000 (GMT)	[thread overview]
Message-ID: <20221107124229.13F713858CDB@sourceware.org> (raw)

https://gcc.gnu.org/g:3277b90e6509dd965518c202edba08e76f048844

commit 3277b90e6509dd965518c202edba08e76f048844
Author: Martin Liska <mliska@suse.cz>
Date:   Mon Nov 7 13:40:03 2022 +0100

    fixup! sphinx: copy files from texi2rst-generated repository

Diff:
---
 doc/requirements.txt                                                  | 3 +++
 .../the-gcc-subdirectory/building-documentation.rst                   | 4 ++--
 2 files changed, 5 insertions(+), 2 deletions(-)

diff --git a/doc/requirements.txt b/doc/requirements.txt
new file mode 100644
index 00000000000..f5558030ca8
--- /dev/null
+++ b/doc/requirements.txt
@@ -0,0 +1,3 @@
+Sphinx>=5.3
+furo
+sphinx_copybutton
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 8184dbc6042..468742c8582 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
@@ -42,7 +42,7 @@ or ``virtualenv``, depending on how your distribution packaged Python 3.
 
 Note the :file:`requirements.txt` file is placed in :rst:dir:`gcc/doc` folder and contains the following packages:
 
-.. literalinclude:: ../../../requirements.txt
+.. literalinclude:: ../../../../../doc/requirements.txt
   :caption: requirements.txt
 
 Then the virtualenv can be provided to the configure script :option:`install:--with-sphinx-build`
@@ -232,4 +232,4 @@ with miscellaneous documentation:
   .. todo:: why isn't this part of this manual or of the GCC Coding Conventions?
 
   .. todo:: document such files in subdirectories, at least :samp:`config`,
-    :samp:`c`, :samp:`cp`, :samp:`objc`, :samp:`testsuite`.
\ No newline at end of file
+    :samp:`c`, :samp:`cp`, :samp:`objc`, :samp:`testsuite`.

                 reply	other threads:[~2022-11-07 12:42 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=20221107124229.13F713858CDB@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: 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).