Date: Tue, 25 Feb 2003 16:09:38 -0800 From: Kris Kennaway <kris@obsecurity.org> To: Edwin Groothuis <edwin@mavetju.org> Cc: Kris Kennaway <kris@FreeBSD.ORG>, ports@FreeBSD.ORG Subject: Re: INDEX build failed Message-ID: <20030226000938.GB80368@rot13.obsecurity.org> In-Reply-To: <20030225231642.GN50581@k7.mavetju> References: <200302252310.h1PNAP7a023317@8ball.rtp.FreeBSD.Org> <20030225231642.GN50581@k7.mavetju>
next in thread | previous in thread | raw e-mail | index | archive | help
--XF85m9dhOBO43t/C
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
On Wed, Feb 26, 2003 at 10:16:42AM +1100, Edwin Groothuis wrote:
> On Tue, Feb 25, 2003 at 06:10:25PM -0500, Kris Kennaway wrote:
> > INDEX build failed with errors:
> > /nonexistentlocal: not found
> > "Makefile", line 29: warning: "/nonexistentlocal" returned non-zero sta=
tus
>=20
> You really should put more information than this in it if you want
> to make it a usefull failure report.
This is just the output of 'make index': it doesn't produce any more
information than this. Making 'make index' more descriptive in its
failure messages would be a very useful project for someone to take
on. If you have other suggestions for improving the emails, then
please let me know (I will commit the script to Tools/ soon).
In general you can look at the first failure email when the problem
occurred, because the commit that broke it will be one of those listed
in the 'cvs update' output included in the mail. In this case it's
not that simple because there were about a dozen separate errors
committed in a short time period, all of which individually caused
INDEX builds to break.
Yes, it's a pain in the butt to fix broken INDEXes, which is why I get
so annoyed when committers break it and then leave it to someone else
to fix (usually me).
This particular failure can likely be tracked down by doing a 'make
describe' with a bogus LOCALBASE, X11BASE and PREFIX (cf the 'make
index' target), and looking where the error is. From looking at the
error message, I expect it's another one of the
FOO!=3D${LOCALBASE}
bugs you committed.
Kris
--XF85m9dhOBO43t/C
Content-Type: application/pgp-signature
Content-Disposition: inline
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (FreeBSD)
iD8DBQE+XAXBWry0BWjoQKURAlUmAKC3zfDO/hJS+HzO7ro31ZnS0RPqjACgouor
ylIKc0VexhUpSLfzI+zLRvc=
=TClx
-----END PGP SIGNATURE-----
--XF85m9dhOBO43t/C--
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-ports" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030226000938.GB80368>