From owner-freebsd-apache@FreeBSD.ORG Thu Jun 30 21:15:15 2011 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 E7F3C106564A for ; Thu, 30 Jun 2011 21:15:15 +0000 (UTC) (envelope-from ohauer@FreeBSD.org) Received: from p578be941.dip0.t-ipconnect.de (p578be941.dip0.t-ipconnect.de [87.139.233.65]) by mx1.freebsd.org (Postfix) with ESMTP id 6E2318FC14 for ; Thu, 30 Jun 2011 21:15:15 +0000 (UTC) Received: from [192.168.0.100] (cde1100.uni.vrs [192.168.0.100]) (Authenticated sender: ohauer) by p578be941.dip0.t-ipconnect.de (Postfix) with ESMTPSA id C220B20624; Thu, 30 Jun 2011 23:15:12 +0200 (CEST) Message-ID: <4E0CE75F.1090101@FreeBSD.org> Date: Thu, 30 Jun 2011 23:15:11 +0200 From: Olli Hauer User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:5.0) Gecko/20110624 Thunderbird/5.0 MIME-Version: 1.0 To: =?UTF-8?B?0JTQvNC40YLRgNC40Lkg0KfQsNGB0YLQuNC9?= References: In-Reply-To: X-Enigmail-Version: 1.2 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Cc: apache@FreeBSD.org Subject: Re: Error in apache22-itk-mpm X-BeenThere: freebsd-apache@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: ohauer@FreeBSD.org List-Id: Support of apache-related ports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 30 Jun 2011 21:15:16 -0000 On 2011-06-02 05:39, Дмитрий Частин wrote: > configure: error: the selected mpm -- itk -- is not supported > ===> Script "configure" failed unexpectedly. > Please report the problem to apache@FreeBSD.org [maintainer] and attach the > "/usr/ports/www/apache22-itk-mpm/work/httpd-2.2.19/config.log" including the > output of the failure of your make command. Also, it might be a good idea to > provide an overview of all packages installed on your system (e.g. an `ls > /var/db/pkg`). > *** Error code 1 > > Stop in /usr/ports/www/apache22-itk-mpm. > *** Error code 1 > > Stop in /usr/ports/www/apache22-itk-mpm. > Hi, this issue should be solved now with the last commit to the apache22 port.