On Fri, 8 Jul 2011, Emmanuel Noobadmin wrote: > Mr Hodrien already demonstrated how to provide the information. Could > you not at least follow suit, copy and paste the relevant commands > leading up to the problem? If you had done so, he would had known the > problem occurred after that point and might had actually went past > when he stopped to see if he was going to get the same problem. But > because you refused to provide any information, he or anybody else > probably won't be bothered to waste time shooting blindly hoping to > reach the step where you got stuck. I was curious, so *did* find out what the cause was, and it's entirely not CentOS's fault. It's very hard to shoot blindly given that the cause was likely not to be CentOS. That only left his autoconf files, and tracing configure made it quite easy to find. jh