One mistake does not wreck the train.
I am going to Oregon for a few days, but will have access.
I will look at it again when I land later today.
Bobbau, I rolled back cmdline.h, what are the new errors. Start a new thread on this so we can sort it out. You STILL sound like you have manual conflicts you have to resolve. It only puts those >>>>> <<<<<<< in when there is such a thing.
I am splitting this thread from the "next build" one.
Check the version number on the cmdlin.h, it SHOULD say 2.10 and are the errors the same?
I am going to be equally constructive and say that most of this conversation SHOULD have taken place over some kind of real time chat.
Also, EVERY CHANGE IS DOCUMENTED. LOOK AT CVS. I don;t mean to be rude, but, we have the tools to make sure we can find these errors, and roll them back. The CVS weblog for each file exists, go look at the files giving you errors and make your own determination. Even the last committ where there were no comments in the logs SHOWS you there was a committ (and I have chastised the appropriate person for missing that, everyone makes mistakes).
So, Bob, help me out here and tell me if the same file is failing in the same place. We roll back till we get it right.
I land at 5:27 PST, probably check in around 6. I'll try compiling it on the plane and hopefully have some news.
RT: Did it compile for you?
DTP: How about you?
Anyone else?