gluster-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Gluster-devel] debian lenny + apache2 + mod_glusterfs 2.0.0rc4


From: Ivan Dimitrov
Subject: [Gluster-devel] debian lenny + apache2 + mod_glusterfs 2.0.0rc4
Date: Tue, 10 Mar 2009 11:38:31 +0200
User-agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; bg; rv:1.8.1.19) Gecko/20081209 Thunderbird/2.0.0.19 Mnenhy/0.7.5.666

Hello list, this is my first time writing here

I've been trying to compile mod_glusterfs 2.0.0.rc4 for debian lenny with apache2.2 from debian package.
I've got the following debian packages installed:
apache2-mpm-prefork
apache2-prefork-dev
apache2-utils
apache2.2-common

./configure --enable-mod_glusterfs --with-apxs=/usr/bin/
...................................
checking for apxs... no
apxs is required to build mod_glusterfs. Use --with-apxs to specify path to apxs. If mod_glusterfs is not required, do not pass --enable-mod_glusterfs option to configure
...................................

Debian puts apxs in "/usr/bin/apxs2" and "--with-apxs=/usr/bin/" does not discover it. I had to make a symlink /usr/bin/apxs -> /usr/bin/apxs2 in order to make configure recognize it. For apache1.3 deb package puts the apxs in the same place /usr/bin/apxs. I suggest to make this option a full path to the binary in order to support multiple apache installations residing in one directory (apache1, apache2, some-custom-apache)


./configure --enable-mod_glusterfs --with-apxs=/usr/bin/
.............................
checking for apxs... apxs
./configure: line 20804: /usr/sbin/httpd: No such file or directory
...............................
At this point the configure completed
mod_glusterfs      : yes ()

By default, Debian's httpd binary is in "/usr/sbin/apache2", so I make a symlink again and configure again. For apache1.3 the binary is called "/usr/sbin/apache"
checking for apxs... apxs

mod_glusterfs      : yes (2.2)


Unfortunately I'm not very experienced with configure to make a patch for it..





reply via email to

[Prev in Thread] Current Thread [Next in Thread]