Content-Type: text/plain; charset=UTF-8
Cc: Kevin Grittner <kevin.grittner@wicourts.gov>,
	Pg Docs <pgsql-docs@postgresql.org>
Subject: Re: Cannot build docs on Ubuntu 10.04?
From: Alvaro Herrera <alvherre@commandprompt.com>
To: Josh Berkus <josh@agliodbs.com>
In-reply-to: <4F0F540B.9060908@agliodbs.com>
References: <4F0F3CD7.1020905@agliodbs.com>
	<4F0EEB5E0200002500044738@gw.wicourts.gov>
	<4F0F426C.7060409@agliodbs.com>
	<1326402821-sup-6197@alvh.no-ip.org>
	<4F0F540B.9060908@agliodbs.com>
Date: Thu, 12 Jan 2012 19:01:33 -0300
Message-Id: <1326405509-sup-9740@alvh.no-ip.org>
User-Agent: Sup/git
Content-Transfer-Encoding: quoted-printable


Excerpts from Josh Berkus's message of jue ene 12 18:43:39 -0300 2012:
>=20
> > The warning about "unknown warning type" means you're using the wrong
> > tool to me.  My toolchain here uses "openjade" which is a fork of the
> > earlier jade (so install opensp as Kevin suggested, and rerun configu=
re
> > after that); my guess is that we're pretty much dependent on openjade
> > features that did not exist in plain jade.  Maybe we should just get =
rid
> > of our attempts to use the older tool.
>=20
> Yeah, the problem is that if you install just "openjade" on
> debian/ubuntu, it doesn't create the command "jade", which is what our
> make script is looking for.

BS.  You just neglected to rerun configure at that point.

# config/docbook.m4

# PGAC_PROG_JADE
# --------------
AC_DEFUN([PGAC_PROG_JADE],
[AC_CHECK_PROGS([JADE], [openjade jade])])


I think the main failure of the docs is to make it more prominent that
you need to rerun configure after you install stuff.

--=20
=C3=81lvaro Herrera <alvherre@commandprompt.com>
The PostgreSQL Company - Command Prompt, Inc.
PostgreSQL Replication, Consulting, Custom Development, 24x7 support