From owner-freebsd-current  Thu Jul 16 20:20:24 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id UAA11656
          for freebsd-current-outgoing; Thu, 16 Jul 1998 20:20:24 -0700 (PDT)
          (envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.15.68.22])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA11649
          for <current@FreeBSD.ORG>; Thu, 16 Jul 1998 20:20:21 -0700 (PDT)
          (envelope-from bde@godzilla.zeta.org.au)
Received: (from bde@localhost)
	by godzilla.zeta.org.au (8.8.7/8.8.7) id NAA00328;
	Fri, 17 Jul 1998 13:19:59 +1000
Date: Fri, 17 Jul 1998 13:19:59 +1000
From: Bruce Evans <bde@zeta.org.au>
Message-Id: <199807170319.NAA00328@godzilla.zeta.org.au>
To: current@FreeBSD.ORG, dag-erli@ifi.uio.no
Subject: Re: make installworld -j8
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

>make can't execute /bin/sh to install the sh(1) man pages because
>/bin/sh is in the process of being clobbered by a sibling make
>process. Shouldn't make installworld use the freshly compiled sh from
>/usr/obj rather than /bin/sh?

You mean `make -jN installworld'.  `make installworld' doesn't have
this problem, since it doesn't install things concurrently.
`make -jN world' doesn't have this problem, since it uses
`${MAKE} -B installworld' internally.

All the world-related targets attempt to use ${WORLDTMP}/bin/sh
after it is created, but many programs have /bin/sh hard-coded.

Bruce

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message