From owner-freebsd-ports Wed Feb 26 10:38:28 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id KAA24389 for ports-outgoing; Wed, 26 Feb 1997 10:38:28 -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 KAA24379 for ; Wed, 26 Feb 1997 10:38:22 -0800 (PST) Received: from rover.village.org [127.0.0.1] by rover.village.org with esmtp (Exim 0.56 #1) id E0vzoEj-0000g9-00; Wed, 26 Feb 1997 11:37:53 -0700 To: Adam David Subject: Re: make -k oddities Cc: freebsd-ports@freebsd.org In-reply-to: Your message of "Wed, 26 Feb 1997 04:32:33 GMT." <199702260432.EAA07601@veda.is> References: <199702260432.EAA07601@veda.is> Date: Wed, 26 Feb 1997 11:37:53 -0700 From: Warner Losh Message-Id: Sender: owner-ports@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In message <199702260432.EAA07601@veda.is> Adam David writes: : >When I do a make -k for a port that I don't have (and can't get) the : >dist file for, then it will try to fetch and fail. Once it fails it : >will then try to patch, which it shouldn't do. : : make -k means "ignore error return from command" but bsd.port.mk uses the : error return to bail out at that point. Not quiet. make -i means "ignore error return from command" but -k means this with the restriction that nothing that depends on those things returning an error should be built. No fetch should imply no build, but doesn't. : >I've also seen weird things where sometimes it would fetch things : >twice, mysteriously hang when failing back to ftp.freebsd.org (but : >only sometimes, and sometimes after < 64k was trasnferred) and a few : >other sh related oddities. : : If the network connection breaks during fetch, the next site on the list is : tried. I have sometimes seen fetch fail on the last byte of the file. This is more of a hang with OpenBSD's ftp. For some reason, it hangs after about 64k when talking to freefall for reasons unknown. Warner