From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jonathan Corbet Subject: Re: [PATCH 1/2] doc/sphinx: Enable keep_warnings Date: Tue, 19 Jul 2016 16:23:12 -0600 Message-ID: <20160719162312.692230e7@lwn.net> References: <1468928575-11309-1-git-send-email-daniel.vetter@ffwll.ch> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 8bit Return-path: In-Reply-To: <1468928575-11309-1-git-send-email-daniel.vetter@ffwll.ch> Sender: linux-doc-owner@vger.kernel.org To: Daniel Vetter Cc: DRI Development , Intel Graphics Development , Markus Heiser , linux-doc@vger.kernel.org, Daniel Vetter List-Id: intel-gfx@lists.freedesktop.org On Tue, 19 Jul 2016 13:42:54 +0200 Daniel Vetter wrote: > Unfortunately warnings generated after parsing in sphinx can end up > with entirely bogus files and line numbers as sources. Strangely for > outright errors this is not a problem. Trying to convert warnings to > errors also doesn't fix it. > > The only way to get useful output out of sphinx to be able to root > cause the error seems to be enabling keep_warnings, which inserts > a System Message into the actual output. Not pretty at all, but I > don't really want to fix up core rst/sphinx code, and this gets the job > done meanwhile. I'll go ahead and apply this. It *would* be nice, someday, to figure out how to get proper info out for warnings directly, but until somebody gets there... Thanks, jon