From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-bugzilla@gcc.gnu.org>
Received: by sourceware.org (Postfix, from userid 48)
	id 0C5B33858C98; Wed, 27 Mar 2024 15:47:46 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 0C5B33858C98
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1711554466;
	bh=ySc0+eiKdjgADLJAKPlZpXHhZrOP4VBZPJk8ya8qC/A=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=QMNSoWyxq/RIppeaOvMgIh0wIXYIA/3bIHeALFOjwofdeO1lwhMR0OFQ4sd9GoFaQ
	 NnF8w3fUYj3tpcDkalK7wEJsxgkjLK+otCTlw3KimM8+H4vS1LpYOTHbJvpzTM1Pwl
	 jvqfBc1C2dI7i3YCFrMIxF12G7l4Db+9BnvoJSsU=
From: "egallager at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug jit/102824] building pdf/dvi documentation for libgccjit fails
Date: Wed, 27 Mar 2024 15:47:45 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: jit
X-Bugzilla-Version: 12.0
X-Bugzilla-Keywords: documentation
X-Bugzilla-Severity: normal
X-Bugzilla-Who: egallager at gcc dot gnu.org
X-Bugzilla-Status: WAITING
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: dmalcolm at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-102824-4-SccYq5YeEj@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-102824-4@http.gcc.gnu.org/bugzilla/>
References: <bug-102824-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
List-Id: <gcc-bugs.sourceware.org>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D102824

--- Comment #13 from Eric Gallager <egallager at gcc dot gnu.org> ---
(In reply to Iain Sandoe from comment #12)
> what input is this waiting for at the moment?

>From checking the bug history, it looks like Martin Li=C5=A1ka was the one =
to put
this in the WAITING status, which came along with this comment:

(In reply to Martin Li=C5=A1ka from comment #7)
> Well, running 'make latexpdf' works if you jump into gcc/jit/docs folder.=
 Do
> I miss something?

...which I thought we'd answered, but to make it a bit more clear: we shoul=
dn't
have to do that to get the jit docs to build properly. They should build
properly when doing `make dvi` and/or `make pdf` from the top-level, rather
than requiring their own special procedures.=