Date: Wed, 22 Jul 1998 18:38:43 +0100 From: Paul Richards <paul@originative.co.uk> To: "'John Birrell'" <jb@cimlogic.com.au> Cc: current@FreeBSD.ORG Subject: RE: Does building current on 2.2.x still work? Message-ID: <E40CBF0361C7D111914000C0F0303D10866E@OCTOPUS>
next in thread | raw e-mail | index | archive | help
> -----Original Message----- > From: John Birrell [mailto:jb@cimlogic.com.au] > Sent: Wednesday, July 22, 1998 11:11 AM > To: paul@originative.co.uk > Cc: jb@cimlogic.com.au; dwhite@resnet.uoregon.edu; > nrice@emu.sourcee.com; imp@village.org; current@FreeBSD.ORG > Subject: Re: Does building current on 2.2.x still work? > > > Paul Richards wrote: > > Would it make sense to install the new mk files during the bootstrap > > target. The original idea I had for the bootstrap target was to deal > > with precisely these things, carry out steps required to > bootstrap from > > the previously released version to current. > > The issue here is that you can't necessarily parse the top > level makefile > without consistent .mk includes, so your bootstrap target won't be > guaranteed of working. And a buildworld is not supposed to clobber > things on the host system, so you have to live with old installed .mk > files. Ahh, good point. > The answer is: don't use them. Except for parsing the top > level makefile, > the current build system doesn't use the installed .mk files. When you > specify the -m argument on the command line, you get a > consistent build. > W^5 (Which Was What We Wanted). Hmm, we could wrapper the Makefile with a shell script for doing builds. This is attractive in that it isolates the build process from the action that makes it happen. This may just move the dependancy but I think isolation would be much easier to achieve than with the make environment since the shell mechanism virtually never changes whereas the make environement quite often does. If we created a buildworld command script then when a developer knows that a change is going to require something extra to be done they can update the buildworld script. Bootstrap problems like this have cropped up throughout FreeBSD's history and the problem always tends to be that people just forget what the extra steps are even though they've been told. People are creatures of habit, if we habitualise them to use a 'buildworld' script then we can isolate them from the changes. I find myself typing make world sometimes and hoping for the best because I've remembered that something needed to be done but not where I saved that important email that told me what :-) Paul Richards Ph.D. Originative Solutions Ltd To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?E40CBF0361C7D111914000C0F0303D10866E>