From owner-freebsd-current@FreeBSD.ORG Sun Feb 29 13:30:24 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 3F9AC16A4CE for ; Sun, 29 Feb 2004 13:30:24 -0800 (PST) Received: from mail.daemonground.de (daemonground.de [217.160.129.149]) by mx1.FreeBSD.org (Postfix) with ESMTP id EA9C543D1F for ; Sun, 29 Feb 2004 13:30:23 -0800 (PST) (envelope-from sascha@daemonground.de) Received: from localhost (localhost.localdomain [127.0.0.1]) by mail.daemonground.de (Postfix) with ESMTP id 0D1CF8A013 for ; Sun, 29 Feb 2004 22:30:23 +0100 (CET) Received: from mail.daemonground.de ([127.0.0.1]) by localhost (daemonground.de [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 72310-07 for ; Sun, 29 Feb 2004 22:30:20 +0100 (CET) Received: from [192.168.2.18] (pD9530A9D.dip.t-dialin.net [217.83.10.157]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.daemonground.de (Postfix) with ESMTP id 14DBE89260 for ; Sun, 29 Feb 2004 22:30:20 +0100 (CET) From: Sascha Holzleiter To: freebsd-current@freebsd.org In-Reply-To: <1078018800.894.19.camel@dreamland.chief.home> References: <1078018800.894.19.camel@dreamland.chief.home> Content-Type: text/plain Message-Id: <1078090214.653.6.camel@dreamland.chief.home> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.5 Date: Sun, 29 Feb 2004 22:30:14 +0100 Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at daemonground.de Subject: Re: /usr/ports/graphics/tiff build failure 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: Sun, 29 Feb 2004 21:30:24 -0000 On Sun, 2004-02-29 at 02:40, Sascha Holzleiter wrote: > I have the same problem with a 28.2.(yesterday) -CURRENT. > With a 2004.02.26 system the problem goes away so there must have been a change between 2004.02.26 and 2004.02.28 which broke this... Regards, Sascha