... is the question that prompted my post, but this has come up before. Sure, he's using an old server OS and basically working around self-inflicted limitations, but most of us have been in a similar situation at some point: patching up old systems to keep them going just little bit longer.
In this case, part of the problem is that the OP's phrasing made it sound like he wasn't the admin of the box and it took some back and forth in comment for that critical detail to come out: the OP is administering the box he's talking about.
But even so, I think we're sometimes too quick to say "it's not professional to use such an old version" or "it's not professional to use (that software) in production" or whatever. If there's a reasonable solution (in this case, some hints for how to compile Apache), the OP should be told of it.
That's not to say that "don't do that" is a bad answer. It's perfectly valid for someone to answer "a better solution would be to upgrade your software" (OS in this case), or "don't use that software for that task." (VirtualBox in production).