From owner-cvs-all@FreeBSD.ORG Fri Aug 1 12:35:27 2003 Return-Path: Delivered-To: cvs-all@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B6C4A37B401; Fri, 1 Aug 2003 12:35:27 -0700 (PDT) Received: from storm.FreeBSD.org.uk (storm.FreeBSD.org.uk [194.242.157.42]) by mx1.FreeBSD.org (Postfix) with ESMTP id A71EA43FCB; Fri, 1 Aug 2003 12:35:26 -0700 (PDT) (envelope-from mark@grondar.org) Received: from storm.FreeBSD.org.uk (Ugrondar@localhost [127.0.0.1]) by storm.FreeBSD.org.uk (8.12.9/8.12.9) with ESMTP id h71JZPHo019790; Fri, 1 Aug 2003 20:35:25 +0100 (BST) (envelope-from mark@grondar.org) Received: (from Ugrondar@localhost)h71JZPjf019789; Fri, 1 Aug 2003 20:35:25 +0100 (BST) X-Authentication-Warning: storm.FreeBSD.org.uk: Ugrondar set sender to mark@grondar.org using -f Received: from grondar.org (localhost [127.0.0.1])h71JWmZ2096463; Fri, 1 Aug 2003 20:32:48 +0100 (BST) (envelope-from mark@grondar.org) From: Mark Murray Message-Id: <200308011932.h71JWmZ2096463@grimreaper.grondar.org> To: Garance A Drosihn In-Reply-To: Your message of "Fri, 01 Aug 2003 14:48:14 EDT." Date: Fri, 01 Aug 2003 20:32:48 +0100 Sender: mark@grondar.org X-Spam-Status: No, hits=0.2 required=5.0 tests=EMAIL_ATTRIBUTION,FROM_NO_LOWER,IN_REP_TO, QUOTED_EMAIL_TEXT,REPLY_WITH_QUOTES version=2.55 X-Spam-Checker-Version: SpamAssassin 2.55 (1.174.2.19-2003-05-19-exp) cc: Gordon Tetlow cc: cvs-src@FreeBSD.org cc: src-committers@FreeBSD.org cc: cvs-all@FreeBSD.org Subject: Re: cvs commit: src/rescue/rescue Makefile X-BeenThere: cvs-all@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: CVS commit messages for the entire tree List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 01 Aug 2003 19:35:28 -0000 Garance A Drosihn writes: > >Will this fix "make rerelease"? > > I don't think it will do much for 'make rerelease', but then I > don't know what problem comes up for 'make rerelease'. Does > that die while trying to build /rescue? The actual breakage comes much later. It looks like building rescue/ causes some .o files to be made with -DFOO type options. Later, the "real" binaries are built without the -DFOO, and link errors and the like result. It looks like there is a conflict with ${.OBJDIR}, in that for each build, a separate ${.OBJDIR} should be used. M -- Mark Murray iumop ap!sdn w,I idlaH