Warzone2100 on Sparc64 (Linux)

Do you need help? Ask here!

Bug reporting belongs here: http://developer.wz2100.net/newticket
shimitar
Greenhorn
Posts: 9
Joined: 24 May 2007, 15:02

Re: Warzone2100 on Sparc64 (Linux)

Post by shimitar »

From the latest svn:

Code: Select all

ar cru libsequence.a adpcm.o dec130.o rpl_reader.o sequence_stub.o ../../lib/framework/libframework.a
ranlib libsequence.a
make[3]: Leaving directory `/home/willy/warzone/lib/sequence'
Making all in ivis_common
make[3]: Entering directory `/home/willy/warzone/lib/ivis_common'
gcc -DHAVE_CONFIG_H -I. -I../..   -I../..  -mcpu=ultrasparc -mtune=ultrasparc -O2 -pipe -Wno-error -D__BIG_ENDIAN__  -O0 -g -DDEBUG -Wall -Wno-nonnull -Wno-unused-label -Werror -I/usr/include/SDL -D_GNU_SOURCE=1 -D_REENTRANT -I/usr/X11R6/include/SDL -DYY_STATIC -DLOCALEDIR=\"/home/willy/warzone2100/share/locale\" -DDATADIR=\"/home/willy/warzone2100/share/warzone2100\" -MT bitimage.o -MD -MP -MF .deps/bitimage.Tpo -c -o bitimage.o bitimage.c
cc1: warnings being treated as errors
bitimage.c: In function 'iV_LoadImageFile':
bitimage.c:109: warning: pointer targets in passing argument 1 of 'LoadTextureFile' differ in signedness
make[3]: *** [bitimage.o] Error 1
make[3]: Leaving directory `/home/willy/warzone/lib/ivis_common'
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory `/home/willy/warzone/lib'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/home/willy/warzone'
make: *** [all] Error 2
So what should i do? I tried to set "-Wno_error" in my CFLAG but does not change a bit....

// Edit: Giel: use code-tags instead of quote
Last edited by Giel on 29 May 2007, 00:29, edited 1 time in total.
Giel
Regular
Regular
Posts: 725
Joined: 26 Dec 2006, 19:18
Contact:

Re: Warzone2100 on Sparc64 (Linux)

Post by Giel »

shimitar wrote: From the latest svn:
"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
shimitar
Greenhorn
Posts: 9
Joined: 24 May 2007, 15:02

Re: Warzone2100 on Sparc64 (Linux)

Post by shimitar »

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...
Giel
Regular
Regular
Posts: 725
Joined: 26 Dec 2006, 19:18
Contact:

Re: Warzone2100 on Sparc64 (Linux)

Post by Giel »

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
User avatar
kage
Regular
Regular
Posts: 751
Joined: 05 Dec 2006, 21:45

Re: Warzone2100 on Sparc64 (Linux)

Post by kage »

i guess the question is... does sparc64's gcc (and proc) support the -m32 switch?
shimitar
Greenhorn
Posts: 9
Joined: 24 May 2007, 15:02

Re: Warzone2100 on Sparc64 (Linux)

Post by shimitar »

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.
Post Reply