Hello, Stas, I didn't take offense at your first reply. Steven, I'm sorry if my post was in any way insulting or otherwise offensive.
Stas, I do understand - more with every piece of code I add to my box - that the xnix world and esp. the open source core of that world is a constantly shifting one. So, I have updated my src of apache, arp and mod_perl2 from cvs. Still the exact same result. Thanks, Daren ---- Steven Adams <[EMAIL PROTECTED]> wrote: > Is there a reason that we have to be this insulting? > > Beckman, I really expected more out of you. > > > > LD_RUN_PATH="/usr/lib" gcc -shared -L/usr/local/lib APR.o -o > > > ../../../blib/arch/Apache2/auto/APR/APR.so > > > -L/usr/local/apache2/2.0.43/lib -lapr -laprutil > > > /usr/bin/ld: cannot find -lapr > > > collect2: ld returned 1 exit status > > > make[3]: *** [../../../blib/arch/Apache2/auto/APR/APR.so] Error 1 > > > > [...] > > > > > And I've had an "Apache Head" check my installs, configs, versions, lib's > > > & processes. > > > So far everything checks out fine. !?! But, mod-perl still won't > > > compile and neither will apr-util. > > > > As repeated many times here, mod_perl builds on top of other components > > that just keep on changing (one of the reasons why a production mod_perl > > can't be released). So if you take a released version of mod_perl, it > > *will* build and work with the apr/apache released at about the same date. > > If you use any later releases/cvs of these components and a new version of > > mod_perl wasn't yet released, you *must* use the cvs version of mod_perl, > > as it adjusts on the go to the latest changes in the components it uses. > > > > In short, you need the latest mod_perl from cvs. > > > > http://perl.apache.org/docs/2.0/user/install/install.html#Installing_mod_pe > >rl_from_Source (scroll down to the CVS Bleeding-Edge Version) > > > > re: problems with building apr, email the apr list directly. > > >
