[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: configure script fails to locate apr

From: Kevin Pilch-Bisson <kevin_at_pilch-bisson.net>
Date: 2001-11-27 16:32:15 CET

On Tue, Nov 27, 2001 at 10:24:50AM +0300, Vlad Skvortsov wrote:
> Hello !
>
> Again, please CC: any replies to me as I have not _still_ received
> any acknowledgement from mailing list manager. :-)
>
You might try again, if you are already subscribed you will get a message to
that effect, not a duplicate subscription, and if you aren't then it might
work this time :)
>
> I have checked out latest subversion source code and moved it to
> fresh box to try building current version from scratch. I have one question
> and a couple of suggestions to authors.
>
> I have downloaded and installed httpd-2.0, it is placed in
> /local/apache2. Configure script when running with arguments
>
> --with-apxs=/usr/local/apache2/bin/apxs
> --enable-maintainer-mode
> --with-apr-includes=/local/apache2/include
> --with-apr-libs=/local/apache2/lib
>
> fails to locate and use APR. File config.log states:
>
> configure:2258: Apache Portable Runtime (APR) library configuration
> configure:2442: checking for apr.h
> configure:2452: gcc -E conftest.c
> configure:2449: apr.h: No such file or directory
> configure:2458: $? = 1
> configure: failed program was:
> #line 2448 "configure"
> #include "confdefs.h"
> #include <apr.h>
> configure:2477: result: no
>
> Somewhy it doesn't pass external -I argument to gcc (specified in
> --with-apr-includes). What do I do wrong or miss ?
>
Probably nothing:) I didn't test the --with-apr* options to configure when
I added the ability to use an external APR. I'll look into it immediately.
>
> And several points to developers from stranger's point of view (as I
> am still newbie to subversion and it's hairy build process ;-) I cannot send
> patches and I am not even sure that I am right).
>
> Files INSTALL, HACKING and notes/dav_setup.txt are not simple to
> understand for beginner. Some of them refer to others and describe
> overlaying stages of build process. User has to jump over them and select
> parts to read and follow. It would be nice to have one file for instructions
> on how to install from working copy, one file describing what should be
> _additionally_ done for server version.
>
> Options passed to build utilities in examples should be described
> (what exactly means --enable-maintainer-mode ?). Each component of a product
> should be briefly described for USER. User has to understand what parts of
> system he needs without getting into details of its functioning. (If you
> need server part, you need: httpd-2.0, neon, etc). User should be able to
> figure out exact sequence of actions he should perform in 5 minutes of
> reading.
>
> Again, I am not flaming but trying to help development process of
> subversion as I'm yet new to it and my suggestions may help other users to
> stick with subversion. I would be glad to discuss points I've figured out in
> this posting and even contribute later when I'll get a bit deeper in all
> this stuff.
>
Don't worry about hurting our feelings (well not TOO much anyway:), and thanks
for the suggestion. Karl has already moved the notes/dav-setup to an html
page that is referenced all over the subversion website. As for the INSTALL
file, it tends to get things added to it as people report problems, perhaps
it is time for a complete rewrite.

Specifically --enable-maintainer-mode disables optimizations, and turns on
strict warning detection (at least if you are using gcc).

-- 
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Kevin Pilch-Bisson                    http://www.pilch-bisson.net
     "Historically speaking, the presences of wheels in Unix
     has never precluded their reinvention." - Larry Wall
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

  • application/pgp-signature attachment: stored
Received on Sat Oct 21 14:36:49 2006

This is an archived mail posted to the Subversion Dev mailing list.