On Fri, Apr 26, 2002 at 03:20:02PM -0400, Tom Rhodes wrote:
> On Fri, 26 Apr 2002 11:59:21 -0700
> Marcel Moolenaar <[EMAIL PROTECTED]> wrote:
> 
> > On Fri, Apr 26, 2002 at 09:26:34PM +0300, Ruslan Ermilov wrote:
> > 
> > > I.e., if you built world a month ago, and didn't touch /usr/src
> > > since, and /usr/obj has "buildworld" output for this /usr/src,
> > > and you have booted with this world, it should be okay to start
> > > building today's release.
> > 
> > I share my src tree, so I almost always have a /usr/src that's not
> > in sync with the /usr/obj for and on a particular machine.
> > 
> > What goes wrong if /usr/src and /usr/obj are out of sync?
> > 
> > -- 
> >  Marcel Moolenaar     USPA: A-39004          [EMAIL PROTECTED]
> > 
> 
> Correct me if i'm wrong, but last time my obj and src was different,
> and I tried a make installworld, the process returned errors of:
> 
> <filename> file not found
> 
> where filename was a missing file.  After a cvsup and a makebuildworld,
> make install world worked fine ;)
> 
> In other words, I think you will get those errors.
> 
That is the best scenario, but some of our share/mk targets are "broken"
in that they attempt to "build" things at "install" time if they are not
up-to-date.  For example, SCRIPTS and FILES stuff in bsd.prog.mk suffers
from this problem, and it can't be easily solved because we "abuse" the
dependencies to get the correct source paths.  I haven't (yet) found a
way to do it "the other way".

This is often reported on various mailing lists; the most frequent one
is about "expr not found" while attempting to build groff fonts at
"install" time.  I answered this question a few zillion times.  :-)


Cheers,
-- 
Ruslan Ermilov          Sysadmin and DBA,
[EMAIL PROTECTED]           Sunbay Software AG,
[EMAIL PROTECTED]          FreeBSD committer,
+380.652.512.251        Simferopol, Ukraine

http://www.FreeBSD.org  The Power To Serve
http://www.oracle.com   Enabling The Information Age

Attachment: msg37736/pgp00000.pgp
Description: PGP signature

Reply via email to