From owner-freebsd-apache@FreeBSD.ORG Sat Jun 13 19:57:37 2009 Return-Path: Delivered-To: apache@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 94516106566C; Sat, 13 Jun 2009 19:57:37 +0000 (UTC) (envelope-from mi+thun@aldan.algebra.com) Received: from aldan.algebra.com (aldan.algebra.com [216.254.65.224]) by mx1.freebsd.org (Postfix) with ESMTP id 49FC08FC17; Sat, 13 Jun 2009 19:57:36 +0000 (UTC) (envelope-from mi+thun@aldan.algebra.com) Received: from aldan.algebra.com (localhost [127.0.0.1]) by aldan.algebra.com (8.14.3/8.14.3) with ESMTP id n5DJvanI067361; Sat, 13 Jun 2009 15:57:36 -0400 (EDT) (envelope-from mi+thun@aldan.algebra.com) Message-ID: <4A3404B0.6080205@aldan.algebra.com> Date: Sat, 13 Jun 2009 15:57:36 -0400 From: "Mikhail T." User-Agent: Thunderbird 2.0.0.21 (X11/20090407) MIME-Version: 1.0 To: pav@FreeBSD.org References: <1244916221.1261.10.camel@hood.oook.cz> <4A33FB7F.7040401@aldan.algebra.com> <1244922033.1261.19.camel@hood.oook.cz> <4A3401AA.40409@aldan.algebra.com> <1244922341.1261.20.camel@hood.oook.cz> In-Reply-To: <1244922341.1261.20.camel@hood.oook.cz> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Cc: Erwin Lansing , apache@FreeBSD.org Subject: Re: [Fwd: mod_dtcl-0.12.0_1 failed on amd64 8] X-BeenThere: freebsd-apache@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Support of apache-related ports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 13 Jun 2009 19:57:38 -0000 Pav Lucistnik написав(ла): > After closer look, it seems > - this failure is present on both 6.x and 8.x runs > - this failure was reported to you two months ago > On May 27th (not two months ago) Erwin sent me a report about failure on i386: mod_dtcl.c -o mod_dtcl.So mod_dtcl.c: In function `get_parse_exec_file': mod_dtcl.c:383: warning: long unsigned int format, time_t arg (arg 4) mod_dtcl.c:383: warning: long unsigned int format, time_t arg (arg 5) That's a completely different error. I'm not aware of any other outstanding problems with the port. -mi