Problems with 5.0 upgrade and Apache

[Whit Blauvelt <whit transpect com>]

 Upgrading to 5.0, but not upgrading the kernel (I was already running a
 customized 2.0.30 I was happy with, and have now upgraded to 2.0.33) or
 Apache (likewise I have a customized version I want to stay with) has
 resulted in Apache dumping core. And attempts to do a fresh compile of
 Apache fail (even after installing the kernel-headers rpm - which solved
 some initial compile problems). It looks like this is a libraries problem.
 Is there an obvious solution? 

 Although performance is in some respects obviously improved running 5.0
 instead of 4.2, the upgrade process is still too much of a problem when
 the system being upgraded isn't purely stock. For one thing, 5.0 insisted
 on upgrading my sendmail, even though I had specifically unselected it.
 This wasn't the only package that went ahead and installed unselected.

 But this Apache problem is serious for me, since a primary use of the
 system is to perfect PHP scripts against Apache which I then export to
 external hosts - and I need to be able to run a version of Apache I've set
 up to exactly mirror the configuration on those hosts. Having a program as
 well-constructed and thoroughly-tested as Apache neither run nor compile
 under 5.0 is a bit of a problem. IMHO a primary design goal for Redhat
 should be to have a standard-enough Linux that custom compilation of
 standard packages from their tar distributions should rarely fail.

 Hopefully there's an easy fix that does not require reinstalling through
 the 5.0 upgrade script - I don't want to again clobber things like
 sendmail that I've already fixed.


 \/\/ I-I I T 
 Blauvelt
 whit transpect com