building apr1 fails

[Michael Powell]

DA Forsyth wrote:

[snip] 
>> I just updated Apache to 2.2.15_5 yesterday and it builds fine when
>> the above mentioned option is turned off.

It was actually the day before yesterday, when it was still 2.2.15_5.
 
> Yes indeed, I upgraded the main server yesterday and it built fine
> except for having to turn 'mod_ssl' off as it kept dying in the ssl
> code.  I don't need ssl anyway.
> 
> However, today an update (cvsup) shows that that option has been
> removed entirely, I have just searched the Makefile to confirm it,
> also mentioned in UPDATING.

I see what you mean. I just csup'd and it is now apache-2.2.15_7, with the 
changes you described. So I just #'d out the WITHOUT_APR_FROM_PORTS=true 
line in my /var/db/ports/apache22/options file.

Tried a simple portupgrade -a which usually does the trick for upgrading 
Apache painlessly, but it completely bombed with errors.

> So now apache HAS to use devel/apr1 but apr1 will not compile with no
> real clue as to why not.

So I changed to /usr/ports/devel/apr1, built and installed this port 
manually to see if it would error out. It built and installed OK, pulling in 
some dependencies during the process.

So I then tried to manually upgrade apache-2.2.15_5 with the make deinstall 
&& make reinstall dance and it barfed because when apache compiles it builds 
the apr1 ports *again*. OK - so I pkg_deinstalled the apr1 install and did 
make clean for the apache build and started over. This time it built OK, and 
make deinstall && make reinstall succeeded. So now I somehow actually have 
upgraded to apache-2.2.15_7.
 
> I have just finished upgrading perl to 5.10.1, with a forced
> recompile of everything that depends on it, and of course
> apache22/apr still fails.
> 

Differences between us are that I am still using perl 5.8.9, and possibly I 
have an WITHOUT_X11= yes entry in my make.conf that you may not.

You might try and see if the apr1 port will build and install by itself. I'm 
also wondering if my installing it, then removing it somehow left behind a 
file that the apache build process was expecting to be present. I recall 
somewhere in the process something complained that apr-1-config could not be 
found. The apr1 port does need to be removed because apache build will 
rebuild it a second time and bomb trying to install it if the port is 
already installed.

As to exactly *why* I eventually succeeded I'm not entirely clear.  :-)

-Mike