From owner-freebsd-hackers  Thu Jun 19 23:43:21 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.5/8.8.5) id XAA15673
          for hackers-outgoing; Thu, 19 Jun 1997 23:43:21 -0700 (PDT)
Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226])
          by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id XAA15668
          for <freebsd-hackers@FreeBSD.ORG>; Thu, 19 Jun 1997 23:43:19 -0700 (PDT)
Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.5/8.6.9) with ESMTP id XAA26362; Thu, 19 Jun 1997 23:41:50 -0700 (PDT)
To: tom@tomqnx.com (Tom Torrance at home)
cc: mike@sentex.net, freebsd-hackers@FreeBSD.ORG
Subject: Re: make world error in RELENG_2_2 
In-reply-to: Your message of "Fri, 20 Jun 1997 00:50:47 EDT."
             <m0wevep-000A41C@TomQNX.tomqnx.com> 
Date: Thu, 19 Jun 1997 23:41:49 -0700
Message-ID: <26359.866788909@time.cdrom.com>
From: "Jordan K. Hubbard" <jkh@time.cdrom.com>
Sender: owner-hackers@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

> I suspect that there IS some other problem, and it is/was with cvsup.
> I don't know why or how or if I contributed to it:-)

It's not a problem with cvsup.  It's a fundamental flaw in the model
of trying to "upgrade" a source tree by continually:

	a) Changing modified bits.
	b) Adding new ones.
	c) Not deleting the old ones.

It's (c) which is the killer since you will eventually confuse the
bezeesus out of the build system with old bits.  Do you have the
"delete" option turned on in your supfile?

					Jordan