Date: Mon, 24 Mar 2008 18:10:24 +0000 (GMT) From: Robert Watson <rwatson@FreeBSD.org> To: David Wolfskill <david@catwhisker.org> Cc: Chuck Robey <chuckr@chuckr.org>, freebsd-current@freebsd.org Subject: Re: patching Message-ID: <20080324180925.X12107@fledge.watson.org> In-Reply-To: <20080324174912.GM75023@bunrab.catwhisker.org> References: <47E55BD0.2000101@chuckr.org> <20080324164814.GA86990@dragon.NUXI.org> <47E7E283.5070406@chuckr.org> <20080324174912.GM75023@bunrab.catwhisker.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, 24 Mar 2008, David Wolfskill wrote:
> On Mon, Mar 24, 2008 at 01:18:59PM -0400, Chuck Robey wrote:
>> ...
>>> In otherwords, you have stale files in ${DESTDIR}/usr/include.
>>
>> Thanks, David, I'd found it a couple days ago, actually it was pointed directly
>> to in an earlier email. I had somehow pulled a really old copy of tablet.h from
>> my cvs archive onto my system....
>
> Something I've been doing for a while to avoid that is to augment the steps
> listed in src/UPDATING by prefixing the "make installworld" with
>
> rm -fr /usr/include.old && mv /usr/include{,.old}
>
> so once "make installworld" has completed, /usr/include is fresh.
>
> I have had very few breaks -- even in CURRENT -- over the years since
> adopting the approach. (And I generally track CURRENT daily.)
>
> Note that the approach is not appropriate for a machine that has
> /usr/include updated outside of the "make installworld" process -- but my
> machines don't have that issue. (Still, note that I "move aside" the old
> /usr/include, just in case....)
buildworld instructions generally also seem to exclude "rm -Rf
/usr/obj/whatever", or some make clean variation, which is, once in a while,
required to get a successful build.
Robert N M Watson
Computer Laboratory
University of Cambridge
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20080324180925.X12107>