From owner-freebsd-ports  Wed Feb 26 10:44:51 1997
Return-Path: <owner-ports>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id KAA24900
          for ports-outgoing; Wed, 26 Feb 1997 10:44:51 -0800 (PST)
Received: from rover.village.org (rover.village.org [204.144.255.49])
          by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id KAA24893
          for <freebsd-ports@freebsd.org>; Wed, 26 Feb 1997 10:44:48 -0800 (PST)
Received: from rover.village.org [127.0.0.1] 
	by rover.village.org with esmtp (Exim 0.56 #1)
	id E0vzoKJ-0000h5-00; Wed, 26 Feb 1997 11:43:39 -0700
To: Adam David <adam@veda.is>
Subject: Re: make -k oddities 
Cc: asami@vader.cs.berkeley.edu (Satoshi Asami), freebsd-ports@freebsd.org
In-reply-to: Your message of "Wed, 26 Feb 1997 08:18:18 GMT."
		<199702260818.IAA08085@veda.is> 
References: <199702260818.IAA08085@veda.is>  
Date: Wed, 26 Feb 1997 11:43:39 -0700
From: Warner Losh <imp@village.org>
Message-Id: <E0vzoKJ-0000h5-00@rover.village.org>
Sender: owner-ports@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

In message <199702260818.IAA08085@veda.is> Adam David writes:
: Fundamental command paradigm
: 
: user: do this
: unix: (ok)
: 
: :) silence is golden :)

Yes, but this is currently broken.  make -k says not to build things
that depend on those things that caused the error:
     -k      Continue processing after errors are encountered, but only on
             those targets that do not depend on the target whose creation
             caused the error.
which implies that if you do a make -k as a submake, it should return
an error if anything it ran caused an error (excluding those things
explicitly ignored).

Warner