Subject: Re: RE: problem getting apache2 to work with subversion - msg#00077

Previous Message by Date: click to view message preview

RE: problem getting apache2 to work with subversion

You say you were "..trying again and again to build apache from source..." Please post the contents of your "config.nice" file, or if that's no longer available, post how you invoked "configure". For example, I use the following for AIX: CC="xlc_r"; export CC CPPFLAGS="-D_THREAD_SAFE"; export CPPFLAGS ./configure \ --prefix=/usr/local/apache \ --with-mpm=worker \ --without-berkeley-db \ --enable-dav=static \ --enable-dav_fs=static \ --with-ssl=/usr/local/ssl \ --enable-ssl=static \ --with-egd=/etc/entropy -tony -----Original Message----- From: dav-dev-bounces@xxxxxxxx [mailto:dav-dev-bounces@xxxxxxxx] On Behalf Of mhardas@xxxxxxxx Sent: Thursday, August 18, 2005 11:41 AM To: jfeise@xxxxxxxxxxx Cc: dav-dev@xxxxxxxx Subject: Re: [dav-dev] problem getting apache2 to work with subversion ok, so i guess the problem was tht i wasnt using a released version of apache, though i was building from apache 2.0.54 source. !!!??? >You only found that that this separate mod_dav doesn't compile with Apache 2... well this, http://www.webdav.org/mod_dav/#how, led me to believe it does !!! > Because that separate mod_dav is for Apache 1.3 *only*. It won't > compile with Apache 2, no matter what you try. trying again and again to build apache from source (exact file httpd-2.0.54.tar.gz) and unable to compile mod_dav, again led me to download a seperate version of mod_dav. > Hmm, no. You did it because *you* decided to use the latest Apache > source code from their archive. That's the crucial mistake. > Unless you are a developer or need something really special that's not > in the released version, it is *always* the best and easiest to use > release versions. They are tested and work. Stuff in source archives > is in flux, and as such often broken. After all, that's why developers > work on it... well tht is just true.... >Yes. will do it and let you know. Thanks. Manas. ----- Original Message ----- From: Joachim Feise <jfeise@xxxxxxxxxxx> Date: Thursday, August 18, 2005 2:22 pm Subject: Re: [dav-dev] problem getting apache2 to work with subversion > mhardas@xxxxxxxx wrote on 8/18/2005 10:41: > > hi again, > > webdav.org says tht mod_dav works for apache versions >=1.3 ... > so i > > gave it a try. atleast i found tht apxs installation is broken. > > No, you didn't find that. That's just your conjecture. > You only found that that this separate mod_dav doesn't compile with > Apache 2... > See http://www.catb.org/~esr/faqs/smart-questions.html#id3001405 > It generally helps to have internalized that document, anyway ;-) > > > ok let me start from the beginning. iam trying to install Subversion > > (file managment software) on redhat linux 9. Subversion uses WebDAV > > protocol to make its repository available over the network (http > > access...it also has another protocol svn for remote sharing but > i dont > > want to use that). > > I installed subversion and its working fine. then i installed > Apache2> (from source) hoping tht it would already include all the > dependencies,> as the documentation said it would. > > That's the mistake right there. Get a released version, e.g., 2.0.54, > and everything will work. > > > My first problem was, when i couldnt access the repository over the > > netowrk, though apache did start at tht time. thts when i found tht > > apache doesnt know about the repos and needs mod_dav. So then i > started> looking for mod_dav but as you said it wasnt compiled at > all. I build > > apache again and again but mod_dav was never build. So finally i > > downloaded mod_dav source (which they say works for >=1.3) and > tried to > > build it. thts when i got the error, > > When the website was written, there was no Apache 2, so at that time > it was true. Since mod_dav is included in Apache 2, there is not even > any need to have a separate product for Apache 2. > > > configure: error: your apxs installation is broken and cannot be > used.> So later i looked at the indicated links (php dev forums) and > made > > changes to apxs accordingly, however with no luck. > > Because that separate mod_dav is for Apache 1.3 *only*. It won't > compile with Apache 2, no matter what you try. > > >>For example, you earlier said you were using buildconf. Why? > That's only > >>necessary if you checked out the source code from the archive > > > > I did tht simply because the install file told me to do so > (subversion) > Hmm, no. You did it because *you* decided to use the latest Apache > source code from their archive. That's the crucial mistake. > > Unless you are a developer or need something really special that's not > in the released version, it is *always* the best and easiest to use > release versions. They are tested and work. Stuff in source archives > is in flux, and as such often broken. After all, that's why developers > work on it... > > > So here is the whole story, i guess my best bet is to reinstall > apache> from prepackaged binaries. > > Yes. > > -Joe > _______________________________________________ dav-dev maillist - dav-dev@xxxxxxxx http://dav.lyra.org/mailman/listinfo/dav-dev

Next Message by Date: click to view message preview

close_stream and commit

Hi all, I'm a little confused by the close_stream callback in dav_provider. Under what conditions is the commit flag true? Also, the comment mentions that "the commit flag is ignored for streams opened for reading." If I am implementing my own provider, does this imply that my provider *must* know if the stream has been opened for reading? http://lxr.webperf.org/source.cgi/modules/dav/main/mod_dav.h#1794 Thanks dave

