From owner-freebsd-ports-bugs@FreeBSD.ORG Mon Apr 25 08:10:16 2005 Return-Path: Delivered-To: freebsd-ports-bugs@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3102116A4CE; Mon, 25 Apr 2005 08:10:16 +0000 (GMT) Received: from 21322530218.direct.eti.at (21322530218.direct.eti.at [213.225.30.218]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2748D43D1F; Mon, 25 Apr 2005 08:10:15 +0000 (GMT) (envelope-from tilman@arved.at) Received: from jim.arved.de (localhost [127.0.0.1])j3P8AD8T017037; Mon, 25 Apr 2005 10:10:13 +0200 (CEST) (envelope-from tilman@arved.at) Received: (from arved@localhost) by jim.arved.de (8.13.1/8.13.1/Submit) id j3P8ADc4017036; Mon, 25 Apr 2005 10:10:13 +0200 (CEST) (envelope-from tilman@arved.at) X-Authentication-Warning: jim.arved.de: arved set sender to tilman@arved.at using -f Date: Mon, 25 Apr 2005 10:10:13 +0200 From: Tilman Linneweh To: Hye-Shik Chang Message-ID: <20050425081013.GC46071@arved.at> References: <200504211559.j3LFx5Uo020584@freefall.freebsd.org> <426C3626.6070905@yasi.to> <4f0b69dc05042423592636c024@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4f0b69dc05042423592636c024@mail.gmail.com> User-Agent: Mutt/1.4.2.1i cc: freebsd-ports-bugs@freebsd.org cc: David Kleiner cc: HAYASHI Yasushi cc: freebsd-python@freebsd.org Subject: Re: ports/75341: Unable to install py-imaging port python2.4 on amd64-current X-BeenThere: freebsd-ports-bugs@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Ports bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 25 Apr 2005 08:10:16 -0000 * Hye-Shik Chang [2005-04-25 08:59]: > 2005/4/25, HAYASHI Yasushi : > > Hello, > > > > There is no error logs on http://pointyhat.freebsd.org/errorlogs/ now > > about this PR. > > > > This PR was written at Dec 20 2004 at first. Isn't it too old PR for > > 6-current? > > > > There's no problem in my amd64 machine also. Thanks for confirmation. I rebuild all dependencies (tried with -O and -O2) and now i can't reproduce it either, so it looks like a temporary CURRENT bug. regards tilman