Re: Build problem

[<br...@ph...>]

Ethan A Merritt wrote:

> The patch was not correct. Instead the changes of 2006-06-11 should
> have been reverted entirely.  Unfortunately, I don't know how to issue
> a "revert to verion xxx" command in cvs.  Is that even possible?

Not directly.  But see the -j <rev|date> option of 'cvs update'.  That 
one allows you to check get a version with all changes between to given 
ones applied to it.  So

	cvs update -j 1.25 -j 1.23 file.ext

will revert all the changes from revision 1.23 to revision 1.25 of that 
file.  As an alternative, you can check out a given old revision,
remove the sticky revision state, and check it back in as new.

[gcc -Wuninitialized warnings]

> I've been getting all 3 of those for a long time now.
> They are all false alarms, and highly dependent on the precise gcc version
> being used.  I don't know of any way to make gcc more accurate in such cases.

Well, just initialize them!  Worst that can happen is that the code 
gratuitously grows by 3 'load value into variable' operations.  *If* 
they're actually false alarms, that is.