Subject: Re: WARNING: -current toplevel build process changing!
To: None <firstname.lastname@example.org>
From: Greg A. Woods <email@example.com>
Date: 06/02/2001 02:54:24
[ On Friday, June 1, 2001 at 20:33:44 (-0400), Todd Vierling wrote: ]
> Subject: Re: WARNING: -current toplevel build process changing!
> Because the top level make needs to work on *vendor* makes, which may not be
> bmake, and thus cannot read /etc/mk.conf. The bootstrap harness builds
> bmake from the source tree in use, and needs to put it in TOOLDIR, which has
> to be defined *BEFORE* bmake is run.
Ah, of course. That was going to be my first question too, but of
course I hadn't thought it all the way through yet....
Obviously in that case it can also be supplied on the command-line. I
know of no (half-way modern) make that won't set variables that way.
> Now, I can probably put in some kind of hook to try to pry this out of
> mk.conf if the native system make is bmake. I'll look into this.
That would be most useful! (indeed my first reaction was that I'd
already be running bmake! ;-)
Greg A. Woods
+1 416 218-0098 VE3TCP <firstname.lastname@example.org> <email@example.com>
Planix, Inc. <firstname.lastname@example.org>; Secrets of the Weird <email@example.com>