On Wed, Nov 21, 2012 at 7:37 AM, Eric S. Raymond <e...@thyrsus.com> wrote: > I have whatever I get from the wget recommended in the instructions printed > by configure.
configure doesn't tell you to wget APR and APR-UTIL it tells you to do a svn checkout. So it does appear that you have a dev checkout from the 1.3.x branches of those two, which is one of the suggestions that configure makes. The problem here is that APR's 1.3.x branch seems to be broken. Just doing a checkout of 1.3.x, buildconf, configure, make fails the same way. > I don't have any particular desire to do either of these things. What I want > is for the build instructions to be clear about what I have to do, and for the > build to succeed when I do it. Right now neither of those things is the case. Our directions are mostly fine though a tad out of date since 1.3.x is somewhat old. I've updated them to point to apr 1.4.x and apr-util 1.5.x the current release branches for those projects. I've also tried to make it clear that you should run buildconf in the directory. Using APR 1.4.x and APR-UTIL 1.5.x worked fine for me just now. So you should be good now. > Best would be if the configure script knew how to install these > components correctly and just did it, bothering me only when it > detects a failure. That's what get-deps.sh is for, which is mentioned in our INSTALL. However, I really don't understand the decisions you're making. You're choosing the least desirable options here. Using an in-tree build of APR et al is largely a legacy option in our build system for back when we used to provide a deps source package since the dependencies were somewhat exotic. Things have changed a lot and the dependencies are generally packaged by all the major distributions/operating systems out there. While I realize your current build isn't including httpd module support. If you ever want httpd modules, using an in-tree APR build is going to make things harder. You really don't want to build svn and httpd with different versions of APR (it may work but you may also run into very subtle things that don't work depending on which versions are built where, which I'm not going to get into here). Unless you have a specific need you ought to be fine just installing the packages provided by your distribution. Granted, distributions sometimes break things, I recently worked around a very poor choice Debian (and by extension Ubuntu) made on their APR-UTIL package that broke our detection of bdb. Unfortunately, given the large number of distributions and variations on package naming it's difficult to provide good instructions for the packages to install. HTH
