Date: Thu, 19 Aug 2004 14:05:26 -0500 From: Stephen Hocking <shocking@houston.rr.com> To: Doug White <dwhite@gumbysoft.com> Cc: current@freebsd.org Subject: Re: Persisten buildworld errors Message-ID: <200408191905.i7JJ5Q5O003724@boggle.craftncomp.com> In-Reply-To: Your message of "Thu, 19 Aug 2004 11:44:20 PDT." <20040819114350.I62982@carver.gumbysoft.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> > > You can try doing a 'make includes' to try to overwirte whatever busted
> > > include files you have, but it might not fix things. You may want to grab
> > > a snapshot disc and "upgrade" to it.
> > >
> > Please don't suggest people to run "make includes". This will likely
> > break upgrades from older systems because headers (most noticeble one
> > is /usr/include/osreldate.h) will not match the installed world, and
> > you will fool your buildworld into thinking it's running on a more
> > current system than you actually have.
>
> Yeah I know make includes is evil, but this installation is obviously
> missing pieces, and its a last-ditch effort before regressing to a
> snapshot.
>
> Unless you have a better idea :)
>
I had gotten the source tree off ctm-cvs., which suggests that the cvs tree
that the ctm chunks are made from is incomplete. I know my source tree was up
to date with regards to it, which is why I was asking. How are people with
working build trees getting their sources?
Stephen
--
"If any question why we died
Tell them, because our fathers lied."
- Rudyard Kipling.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200408191905.i7JJ5Q5O003724>