From owner-freebsd-current@FreeBSD.ORG Thu Dec 16 18:30:37 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 373B816A4CE; Thu, 16 Dec 2004 18:30:37 +0000 (GMT) Received: from pi.codefab.com (pi.codefab.com [199.103.21.227]) by mx1.FreeBSD.org (Postfix) with ESMTP id ADB9943D58; Thu, 16 Dec 2004 18:30:36 +0000 (GMT) (envelope-from cswiger@mac.com) Received: from [192.168.1.3] (pool-68-160-207-47.ny325.east.verizon.net [68.160.207.47]) by pi.codefab.com (8.12.11/8.12.11) with ESMTP id iBGIUT3Q096012 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 16 Dec 2004 13:30:31 -0500 (EST) Message-ID: <41C1D442.8090608@mac.com> Date: Thu, 16 Dec 2004 13:30:26 -0500 From: Chuck Swiger Organization: The Courts of Chaos User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.3) Gecko/20040910 X-Accept-Language: en-us, en MIME-Version: 1.0 To: FreeBSD-Current References: <41C10C99.10600@mac.com> <20041216103849.GF10839@ip.net.ua> In-Reply-To: <20041216103849.GF10839@ip.net.ua> X-Enigmail-Version: 0.89.5.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=1.8 required=5.5 tests=RCVD_IN_NJABL_DUL, RCVD_IN_SORBS_DUL autolearn=disabled version=3.0.1 X-Spam-Level: * X-Spam-Checker-Version: SpamAssassin 3.0.1 (2004-10-22) on pi.codefab.com cc: harti@freebsd.org Subject: Re: make vs. gmake in 6-CURRENT... X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 16 Dec 2004 18:30:37 -0000 Hi, Ruslan, Harti, (and all): Ruslan Ermilov wrote: > On Wed, Dec 15, 2004 at 11:18:33PM -0500, Chuck Swiger wrote: [ ... ] >>However, it seems like that space-stuffing when generating paths would >>break lots of other things. Anyway, I wanted to bring up the issue here >>and ask whether this change to make's behavior is expected or whether it >>should be considered a bug...? > > FWIW, I cannot reproduce this problem: Did you comment out the "USE_GMAKE= YES" line? As I mentioned, a fix to the port has already been applied, but you can see the problem reproduced on the ports build cluster at this URL: http://pointyhat.freebsd.org/errorlogs/i386-errorlogs/e.6.2004121303/dvd+rw-tools-5.21.4.10.8.log ----- Harti Brandt wrote: [ ... ] > I cannot reproduce this (I have not looked at the port's makefile). Can > you make a small makefile that shows this behaviour? Sure, I'll give it a shot. Try a "make install" against this: # Makefile attempt to reproduce bug BIN_FILES= foo bar baz WRKSRC= /tmp install: .for i in ${BIN_FILES} cp ${WRKSRC}/${i} /var/tmp/ .endfor ...and see whether 6's make space-stuffs "/tmp/foo" into "/tmp/ foo". If it doesn't, the port's Makefile isn't much bigger than this example. Thanks for the interest... -- -Chuck