httpd-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jeff Trawick <traw...@gmail.com>
Subject Re: [mod_fcgid] can't find apr headers
Date Wed, 09 Dec 2009 15:44:11 GMT
On Wed, Dec 9, 2009 at 9:02 AM, Carsten Wiedmann <carsten_sttgt@gmx.de> wrote:
> Jeff Trawick schrieb:
>> Check for the following after configure.apxs finishes:
>>
>> fcgid-2.3.4/Makefile sets top_builddir to /usr/local
> I have:
> | top_builddir=/usr/local/share/apache22
>
> But I think that's ok, because "rules.mk", "config_vars.mk" ... are in:
> /usr/local/share/apache22/build
>
>
>> fcgid-2.3.4/Makefile includes /usr/local/build/rules.mk (from your
>> httpd install)
>
> I have:
> | include /usr/local/share/apache22/build/rules.mk
>
>
>> /usr/local/build/rules.mk includes $(top_builddir)/build/config_vars.mk
>
> I have:
> | include  $(top_builddir)/build/config_vars.mk
>
>
>> /usr/local/build/config_vars.mk includes /usr/local/include/apr-1 in
>> EXTRA_INCLUDES
>>   (if not, what is EXTRA_INCLUDES set to?)
>
> No, the apr include dir is not part of EXTRA_INCLUDES. The apr inlude dir is
> defined in APR_INCLUDEDIR.

The APR include dir should appear within both APR_INCLUDEDIR and
EXTRA_INCLUDES.  Report that to your httpd provider, or open a bug at
https://issues.apache.org/bugzilla/ if you built it yourself.

> BTW: A normal apxs run is using the script defined in APR_CONFIG
> (/usr/local/bin/apr-1-config) to get e.g. the apr include dir.
>
>
> OK, with using apxs I can build and install the module:
> # cd modules/fcgid
> # apxs -c mod_fcgid.c fcgid_bridge.c fcgid_conf.c fcgid_pm_main.c \
>        fcgid_protocol.c fcgid_spawn_ctl.c fcgid_proctbl_unix.c \
>        fcgid_pm_unix.c fcgid_proc_unix.c fcgid_bucket.c fcgid_filter.c
> # apxs -i -a mod_fcgid.la
>
> And and least I have to set e.g.:
> | FcgidIPCDir /var/run/
> | FcgidProcessTableFile /var/run/fcgid_shm
> Or Apache can't start: No access/exists to the default values of these two
> directives.

the enclosing directories exist but you can't write to it?

> Maybe e.g. TMPDIR should be used as default?

The defaults are "logs/fcgidsock" and "logs/fcgid_shm" under
ServerRoot.  I think DEFAULT_REL_RUNTIMEDIR is a better choice than
hard-coded "logs", but that wouldn't help you since your ServerRoot
has no "logs" directory or you have no write access anyway.  I don't
think a system-wide directory is an appropriate default.  (mod_fcgid
currently creates lock files there :( ).

We need a sample configuration file snippet with commented out
defaults for these two and an explanation of when to change the
settings.  (I just opened bug 48360 for that.)

> So for me there is only one problem left. php_apc does not work together
> with mod_fcgid. And the question, who the guilty party is (mod_fcgid or
> apc...). Only the first request for a file is working, a core dump at the
> second, and so on.

As for the core dump, open a bug with the component that is
segfaulting. (I'm guessing PHP or APC, which are developed at
php.net.)

Somewhat separately, can APC work as desired with mod_fcgid barring
any implementation bugs?  I don't know.  See the discussion in
https://issues.apache.org/bugzilla/show_bug.cgi?id=48110

>>> in config.apxs.log I have 2 errors for "conftest_sys_mutex.h.c".  Maybe
>>> that's normal and can happen?
>>
>> That shouldn't affect a build for httpd 2.2, but what are those errors?
>
> | /usr/local/build-1/libtool --silent --mode=compile cc -I/usr/local/include
>  -O2 -pipe -I/usr/include -fno-strict-aliasing
> -I/usr/local/include/apache22 -I. -I/var/ports/usr/ports/www/apache22
> | In file included from /usr/include/sys/mutex.h:37,
> |                  from conftest_sys_mutex_h.c:1:
> | /usr/include/sys/_lock.h:36: error: expected specifier-qualifier-list
> before 'u_int'
> | In file included from /usr/include/sys/mutex.h:38,
> |                  from conftest_sys_mutex_h.c:1:
> | /usr/include/sys/_mutex.h:39: error: expected ':', ',', ';', '}' or
> '__attribute__' before 'mtx_lock'
> | *** Error code 1

Ahhh, I see these in my FreeBSD builds and will try to fix (maybe we
have to include <sys/types.h> first).  This never hurt me since I
didn't try to build for httpd 2.0 on FreeBSD.  Thanks!

Mime
View raw message