Previous Message by Thread: click to view message preview

RE: problem getting apache2 to work with subversion

You say you were "..trying again and again to build apache from source..." Please post the contents of your "config.nice" file, or if that's no longer available, post how you invoked "configure". For example, I use the following for AIX: CC="xlc_r"; export CC CPPFLAGS="-D_THREAD_SAFE"; export CPPFLAGS ./configure \ --prefix=/usr/local/apache \ --with-mpm=worker \ --without-berkeley-db \ --enable-dav=static \ --enable-dav_fs=static \ --with-ssl=/usr/local/ssl \ --enable-ssl=static \ --with-egd=/etc/entropy -tony -----Original Message----- From: dav-dev-bounces@xxxxxxxx [mailto:dav-dev-bounces@xxxxxxxx] On Behalf Of mhardas@xxxxxxxx Sent: Thursday, August 18, 2005 11:41 AM To: jfeise@xxxxxxxxxxx Cc: dav-dev@xxxxxxxx Subject: Re: [dav-dev] problem getting apache2 to work with subversion ok, so i guess the problem was tht i wasnt using a released version of apache, though i was building from apache 2.0.54 source. !!!??? >You only found that that this separate mod_dav doesn't compile with Apache 2... well this, http://www.webdav.org/mod_dav/#how, led me to believe it does !!! > Because that separate mod_dav is for Apache 1.3 *only*. It won't > compile with Apache 2, no matter what you try. trying again and again to build apache from source (exact file httpd-2.0.54.tar.gz) and unable to compile mod_dav, again led me to download a seperate version of mod_dav. > Hmm, no. You did it because *you* decided to use the latest Apache > source code from their archive. That's the crucial mistake. > Unless you are a developer or need something really special that's not > in the released version, it is *always* the best and easiest to use > release versions. They are tested and work. Stuff in source archives > is in flux, and as such often broken. After all, that's why developers > work on it... well tht is just true.... >Yes. will do it and let you know. Thanks. Manas. ----- Original Message ----- From: Joachim Feise <jfeise@xxxxxxxxxxx> Date: Thursday, August 18, 2005 2:22 pm Subject: Re: [dav-dev] problem getting apache2 to work with subversion > mhardas@xxxxxxxx wrote on 8/18/2005 10:41: > > hi again, > > webdav.org says tht mod_dav works for apache versions >=1.3 ... > so i > > gave it a try. atleast i found tht apxs installation is broken. > > No, you didn't find that. That's just your conjecture. > You only found that that this separate mod_dav doesn't compile with > Apache 2... > See http://www.catb.org/~esr/faqs/smart-questions.html#id3001405 > It generally helps to have internalized that document, anyway ;-) > > > ok let me start from the beginning. iam trying to install Subversion > > (file managment software) on redhat linux 9. Subversion uses WebDAV > > protocol to make its repository available over the network (http > > access...it also has another protocol svn for remote sharing but > i dont > > want to use that). > > I installed subversion and its working fine. then i installed > Apache2> (from source) hoping tht it would already include all the > dependencies,> as the documentation said it would. > > That's the mistake right there. Get a released version, e.g., 2.0.54, > and everything will work. > > > My first problem was, when i couldnt access the repository over the > > netowrk, though apache did start at tht time. thts when i found tht > > apache doesnt know about the repos and needs mod_dav. So then i > started> looking for mod_dav but as you said it wasnt compiled at > all. I build > > apache again and again but mod_dav was never build. So finally i > > downloaded mod_dav source (which they say works for >=1.3) and > tried to > > build it. thts when i got the error, > > When the website was written, there was no Apache 2, so at that time > it was true. Since mod_dav is included in Apache 2, there is not even > any need to have a separate product for Apache 2. > > > configure: error: your apxs installation is broken and cannot be > used.> So later i looked at the indicated links (php dev forums) and > made > > changes to apxs accordingly, however with no luck. > > Because that separate mod_dav is for Apache 1.3 *only*. It won't > compile with Apache 2, no matter what you try. > > >>For example, you earlier said you were using buildconf. Why? > That's only > >>necessary if you checked out the source code from the archive > > > > I did tht simply because the install file told me to do so > (subversion) > Hmm, no. You did it because *you* decided to use the latest Apache > source code from their archive. That's the crucial mistake. > > Unless you are a developer or need something really special that's not > in the released version, it is *always* the best and easiest to use > release versions. They are tested and work. Stuff in source archives > is in flux, and as such often broken. After all, that's why developers > work on it... > > > So here is the whole story, i guess my best bet is to reinstall > apache> from prepackaged binaries. > > Yes. > > -Joe > _______________________________________________ dav-dev maillist - dav-dev@xxxxxxxx http://dav.lyra.org/mailman/listinfo/dav-dev

Next Message by Thread: click to view message preview

close_stream and commit

Hi all, I'm a little confused by the close_stream callback in dav_provider. Under what conditions is the commit flag true? Also, the comment mentions that "the commit flag is ignored for streams opened for reading." If I am implementing my own provider, does this imply that my provider *must* know if the stream has been opened for reading? http://lxr.webperf.org/source.cgi/modules/dav/main/mod_dav.h#1794 Thanks dave