From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 3589 invoked by alias); 2 Feb 2015 17:53:23 -0000 Mailing-List: contact jit-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Post: List-Help: List-Subscribe: Sender: jit-owner@gcc.gnu.org Received: (qmail 3534 invoked by uid 89); 2 Feb 2015 17:53:23 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Checked: by ClamAV 0.98.5 on sourceware.org X-Virus-Found: No X-Spam-SWARE-Status: No, score=-1.7 required=5.0 tests=AWL,BAYES_00,SPF_PASS autolearn=ham version=3.3.2 X-Spam-Status: No, score=-1.7 required=5.0 tests=AWL,BAYES_00,SPF_PASS autolearn=ham version=3.3.2 X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on sourceware.org X-Spam-Level: X-Spam-User: qpsmtpd, 2 recipients X-HELO: ainaz.pair.com Date: Thu, 01 Jan 2015 00:00:00 -0000 From: Gerald Pfeifer To: David Malcolm cc: Jeff Law , jit@gcc.gnu.org, gcc-patches@gcc.gnu.org Subject: Re: [PING, www] Re: [PATCH] update_web_docs_svn: support the JIT docs (PR jit/64257) In-Reply-To: <1422895170.29180.74.camel@surprise> Message-ID: References: <1422053051-11954-1-git-send-email-dmalcolm@redhat.com> <1422290574.1463.38.camel@surprise> <54C6BDCC.60206@redhat.com> <1422317687.1463.41.camel@surprise> <1422895170.29180.74.camel@surprise> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII X-SW-Source: 2015-q1/txt/msg00055.txt.bz2 Hi David, On Monday 2015-02-02 11:39, David Malcolm wrote: >>>> * update_web_docs_svn: Don't delete gcc/jit/docs or >>>> gcc/jit/jit-common.h, gcc/jit/notes.txt. Special case the >>>> building of the jit docs (using sphinx-build). Special case >>>> copying them up. >> I've committed this to trunk as r220149. >> >> Does this automatically get propagated to the machine that builds the >> website (and thus would be run next time the relevant cronjob runs)? I looked into this, and it does not get propagated automatically, so I did it manually (svn up at the proper location). >> Or does someone need to do additional work for this to "go live"? (if >> nothing else, the machine needs to have sphinx-build in its $PATH, as >> noted in the patch). > I'm hoping to have the jit docs on the gcc website. I guess we'll be testing the error handling behavior of your new code :-), since indeed sphinx-build is not in the standard $PATH. Do you know where it can be found on this machine? > Presumably, some machine needs to have the relevant sphinx packaged > installed (if that's OK [1]), and perhaps the update to the > update_web_docs_svn script needs to make it onto that machine? > > Or is this more appropriate for the "overseers" list? Yes, please direct the request for sphinx to overseers. (In parallel, if you can refine how the script behaves when sphinx is not present, that might be a good idea, too.) Gerald