You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@subversion.apache.org by Warren Falk <wa...@warrenfalk.com> on 2003/05/14 15:39:31 UTC

Subversion build failure

I'm running RedHat Linux 8.0.

I have apache 2.0.44 in /usr/local/apache2

The apr.h in  /usr/local/apache2/include does not include the define for
APR_UINT64_T_FMT (it is an older version)

so I configured svn with --with-apr=<apr
directory> --with-apr-util=<apr-util directory>

when building subversion/mod_dav_svn/liveprops.lo, I get a "parse error
before APR_UINT64_T_FMT" because the apache include folder comes before the
apr include folder in the makefile which causes the old apr.h file to be
included even though I configured with the new apr folder.  This was
frustrating to track down.

because apr is included in apache2 includes, the --with-apr should
"override" the apache location where possible, I believe.  To do this I
altered Makefile.in ... here is the diff, this solved my build problem - I
simply moved $(INCLUDES) before $(APACHE_INCLUDES) in the search order for
mod_dav_svn destined files.

--- Makefile.in (revision 5891)
+++ Makefile.in (working copy)
@@ -121,7 +121,7 @@
 LT_COMPILE = $(LIBTOOL) $(LTFLAGS) --mode=compile $(COMPILE)

 # special compilation for files destined for mod_dav_svn
-COMPILE_APACHE_MOD = $(LIBTOOL) $(LTFLAGS) --mode=compile $(CC) $(CPPFLAGS)
$(CFLAGS) $(APACHE_INCLUDES) $(INCLUDES) -o $@ -c
+COMPILE_APACHE_MOD = $(LIBTOOL) $(LTFLAGS) --mode=compile $(CC) $(CPPFLAGS)
$(CFLAGS) $(INCLUDES) $(APACHE_INCLUDES) -o $@ -c

 # special compilation for files destined for libsvn_swig_* (e.g.
swigutil_*.c)
 COMPILE_SWIG_PY = $(LIBTOOL) $(LTFLAGS) --mode=compile $(CC)
$(CPPFLAGS) -DSWIGPYTHON $(CFLAGS) $(SWIG_PY_INCLUDES) $(INCLUDES) -o $@ -c




---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org

RE: Subversion build failure

Posted by Sander Striker <st...@apache.org>.
> From: kfogel@newton.ch.collab.net [mailto:kfogel@newton.ch.collab.net]On
> Behalf Of kfogel@collab.net

> "Warren Falk" <wa...@warrenfalk.com> writes:
> > My point is that no matter what I specify for --with-apr, it still uses the
> > apr under the apache folder which it includes by default so --with-apr is
> > actually useless in mod_dav_svn.  This seems incorrect.
> > 
> > Because apache automatically includes apr, it only makes sense that if I
> > specify a different apr using --with-apr, that it use that version not the
> > apache default.
> > 
> > Am I wrong there?
> 
> Hmmm.  I think you might be; it seems to me that since mod_dav_svn
> links into Apache, it has to use the same apr and apr-util that Apache
> is using, no?

Exactly.  The apr mod_dav_svn will see when hooked into httpd is the one
that httpd was linked against.  It makes totally no sense to use a different
apr of mod_dav_svn.
 
> Of course, silently ignoring the --with-apr flag is bad; I just don't
> think it can reasonably obey the flag either...

Well, we could throw an error when both flags are used.  --with-apache implies
using apr and apr-util that go with httpd.


Sander

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org

Re: Subversion build failure

Posted by kf...@collab.net.
"Warren Falk" <wa...@warrenfalk.com> writes:
> My point is that no matter what I specify for --with-apr, it still uses the
> apr under the apache folder which it includes by default so --with-apr is
> actually useless in mod_dav_svn.  This seems incorrect.
> 
> Because apache automatically includes apr, it only makes sense that if I
> specify a different apr using --with-apr, that it use that version not the
> apache default.
> 
> Am I wrong there?

Hmmm.  I think you might be; it seems to me that since mod_dav_svn
links into Apache, it has to use the same apr and apr-util that Apache
is using, no?

Of course, silently ignoring the --with-apr flag is bad; I just don't
think it can reasonably obey the flag either...

-Karl

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org

Re: Subversion build failure

Posted by Warren Falk <wa...@warrenfalk.com>.
< karl: >
> I believe we require 2.0.45 now.  See this item in the INSTALL file
>

My point is that no matter what I specify for --with-apr, it still uses the
apr under the apache folder which it includes by default so --with-apr is
actually useless in mod_dav_svn.  This seems incorrect.

Because apache automatically includes apr, it only makes sense that if I
specify a different apr using --with-apr, that it use that version not the
apache default.

Am I wrong there?



---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org

Re: Subversion build failure

Posted by kf...@collab.net.
"Warren Falk" <wa...@warrenfalk.com> writes:
> I have apache 2.0.44 in /usr/local/apache2

I believe we require 2.0.45 now.  See this item in the INSTALL file

      7.  Apache Web Server 2.0.45 or newer
      [...]

Best,
-Karl

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org