From owner-freebsd-hackers Tue Feb 24 20:51:19 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA29233 for freebsd-hackers-outgoing; Tue, 24 Feb 1998 20:51:19 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from ns.mt.sri.com (sri-gw.MT.net [206.127.105.141]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA29165 for ; Tue, 24 Feb 1998 20:50:34 -0800 (PST) (envelope-from nate@mt.sri.com) Received: from mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by ns.mt.sri.com (8.8.8/8.8.8) with SMTP id VAA04642; Tue, 24 Feb 1998 21:50:31 -0700 (MST) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id VAA13020; Tue, 24 Feb 1998 21:50:29 -0700 Date: Tue, 24 Feb 1998 21:50:29 -0700 Message-Id: <199802250450.VAA13020@mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Mike Smith Cc: hackers@FreeBSD.ORG Subject: Re: Odd(?) sh/make behaviour. In-Reply-To: <199802250423.UAA17980@dingo.cdrom.com> References: <199802250423.UAA17980@dingo.cdrom.com> X-Mailer: VM 6.29 under 19.15 XEmacs Lucid Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I'm looking at a Makefile that does: > > foo:: > (set -e; cd foo; unset BAR BAZ; ./something; make stuff) > > Now, if I walk up to sh and say 'set -e; unset FOO' where foo doesn't > exist, sh immediately exit. At this point, make throws in the towel. > > But GNU make doesn't, and for that matter, sh doesn't exit under GNU > make either, despite the 'set -e'. IMHO, under FreeBSD GNU make doesn't check for errors, and blindly continues on as if nothing bad has happened. This really *sucks*, since I've got a build environment from Solaris that only works with SysV make, so I use GNU make under FreeBSD and it dies in the middle of something but continues on (and keeps getting errors because previous dependencies weren't built). When I get back to the machine, I assume that the build work since the last part of the build doesn't happen to depend on anything that broke, so I don't see any errors and stupidly assume it actually worked and all heck breaks loose when I try to do something and it fails. :( It may be that our make is 'doing the right thing' in this case. Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message