public inbox for jit@gcc.gnu.org
 help / color / mirror / Atom feed
From: Gerald Pfeifer <gerald@pfeifer.com>
To: David Malcolm <dmalcolm@redhat.com>
Cc: jit@gcc.gnu.org, gcc-patches@gcc.gnu.org, Jeff Law <law@redhat.com>
Subject: Re: [PATCH] More fixes for update_web_docs_svn for jit docs (PR jit/64257)
Date: Tue, 01 Jan 2019 00:00:00 -0000	[thread overview]
Message-ID: <alpine.LSU.2.21.1908050031430.26759@anthias.pfeifer.com> (raw)
In-Reply-To: <1423088766.29180.129.camel@surprise>

On Wed, 4 Feb 2015, David Malcolm wrote:
>> That was my plan, yes. :-)  I just did that and manually ran
>> the script, and it seems to work.
> Thank you!

>> Still, do you think you can add a bit of error handling such
>> that an issue like the one we had (cf. 
>> https://gcc.gnu.org/ml/gccadmin/2015-q1/msg00077.html ) does
>> not kill the entire script?  A bit of resilience would be good.
> Something like the attached?  (completely untested, sorry)

Yes.

Given that this was a while ago (ahem), I went ahead, created a
ChangeLog entry, committed the patch on your behalf, updated the
version on gcc.gnu.org, and did a test run there.

Gerald


2019-08-05  David Malcolm  <dmalcolm@redhat.com>

	* update_web_docs_svn: Proceed even if the invocation of
	sphinx fails.

Index: update_web_docs_svn
===================================================================
--- update_web_docs_svn	(revision 274098)
+++ update_web_docs_svn	(working copy)
@@ -190,7 +190,7 @@ done
 #   /usr/bin/sphinx-1.0-build
 # so we need to override SPHINXBUILD with this when invoking "make".
 pushd gcc/gcc/jit/docs
-make SPHINXBUILD=/usr/bin/sphinx-1.0-build html
+make SPHINXBUILD=/usr/bin/sphinx-1.0-build html || true
 popd
 cp -a gcc/gcc/jit/docs/_build/html jit
 mkdir -p $DOCSDIR/jit

  parent reply	other threads:[~2019-08-04 22:39 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-01  0:00 [PATCH] update_web_docs_svn: support the JIT " David Malcolm
2015-01-01  0:00 ` Gerald Pfeifer
2015-01-01  0:00   ` David Malcolm
2015-01-01  0:00     ` Jeff Law
2015-01-01  0:00       ` David Malcolm
2015-01-01  0:00         ` [PING, www] " David Malcolm
2015-01-01  0:00           ` Gerald Pfeifer
2015-01-01  0:00             ` [PATCH] More fixes for update_web_docs_svn for jit " David Malcolm
2015-01-01  0:00               ` Gerald Pfeifer
2015-01-01  0:00                 ` David Malcolm
2015-01-01  0:00                   ` Gerald Pfeifer
2015-01-01  0:00                     ` David Malcolm
2015-01-01  0:00                       ` [PATCH] maintainer-scripts: Fix 404s in "Show Source" in jit docs David Malcolm
2015-01-01  0:00                         ` Gerald Pfeifer
2015-01-01  0:00                       ` [PATCH] More fixes for update_web_docs_svn for jit docs (PR jit/64257) David Malcolm
2019-01-01  0:00                       ` Gerald Pfeifer [this message]
2015-01-01  0:00               ` Andrew Pinski
2015-01-01  0:00   ` [PATCH] update_web_docs_svn: support the JIT " Mike Stump

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=alpine.LSU.2.21.1908050031430.26759@anthias.pfeifer.com \
    --to=gerald@pfeifer.com \
    --cc=dmalcolm@redhat.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=jit@gcc.gnu.org \
    --cc=law@redhat.com \
    /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).