From owner-freebsd-current Thu Apr 19 7:55:51 2001 Delivered-To: freebsd-current@freebsd.org Received: from whale.sunbay.crimea.ua (whale.sunbay.crimea.ua [212.110.138.65]) by hub.freebsd.org (Postfix) with ESMTP id 6FE1A37B422 for ; Thu, 19 Apr 2001 07:55:43 -0700 (PDT) (envelope-from ru@whale.sunbay.crimea.ua) Received: (from ru@localhost) by whale.sunbay.crimea.ua (8.11.2/8.11.2) id f3JErr921062; Thu, 19 Apr 2001 17:53:53 +0300 (EEST) (envelope-from ru) Date: Thu, 19 Apr 2001 17:53:53 +0300 From: Ruslan Ermilov To: Bruce Evans Cc: Makoto MATSUSHITA , current@FreeBSD.ORG Subject: Re: groff breaks "make -j N buildworld" Message-ID: <20010419175353.A13567@sunbay.com> Mail-Followup-To: Bruce Evans , Makoto MATSUSHITA , current@FreeBSD.ORG References: <20010419171841Z.matusita@jp.FreeBSD.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from bde@zeta.org.au on Thu, Apr 19, 2001 at 11:12:24PM +1000 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Apr 19, 2001 at 11:12:24PM +1000, Bruce Evans wrote: [...] > > IIRC, it is assumed that "make -jX install (where X > 1)" _doesn't_ work. > > I've heard why, but I've forgotten :-) > > Right. One case where it doesn't work is installing /bin/sh with the > default install flags. /bin/sh gets clobbered, so anything that attempts > to use it concurrently doesn't work. In particular, a concurrent > sub-make may fail. This problem is avoided for some very important > install targets like ld.so by adding -C to INSTALLFLAGS to give an > atomic installation. Atomic installation (but not -C) should be the > default. > This one seems like an easy task, and this is suspicious... How about the attached patch? I have tested it lightly, and haven't found any problems. Will the `make -j32 installworld' of -CURRENT be enough test to commit this and remove -B from Makefile.inc1? > Since make -jX install doesn't work, `make world' in /usr/src/Makefile > uses `${MAKE} -B installworld' to turn off any previous setting of -j. > If you make installworld directly, then then -B is not enforced, so > you must use it in the command line if you have a setting of -j in the > environment. > > ... back to `make all install'. If this works at all, then you can > only use it without -j, since the `install' part of it doesn't work > with -j. Separate steps are required to pass different flags to > make(1). > Is the atomic install the only known issue for not functional `make -jN install'? Cheers, -- Ruslan Ermilov Oracle Developer/DBA, ru@sunbay.com Sunbay Software AG, ru@FreeBSD.org FreeBSD committer, +380.652.512.251 Simferopol, Ukraine http://www.FreeBSD.org The Power To Serve http://www.oracle.com Enabling The Information Age To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message