From owner-cvs-all@FreeBSD.ORG Fri Jul 25 21:59:19 2008 Return-Path: Delivered-To: cvs-all@FreeBSD.org Received: by hub.freebsd.org (Postfix, from userid 1033) id 186701065679; Fri, 25 Jul 2008 21:59:19 +0000 (UTC) Date: Fri, 25 Jul 2008 21:59:19 +0000 From: Alexey Dokuchaev To: QA Tindy Message-ID: <20080725215919.GA31086@FreeBSD.org> References: <200807250934.m6P9YjbR036275@repoman.freebsd.org> <20080726004919.0a424aea@it.buh.tecnik93.com> Mime-Version: 1.0 Content-Type: text/plain; charset=koi8-r Content-Disposition: inline In-Reply-To: <20080726004919.0a424aea@it.buh.tecnik93.com> User-Agent: Mutt/1.4.2.1i Cc: cvs-ports@FreeBSD.org, Mark Linimon , cvs-all@FreeBSD.org, ports-committers@FreeBSD.org Subject: Re: cvs commit: ports/games/warsow Makefile X-BeenThere: cvs-all@freebsd.org X-Mailman-Version: 2.1.5 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, 25 Jul 2008 21:59:19 -0000 On Sat, Jul 26, 2008 at 12:49:19AM +0300, QA Tindy wrote: > Hi, > > The build which triggered this email is done under tinderbox-2.4.3, on > 7-STABLE on amd64, with tinderd_flags="-nullfs -plistcheck -onceonly" > and ccache support, with the "official" up-to-date Ports Tree, with the > following vars set: > NOPORTDOCS=yes, NOPORTEXAMPLES=yes, NOPORTDATA=yes, FORCE_PACKAGE=yes. > > Excerpt from http://t64.tecnik93.com/logs/7-STABLE-FTP/warsow-0.42.log: > > ======================================== > ===> Building package for warsow-0.42 > tar: share/warsow/basewsw/cgame_amd64.so: Cannot stat: No such file or directory > tar: share/warsow/basewsw/game_amd64.so: Cannot stat: No such file or directory > tar: share/warsow/basewsw/ui_amd64.so: Cannot stat: No such file or directory > tar: share/warsow/libs/irc_amd64.so: Cannot stat: No such file or directory > tar: share/warsow/libs/snd_openal_amd64.so: Cannot stat: No such file or directory > tar: share/warsow/libs/snd_qf_amd64.so: Cannot stat: No such file or directory Thanks, I'm aware of this issue on amd64. I'm currently investigating it with a help from an amd64 user, as I currently don't have amd64 box handy at my possession (or that I could use). ./danfe