Return-Path: Delivered-To: apmail-httpd-dev-archive@www.apache.org Received: (qmail 68474 invoked from network); 25 Sep 2009 17:49:21 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 25 Sep 2009 17:49:21 -0000 Received: (qmail 27207 invoked by uid 500); 25 Sep 2009 17:49:20 -0000 Delivered-To: apmail-httpd-dev-archive@httpd.apache.org Received: (qmail 27129 invoked by uid 500); 25 Sep 2009 17:49:20 -0000 Mailing-List: contact dev-help@httpd.apache.org; run by ezmlm Precedence: bulk Reply-To: dev@httpd.apache.org list-help: list-unsubscribe: List-Post: List-Id: Delivered-To: mailing list dev@httpd.apache.org Received: (qmail 27120 invoked by uid 99); 25 Sep 2009 17:49:19 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 25 Sep 2009 17:49:19 +0000 X-ASF-Spam-Status: No, hits=2.2 required=10.0 tests=HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of trawick@gmail.com designates 72.14.220.156 as permitted sender) Received: from [72.14.220.156] (HELO fg-out-1718.google.com) (72.14.220.156) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 25 Sep 2009 17:49:11 +0000 Received: by fg-out-1718.google.com with SMTP id 22so876037fge.12 for ; Fri, 25 Sep 2009 10:48:50 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:content-type; bh=da++tldEx1N/uDD1gcAxIE9SMUFDdOYY0rzANBm0SYo=; b=j03t72IrUbCiB1mk24wqBUSU7zng/6in+j3o0YkFjOSUJCZO7AOXkNnJqJeU35Nz4e EA7Tv8B94dIiS3hLdfjv2vCNyZKFKnJONWEegcZ/dXBRvySJy6TP/ov0ALVHu2aGeM0G l0PNti3cosbmAC+SRWE70CYyOwzzDfEatAte4= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=xETShOKg24GdSDCdr6/NL9LB3gvGHTEzcbluyBbtQTcQUybtLi2OTu9b9V2L9bszrn ddNR0xSAbZdDITyZJRkZQbiZXcrE/v9Uj50I/icMj6fyVWb6fk4C4XJ12BGVVVr8ajFp PgZ7xfVkjJ9lSUlKPS1Yt6Aljn65pNElOdadM= MIME-Version: 1.0 Received: by 10.86.227.1 with SMTP id z1mr1172716fgg.56.1253900930233; Fri, 25 Sep 2009 10:48:50 -0700 (PDT) In-Reply-To: References: Date: Fri, 25 Sep 2009 13:48:50 -0400 Message-ID: Subject: Re: [mod_fcgid] Problems installing 2.3.1 on SuSE 10.3 64bit due to missing mpm.h and mpm_default.h From: Jeff Trawick To: dev@httpd.apache.org Content-Type: multipart/alternative; boundary=001485ea0ff487b86804746a8f20 X-Virus-Checked: Checked by ClamAV on apache.org --001485ea0ff487b86804746a8f20 Content-Type: text/plain; charset=ISO-8859-1 On Fri, Sep 25, 2009 at 1:02 PM, Marcus Merz wrote: > I do not know whether i did something wrong but before a new release of > mod_fcgid, i wanted to share my experience: > > I use Apache 2.2.13 on a OpenSUSE 10.3 distri and did download and extract > mod_fcgid-2.3.1-beta.tar.gz to /usr/local/source/mod_fcgid-2.3.1 > > From there i did > > APXS=/usr/sbin/apxs2 ./configure.apxs > > and following 'make', i got a gcc compiler error complaining about a > missing > mpm.h and mpm_default.h in /usr/include/apache2 > > I came around the problem by symlinking both files using > :/usr/include/apache2 # ln -s ../apache2-prefork/mpm.h mpm.h > :/usr/include/apache2 # ln -s ../apache2-prefork/mpm_default.h > mpm_default.h > mod_fcgid includes mpm_common.h, which in turn includes those. It is perhaps odd for an unbundled module to use those, but httpd does intend for them to be installed. (In fact the mod_fcgid process manager has enough commonality with the httpd MPMs that it might use the same services more extensively in the future.) Can you confirm that this simple module also fails to build? ---------mod_foo.c-------- #include "mpm_common.h" ---------end-------------- Try to build with "apxs -c mod_foo.c" Can you follow up with the OpenSUSE folks on that? It sounds like a packaging problem with their httpd which could affect a minority of modules (those which use mpm_common.h), but maybe they have an explanation of how those .h files are to be found when using apxs. > > So, in the end i got it running (the problems i entered after using > mod_fcgid with binary content are in another thread on this list). I hope to get back to that thread this weekend. (I don't think it has anything to do with binary content, FWIW. It just has to do with the selection by the PHP interpreter of which is the script, and whether or not mod_fcgid is passing information about the request to PHP in a way that PHP can figure it out.) --001485ea0ff487b86804746a8f20 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
On Fri, Sep 25, 2009 at 1:02 PM, Marcus Merz <mmerz@gmx.de> wrote:
I do not know whether i did something wrong but before a new release of
mod_fcgid, i wanted to share my experience:

I use Apache 2.2.13 on a OpenSUSE 10.3 distri and did download and extract<= br> mod_fcgid-2.3.1-beta.tar.gz to /usr/local/source/mod_fcgid-2.3.1

>From there i did

APXS=3D/usr/sbin/apxs2 ./configure.apxs

and following 'make', i got a gcc compiler error complaining about = a missing
mpm.h and mpm_default.h in /usr/include/apache2

I came around the problem by symlinking both files using
:/usr/include/apache2 # ln -s ../apache2-prefork/mpm.h mpm.h
:/usr/include/apache2 # ln -s ../apache2-prefork/mpm_default.h mpm_default.= h

mod_fcgid includes mpm_common.h, which in turn i= ncludes those.

It is perhaps odd for an unbundled module to use thos= e, but httpd does intend for them to be installed.=A0 (In fact the mod_fcgi= d process manager has enough commonality with the httpd MPMs that it might = use the same services more extensively in the future.)

Can you confirm that this simple module also fails to build?

---= ------mod_foo.c--------
#include "mpm_common.h"
---------en= d--------------

Try to build with "apxs -c mod_foo.c"

Can you follow up with the OpenSUSE folks on that?=A0 It sounds like a = packaging problem with their httpd which could affect a minority of modules= (those which use mpm_common.h), but maybe they have an explanation of how = those .h files are to be found when using apxs.

=A0

So, in the end i got it running (the problems i entered after using
mod_fcgid with binary content are in another thread on this list).

I hope to get back to that thread this weekend.

(I don&= #39;t think it has anything to do with binary content, FWIW.=A0 It just has= to do with the selection by the PHP interpreter of which is the script, an= d whether or not mod_fcgid is passing information about the request to PHP = in a way that PHP can figure it out.)

--001485ea0ff487b86804746a8f20--