[PyKDE] [PyKDE - offlist] Weird problem - gcc?

[Jim Bublitz]

I've been having a strange problem with a couple of new KDE 3.2.0 
files. They end up at the end of the list of %Includes, and if I 
leave them there, kdecorecmodule.cpp fails to compile. The error 
I get in both cases is in the middle of an enum in a Qt file 
(qdir.h in one case, qdockwindow.h in the other case). I get 
some error message about constants, and then the whole h file 
blows up (in the qdir case) or EVERYTHING blows up (qdockwindow 
case).

I fixed the kdecorecmodule problem by moving them earlier in the 
%Include list (same effect in cpp file), but the qdockwindow 
case still blows up when that (PyKDE) file's cpp code compiles.

I seem to remember having had similar unusual problems in the 
past, sometimes due to a missing header file or something 
similar. I can't find anything obvious in the present case, and 
the behaviour almost looks like a gcc bug (although I couldn't 
find anything like that either via google).

Just wondering if you've had any similar problems or if you have 
any suggestions about where to look next. Neither of these are 
QObject descendants, if that matters, and I've used the same 
distribution and gcc (3.3.1) to compile earlier PyKDE versions 
without a problem. Everything looks correct as far as I can see. 
gcc switches look OK too, I think.

Jim