"latest" really is quite vague and can be invalid in an hour already (if not less). Usually revision numbers are of more help. Especially in this case I believe this particular error is fixed by Per in revision 1370, which I believe was committed just under half an hour before you posted this.
shimitar wrote:
So what should i do? I tried to set "-Wno_error" in my CFLAG but does not change a bit....
You might want to try using --enable-debug=relaxed instead of --enable-debug=yes this allows compiling with warnings (apart from that it's the same).
"First make sure it works good, only then make it look good." -- Giel
Want to tip/donate? bitcoin:1EaqP4ZPMvUffazTxm7stoduhprzeabeFh
Ok, i tried 2.0.7. No much more luck. Now i can start the game, start a new campaign, see the black intro screen with the text, then start loading the map, then bails out with the same kind of errors as before.
I gues there is come endianess incompatibility in warzone code, probably in some image loading or manipulation code...
2.0.7 is _not_ 64bit safe. Endianness might be a problem for some files, but most certainly not for PNG image files, nor the .img data files. But I think we've got plenty of other binary file formats for files to crop up.
"First make sure it works good, only then make it look good." -- Giel
Want to tip/donate? bitcoin:1EaqP4ZPMvUffazTxm7stoduhprzeabeFh
I tried with the -m32 switch. Unfortunately, it still crashes at the very same point with a "bus error" message. This usually identifies an endianess problem in the code, like a pointer, a cast, or similar.
By the way, since i have no OpenGL hardware (waiting for a Matrox G200 PCI, as soon as i can find one!), the game would be too slow. But its a nice experiment the same.