Jeremy Pereira wrote:
>
> On 24 Oct 2007, at 19:54, Kevin Tomasek wrote:
>
> >
> > the intended audience for the use of svn is only our local
> > network. i don't believe that i really need the apache stuff
> > functional. i can see the configure switch that is supposed to
> > change the httpd.conf file to disable the mod_dav sections. i
> > don't know if this will stop the install of this stuff into /usr/lib64
> >
> > questions:
> > i wish to build this for general consumption. ie i don't want to
> > go to 20 machines to build svn and update each ones 'local' /usr/
> > lib64 directory. is this possible?
> >
> > i don't wish to install as root. is there some way to bypass the /
> > usr/lib64 install sections?
> > why does it look at /usr/lib64? couldn't it use the --
> > prefix=<install_root>/lib64 ??
> > is there a good solution to this or am i missing something completely?
>
>
> I had no problem building subversion into my home directory, but than
> I had previously built Apache also into my home directory so I didn't
> run into those permission issues. I'm guessing a bit, but I think
> your problem is that --prefix is being ignored because the install
> process thinks the Apache modules should go in the directory where
> Apache expects them to be (not an unreasonable assumption IMO).
>
> Looking at configure --help, you could try configuring with --without-
> apxs and --without-apache
>
excellent suggestion!!
that caused the issue to go away. installed and running. thanks.
even though i used the without switches i still had to tell configure
where the apr and apr-utils were.
> >
> >
> > kevin
>
Received on Thu Oct 25 17:45:36 2007