public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Sandra Loosemore <sandra@codesourcery.com>
To: "Gerald Pfeifer" <gerald@pfeifer.com>, "Martin Liška" <mliska@suse.cz>
Cc: Jakub Jelinek <jakub@redhat.com>,
	Joseph Myers <joseph@codesourcery.com>,
	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 - tomorrow
Date: Fri, 11 Nov 2022 14:10:08 -0700	[thread overview]
Message-ID: <d7296397-1d66-80a1-9aa9-0d648ed2767d@codesourcery.com> (raw)
In-Reply-To: <aea319c9-990e-a645-3d48-9dc8473e36a2@pfeifer.com>

On 11/11/22 13:52, Gerald Pfeifer wrote:
> On Tue, 8 Nov 2022, Martin Liška wrote:
>> After the migration, people should be able to build (and install) GCC
>> even if they miss Sphinx (similar happens now if you miss makeinfo).
> 
> My nightly *install* (not build) on amd64-unknown-freebsd12.2 broke
> (from what I can tell due to this - it's been working fine most of
> the last several 1000 days):
> 
>    if [ -f doc/g++.1 ]; then rm -f /home/gerald/gcc-ref12-amd64/share/man/man1/g++.1; /usr/bin/install -c -m 644 doc/g++.1 /home/gerald/gcc-ref12-amd64/share/man/man1/g++.1; chmod a-x /home/gerald/gcc-ref12-amd64/share/man/man1/g++.1; fimake -C /scratch/tmp/gerald/GCC-HEAD/gcc/../doc man SOURCEDIR=/scratch/tmp/gerald/GCC-HEAD/gcc/fortran/doc/gfortran BUILDDIR=/scratch/tmp/gerald/OBJ-1111-0954/gcc/doc/gfortran/man SPHINXBUILD=
>    make[3]: make[3]: don't know how to make w. Stop
>    make[3]: stopped in /scratch/tmp/gerald/GCC-HEAD/doc
>    gmake[2]: *** [/scratch/tmp/gerald/GCC-HEAD/gcc/fortran/Make-lang.in:164: doc/gfortran/man/man/gfortran.1] Error 2
>    gmake[2]: Leaving directory '/scratch/tmp/gerald/OBJ-1111-0954/gcc'
>    gmake[1]: *** [Makefile:5310: install-strip-gcc] Error 2
>    gmake[1]: Leaving directory '/scratch/tmp/gerald/OBJ-1111-0954'
>    gmake: *** [Makefile:2734: install-strip] Error 2
> 
> (This appears to be the case with "make -j1 install-strip". Not sure where
> that "w" target is coming from?)

I've seen something similar:  "make install" seems to be passing an 
empty SPHINXBUILD= option to the docs Makefile which is not equipped to 
handle that.  I know the fix is to get a recent-enough version of Sphinx 
installed (and I'm going to work on that over the weekend), but it ought 
to fail more gracefully, or not try to install docs that cannot be built 
without Sphinx.

-Sandra


  reply	other threads:[~2022-11-11 21:10 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 [this message]
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
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=d7296397-1d66-80a1-9aa9-0d648ed2767d@codesourcery.com \
    --to=sandra@codesourcery.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=gcc@gcc.gnu.org \
    --cc=gerald@pfeifer.com \
    --cc=jakub@redhat.com \
    --cc=joseph@codesourcery.com \
    --cc=mliska@suse.cz \
    --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).