Subject: Re: Updating current in the wrong order after the make change.
To: Richard Earnshaw <firstname.lastname@example.org>
From: Jim Wise <email@example.com>
Date: 01/16/2001 14:10:16
-----BEGIN PGP SIGNED MESSAGE-----
On Tue, 16 Jan 2001, Richard Earnshaw wrote:
>> a "commands()" command was added to make's syntax a few days ago.
>> what you need to do is update your make before you install the new .mk
>> files. here's what i'd do:
>> # cd /usr/share/mk
>> # cvs -d :pserver:firstname.lastname@example.org:/cvsroot co -p -r1.126 sharesrc/share/mk/bsd.prog.mk > bsd.prog.mk
>> # cd /usr/src/usr.bin/make
>> # make
>> # make install
>> assuming, of course, that your source tree is in sync and that's the
>> only problem. :)
>Of course, one could argue that it should always be possible to rebuild
>make even in these circumstances. That is, /usr/src/usr.bin/make/Makefile
>should not pull in any makefile fragments, or there should be an alternate
>makefile in that directory that doesn't rely on /usr/share/mk/*.
Right. Naive little old me thought `well, why can't I use "make -f
Makefile.boot" to get out of this mess, that's what it's for, right?'
But apparently that's not what it's for -- unless you're on a sun.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.4 (NetBSD)
Comment: For info see http://www.gnupg.org
-----END PGP SIGNATURE-----