From owner-freebsd-hackers@FreeBSD.ORG Tue Aug 31 06:37:23 2004 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6BBBF16A4CE; Tue, 31 Aug 2004 06:37:23 +0000 (GMT) Received: from cs1.cs.huji.ac.il (cs1.cs.huji.ac.il [132.65.16.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1CC3F43D5C; Tue, 31 Aug 2004 06:37:23 +0000 (GMT) (envelope-from alsbergt@cs.huji.ac.il) Received: from ludo.cs.huji.ac.il ([132.65.80.122]) by cs1.cs.huji.ac.il with esmtp id 1C22Gf-000K9M-9c; Tue, 31 Aug 2004 09:37:21 +0300 Received: from alsbergt by ludo.cs.huji.ac.il with local (Exim 4.34 (FreeBSD)) id 1C22Ge-000Kiq-Vk; Tue, 31 Aug 2004 09:37:20 +0300 Date: Tue, 31 Aug 2004 09:37:20 +0300 From: Tom Alsberg To: John Baldwin Message-ID: <20040831063720.GA79612@cs.huji.ac.il> Mail-Followup-To: Tom Alsberg , John Baldwin , FreeBSD Hackers List , Brooks Davis , Geert Hendrickx , simon@FreeBSD.org References: <20040810223606.GA75648@lori.mine.nu> <20040815165330.GA4726@odin.ac.hmc.edu> <20040830192722.GA29212@zoopee.org> <200408301656.19394.jhb@FreeBSD.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200408301656.19394.jhb@FreeBSD.org> X-Face: "5"j@Y1Peoz1; ftTv>\|['ox-csmV+:_RDNdi/2lSe2x?0:HVAeVW~ajwQ7RfDlcb^18eJ; t,O,s5-aNdU/DJ2E8h1s,..4}N9$27u`pWmH|; s!zlqqVwr9R^_ji=1\3}Z6gQBYyQ]{gd5-V8s^fYf{$V2*_&S>eA|SH@Y\hOVUjd[5eah{EO@gCr.ydSpJHJIU[QsH~bC?$C@O:SzF=CaUxp80-iknM(]q(W cc: simon@FreeBSD.org cc: Geert Hendrickx Subject: Re: make "quickworld"? (like in DragonFly) X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 31 Aug 2004 06:37:23 -0000 On Mon, Aug 30, 2004 at 04:56:19PM -0400, John Baldwin wrote: > > > So there's no good reason for a make to fail unless something very odd > > happened (with the timestamps, etc.) or something like this happens, > > it means some dependency is missing, or some script external to the > > Makefile did something wrong. > > That may be true for simple projects but this isn't a simple project. For > example, when gcc was recently upgraded it changed the ABI for C++. Imagine > if one had mismatched .o files for libstdc++ if some of the source files > didn't change. That kind of dependency (on a compiler ABI) is not easily > expressed in Makefilesm, and certainly not cleanly. True... As I said, there may be some exceptions, like midway compiler changes (in case of ABI incompatibility - although I wonder, why is it shared objects are compatible and plain ones aren't?), timestamp wrecks, or massive header file changes, etc. However, normally, I can't see such things happening, so I suppose that just continuing a make should work then. Nothing really serious, I just thought I had to comment about it after having dealt with many annoying broken Makefiles of some projects (which break on every update, or try to compile stuff during 'make install', or recompile almost everything on every minor typo fix...) - take the state of Mozilla and Samba two years ago for example. -- Tom -- Tom Alsberg - hacker (being the best description fitting this space) Web page: http://www.cs.huji.ac.il/~alsbergt/ DISCLAIMER: The above message does not even necessarily represent what my fingers have typed on the keyboard, save anything further.