From owner-freebsd-ports@FreeBSD.ORG Sun Feb 21 19:01:53 2010 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6E6BE106566B for ; Sun, 21 Feb 2010 19:01:53 +0000 (UTC) (envelope-from gerald@pfeifer.com) Received: from vexpert.dbai.tuwien.ac.at (vexpert.dbai.tuwien.ac.at [128.131.111.2]) by mx1.freebsd.org (Postfix) with ESMTP id 2D48E8FC12 for ; Sun, 21 Feb 2010 19:01:52 +0000 (UTC) Received: from acrux.dbai.tuwien.ac.at (acrux.dbai.tuwien.ac.at [128.131.111.60]) by vexpert.dbai.tuwien.ac.at (Postfix) with ESMTP id 111B31E072; Sun, 21 Feb 2010 20:01:49 +0100 (CET) Received: by acrux.dbai.tuwien.ac.at (Postfix, from userid 1203) id 887B91604A; Sun, 21 Feb 2010 20:01:52 +0100 (CET) Received: from localhost (localhost [127.0.0.1]) by acrux.dbai.tuwien.ac.at (Postfix) with ESMTP id 7744A16048; Sun, 21 Feb 2010 20:01:52 +0100 (CET) Date: Sun, 21 Feb 2010 20:01:52 +0100 (CET) From: Gerald Pfeifer To: jhell In-Reply-To: Message-ID: References: User-Agent: Alpine 1.99 (LSU 1142 2008-08-13) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Cc: freebsd-ports@freebsd.org Subject: Re: lang/gcc44 Inconsistant package list. Leftover files. X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 21 Feb 2010 19:01:53 -0000 On Fri, 19 Feb 2010, jhell wrote: > Below my .sig is what I found upon removal of the old version of gcc44 > 0126 before re-building 0209. > > Is there a chance to get this fixed ? > > Not sure exactly whats causing this so I did not look further into it. Looking at the specific error message, it seems your installation was (or is) in a very interesting state. Whenever I make an update to the lang/gcc44 port or any of it's peers, doing a full installation into a virgin directory followed by a dein- stallation, as per the Porters' Handbook at http://www.freebsd.org/doc/en/books/porters-handbook/porting-testing.html and lang/gcc44 passes this without any problems, let alone the kind of problems you are seeing. Also the FreeBSD Ports Cluster continously builds this port (among all the others) and has not reported anything that looks like this. >From all I can tell, this is not an issue with the port. I did try to reproduce, but could not. Still, thanks for the report, and if you can provide instructions on how to reproduce, I'll of course look into it again. Gerald