On Feb 11, 9:17pm, m...@eterna.com.au (matthew green) wrote: -- Subject: re: CVS commit: xsrc/external/mit/xorg-server/dist/hw/xfree86/com
| so, to enable warnings you have to fix the code, which will make | updating it harder later. It is just 4 lines, and the cast was wrong (it takes away volatile from a pointer which is passed into a function that takes a volatile!). | can you just not enable the warnings? i'm hoping to update this | unfortunately some what out of date code base (xorg-server) soon, | and going on what i've seen lately, basically *every local change* | will cause conflicts. i wish i was being hyperbolic :-( So instead of fixing the bug, we should silence the warnings, just because there is a slight chance that there will be a conflict in a future import? I prefer to ask upstream to fix it, together with the other bug I found the other day. christos
