Date: Wed, 28 Feb 2007 12:47:07 +0300 From: Ruslan Ermilov <ru@FreeBSD.ORG> To: Nate Lawson <nate@root.org> Cc: cvs-src@FreeBSD.ORG, src-committers@FreeBSD.ORG, cvs-all@FreeBSD.ORG Subject: Re: cvs commit: src UPDATING Message-ID: <20070228094707.GA62675@rambler-co.ru> In-Reply-To: <45E4B16C.7030907@root.org> References: <200702192249.l1JMnhsL027828@repoman.freebsd.org> <20070226155240.GA57984@rambler-co.ru> <45E4B16C.7030907@root.org>
next in thread | previous in thread | raw e-mail | index | archive | help
--5vNYLRcllDrimb99
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
On Tue, Feb 27, 2007 at 02:32:12PM -0800, Nate Lawson wrote:
> I hadn't done anything with the system since about June 2006. I don't
> rule out the possibility that while trying to fix the buildworld problem
> that I copied in /usr/src/include to /usr/include, but I definitely
> didn't do it before the first buildworld failed there.
>=20
"cvs diff -D2006/06/01" in src/contrib/bsnmp" shows no changes
in gensnmptree, so something else was broken. The last time
gensnmptree needed to be bootstrapped was earlier in March:
1.545 (ru 31-Mar-06): .if ${BOOTSTRAPPING} < 700015
1.545 (ru 31-Mar-06): _gensnmptree=3D usr.sbin/bsnmpd/g=
ensnmpt
1.545 (ru 31-Mar-06): .endif
So I'm pretty sure it was your system that was broken, not the
build system.
> Is there any harm in leaving the message in UPDATING?
>=20
Yes, as it's misleading and confusing, and is questioning the
smartness of our build system. ;)
> It's just an FYI in case someone else sees the same problem.
> You can modify it to say
> this is likely pilot error if you want, but I think it's helpful to have
> it there since I saw a few similar reports on list archives with no
> response.
>=20
There could be a plenty of other build problems if the build
system is fooled about the currently running version of the
system. There were quite a few of similar reports in the
past when the problem was real and gensnmptree needed to be
bootstrapped. I suggest that you remove a note unless you
are willing and able to reproduce it by installing a June
snapshot and get the same build failure when trying to build
HEAD on it. My point is that if the bug is real, we need to
fix it, and not to hide from it by adding a note to UPDATING.
Cheers,
--=20
Ruslan Ermilov
ru@FreeBSD.org
FreeBSD committer
--5vNYLRcllDrimb99
Content-Type: application/pgp-signature
Content-Disposition: inline
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.2 (FreeBSD)
iD8DBQFF5U+bqRfpzJluFF4RAneIAJ47AEaUqbnrbVcShNd2oOy8jzRwvQCdGXG3
dvCjOZG8/elrNN3stjzUsSU=
=NV/R
-----END PGP SIGNATURE-----
--5vNYLRcllDrimb99--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20070228094707.GA62675>