From: "Martin Liška" <mliska@suse.cz>
To: Joseph Myers <joseph@codesourcery.com>
Cc: Xi Ruoyao <xry111@linuxfromscratch.org>,
Sandra Loosemore <sandra@codesourcery.com>,
GCC Patches <gcc-patches@gcc.gnu.org>,
GCC Development <gcc@gcc.gnu.org>
Subject: Re: Announcement: Porting the Docs to Sphinx - 9. November 2022
Date: Thu, 10 Nov 2022 14:05:15 +0100 [thread overview]
Message-ID: <410c3aae-cf26-6e1c-3a8c-3c9cdafe61cf@suse.cz> (raw)
In-Reply-To: <e6cf5399-f85e-a979-a94e-d0649b612d8b@codesourcery.com>
On 11/9/22 18:14, Joseph Myers wrote:
> On Wed, 9 Nov 2022, Martin Liška wrote:
>
>> 1) not synchronized content among lib*/Makefile.in and lib*/Makefile.am.
>> Apparently, I modified the generated Makefile.in file with the rules like:
>>
>> doc/info/texinfo/libitm.info: $(SPHINX_FILES)
>> + if [ x$(HAS_SPHINX_BUILD) = xhas-sphinx-build ]; then \
>> make -C $(srcdir)/../doc info SOURCEDIR=$(abs_srcdir)/doc BUILDDIR=$(abs_doc_builddir)/info SPHINXBUILD=$(SPHINX_BUILD); \
>> else true; fi
>>
>> Can you please modify Makefile.am in the corresponding manner and re-generate Makefile.in?
>
> I think someone else had best look at this.
All right, I've got a patch candidate for it, so I'll be hopefully able to manage.
>
>> 2) Adding proper support --enable-generated-files-in-srcdir in gcc_release:
>
> It looks like all the GENINSRC rules / conditionals are still present.
> So maybe there are details where the paths are wrong, or where fixes are
> needed to ensure the files get installed from the source directory when
> available in the source directory but not available in the build directory
> because Sphinx isn't available, but much of the code for the feature is
> still there.
I can investigate then. Is the option --enable-generated-files-in-srcdir suppose
to be used when building from a release tarball (that includes man/info in src),
or to create such a source tarball?
Cheers,
Martin
next prev parent reply other threads:[~2022-11-10 13:05 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-31 14:06 Porting the Docs to Sphinx - project status Martin Liška
2022-02-04 13:40 ` Matthias Klose
2022-03-08 15:59 ` Martin Liška
2022-08-02 12:48 ` Martin Liška
2022-10-17 13:28 ` Announcement: Porting the Docs to Sphinx - 9. November 2022 Martin Liška
2022-10-17 14:16 ` Paul Iannetta
2022-10-19 7:24 ` Martin Liška
2022-10-19 8:13 ` Paul Iannetta
2022-10-19 9:22 ` Martin Liška
2022-10-19 16:42 ` Joseph Myers
2022-10-20 11:13 ` Martin Liška
2022-10-17 22:26 ` Sandra Loosemore
2022-10-19 11:09 ` Martin Liška
2022-10-19 12:45 ` Martin Liška
2022-10-19 16:30 ` Sandra Loosemore
2022-10-20 11:26 ` Martin Liška
2022-10-20 2:26 ` Xi Ruoyao
2022-10-20 11:27 ` Martin Liška
2022-10-20 11:49 ` Xi Ruoyao
2022-10-20 11:53 ` Martin Liška
2022-10-20 11:55 ` Xi Ruoyao
2022-10-20 12:26 ` Martin Liška
2022-10-20 15:35 ` Joseph Myers
2022-10-20 15:50 ` Martin Liška
2022-10-20 16:43 ` Joseph Myers
2022-10-20 16:47 ` Jakub Jelinek
2022-11-08 13:55 ` Announcement: Porting the Docs to Sphinx - tomorrow Martin Liška
2022-11-08 18:44 ` Sam James
2022-11-09 0:00 ` Joseph Myers
2022-11-09 0:06 ` Sam James
2022-11-09 7:49 ` Richard Biener
2022-11-09 10:18 ` Mark Wielaard
2022-11-09 17:11 ` Joseph Myers
2022-11-09 17:16 ` Richard Biener
2022-11-11 20:52 ` Gerald Pfeifer
2022-11-11 21:10 ` Sandra Loosemore
2022-11-13 15:44 ` Martin Liška
2022-11-09 14:45 ` Announcement: Porting the Docs to Sphinx - 9. November 2022 Martin Liška
2022-11-09 17:14 ` Joseph Myers
2022-11-10 13:05 ` Martin Liška [this message]
2022-11-10 13:50 ` Richard Biener
2022-11-11 23:05 ` David Malcolm
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=410c3aae-cf26-6e1c-3a8c-3c9cdafe61cf@suse.cz \
--to=mliska@suse.cz \
--cc=gcc-patches@gcc.gnu.org \
--cc=gcc@gcc.gnu.org \
--cc=joseph@codesourcery.com \
--cc=sandra@codesourcery.com \
--cc=xry111@linuxfromscratch.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).