From: O.Sezer <se...@gm...> - 2005-06-10 13:23:56
|
I get this error when trying to compile glide3 for cvg: make -f makefile.linux FX_GLIDE_HW=cvg [...] gcc -o fifo.o -Wall -W -I. -I../../incsrc -I../../init -I../../../swlibs/fxmisc -I../../../swlibs/newpci/pcilib -I../../../swlibs/fxmemmap -I../../../swlibs/te us2/lib -DINIT_LINUX -D__3Dfx_PCI_CFG__ -DGLIDE3 -DGLIDE3_ALPHA -DGLIDE_HW_TRI_SETUP=1 -DGLIDE_PACKED_RGB=0 -DGLIDE_PACKET3_TRI_SETUP=1 -DGLIDE_TRI_CULLING=1 -DUSE_PACKET_FIFO=1 -DGLIDE_DISPATCH_SETUP -DGLIDE_DISPATCH_DOWNLOAD -DCVG -DGLIDE_PLUG -DGLIDE_SPLASH -DGLIDE_USE_C_TRISETUP -O2 -ffast-math -c fifo.c fifo.c: In function `_FifoMakeRoom': fifo.c:662: structure has no member named `p6Fencer' fifo.c:526: warning: unused parameter `fName' fifo.c:526: warning: unused parameter `fLine' make[1]: *** [fifo.o] Error 1 If I use USE_X86=1, then the compilation finishes OK, but it crashes leaving my monitor black (in fact I never tried the USE_X86 option before). I think this is due the recent #if GL_X86 changes. I might steal a little time for tracing this if anyone wants me to, in which case I shall need some leads. Cheers, Ozkan Sezer |
From: Hans de G. <j.w...@hh...> - 2005-06-10 14:19:43
|
O.Sezer wrote: > I get this error when trying to compile glide3 for cvg: > > make -f makefile.linux FX_GLIDE_HW=cvg > [...] > gcc -o fifo.o -Wall -W -I. -I../../incsrc -I../../init > -I../../../swlibs/fxmisc > -I../../../swlibs/newpci/pcilib -I../../../swlibs/fxmemmap > -I../../../swlibs/te us2/lib -DINIT_LINUX -D__3Dfx_PCI_CFG__ -DGLIDE3 > -DGLIDE3_ALPHA -DGLIDE_HW_TRI_SETUP=1 -DGLIDE_PACKED_RGB=0 > -DGLIDE_PACKET3_TRI_SETUP=1 -DGLIDE_TRI_CULLING=1 -DUSE_PACKET_FIFO=1 > -DGLIDE_DISPATCH_SETUP -DGLIDE_DISPATCH_DOWNLOAD -DCVG -DGLIDE_PLUG > -DGLIDE_SPLASH -DGLIDE_USE_C_TRISETUP -O2 -ffast-math -c fifo.c > fifo.c: In function `_FifoMakeRoom': > fifo.c:662: structure has no member named `p6Fencer' > fifo.c:526: warning: unused parameter `fName' > fifo.c:526: warning: unused parameter `fLine' > make[1]: *** [fifo.o] Error 1 > Thanks for catching and reporting this. This should be fixed in CVS now. I have a cvg myself and I compile with USE_X86=1 (and all other bells and whistles enabled) and it works fine. On what platform and with which compiler are you compiling this? Regards, Hans |
From: O.Sezer <se...@gm...> - 2005-06-10 14:32:48
|
Hans de Goede wrote: > > > O.Sezer wrote: > >> I get this error when trying to compile glide3 for cvg: >> >> make -f makefile.linux FX_GLIDE_HW=cvg >> [...] >> gcc -o fifo.o -Wall -W -I. -I../../incsrc -I../../init >> -I../../../swlibs/fxmisc >> -I../../../swlibs/newpci/pcilib -I../../../swlibs/fxmemmap >> -I../../../swlibs/te us2/lib -DINIT_LINUX -D__3Dfx_PCI_CFG__ -DGLIDE3 >> -DGLIDE3_ALPHA -DGLIDE_HW_TRI_SETUP=1 -DGLIDE_PACKED_RGB=0 >> -DGLIDE_PACKET3_TRI_SETUP=1 -DGLIDE_TRI_CULLING=1 -DUSE_PACKET_FIFO=1 >> -DGLIDE_DISPATCH_SETUP -DGLIDE_DISPATCH_DOWNLOAD -DCVG -DGLIDE_PLUG >> -DGLIDE_SPLASH -DGLIDE_USE_C_TRISETUP -O2 -ffast-math -c fifo.c >> fifo.c: In function `_FifoMakeRoom': >> fifo.c:662: structure has no member named `p6Fencer' >> fifo.c:526: warning: unused parameter `fName' >> fifo.c:526: warning: unused parameter `fLine' >> make[1]: *** [fifo.o] Error 1 >> > > Thanks for catching and reporting this. This should be fixed in CVS now. > > I have a cvg myself and I compile with USE_X86=1 (and all other bells > and whistles enabled) and it works fine. On what platform and with which > compiler are you compiling this? > > Regards, > > Hans Thanks for the quick response. It is x86-linux (p3-533, no-name via-chipsetted board, redhat-7.3, gcc-2.96, nasm-0.98). I use mesa-6.2.1 compiled against glide3. I will try the latest cvs asap. Thanks agains, Ozkan Sezer |
From: Hans de G. <j.w...@hh...> - 2005-06-10 14:37:40
|
Hmm, Funny I'm using a very similar config: -FC4 (gcc-4.0.0) -Glide CVS -Mesa-6.2.1 ppracer (tuxracer) runs fine, I'll try recompiling glide with different options. Regards, Hans O.Sezer wrote: >> >> I have a cvg myself and I compile with USE_X86=1 (and all other bells >> and whistles enabled) and it works fine. On what platform and with >> which compiler are you compiling this? >> >> Regards, >> >> Hans > > > Thanks for the quick response. > > It is x86-linux (p3-533, no-name via-chipsetted board, > redhat-7.3, gcc-2.96, nasm-0.98). I use mesa-6.2.1 > compiled against glide3. I will try the latest cvs > asap. > > Thanks agains, > Ozkan Sezer > |
From: O.Sezer <se...@gm...> - 2005-06-10 14:52:20
|
The cvs seems not updated for anonymous access yet. BTW, does SLI work OK with that config? (spesifically mesa-6 + glide3 from -devel)? Ozkan Hans de Goede wrote: > Hmm, > > Funny I'm using a very similar config: > -FC4 (gcc-4.0.0) > -Glide CVS > -Mesa-6.2.1 > > ppracer (tuxracer) runs fine, > > I'll try recompiling glide with different options. > > Regards, > > Hans > > > O.Sezer wrote: > >>> >>> I have a cvg myself and I compile with USE_X86=1 (and all other bells >>> and whistles enabled) and it works fine. On what platform and with >>> which compiler are you compiling this? >>> >>> Regards, >>> >>> Hans >> >> >> >> Thanks for the quick response. >> >> It is x86-linux (p3-533, no-name via-chipsetted board, >> redhat-7.3, gcc-2.96, nasm-0.98). I use mesa-6.2.1 >> compiled against glide3. I will try the latest cvs >> asap. >> >> Thanks agains, >> Ozkan Sezer >> > |
From: Hans de G. <j.w...@hh...> - 2005-06-10 15:11:17
|
I've been trying Glide3-cvs without USE_X86=1, but that doesn't work. Now I understand why USE_X86=1 was forced in the makefile. So you really should use USE_X86=1. I'm trying yto get it to work without this, but I don't know if I'll succeed. Also nasm in Redhat used to have some problems and gcc-2.96 also might be a problem. When is the last time you got Glide3-cvs to work? Regards, Hans |
From: O.Sezer <se...@gm...> - 2005-06-10 15:18:40
|
Snapshot from 2005-04-04 works fine without USE_X86=1 (did all my development under it), didn't try with USE_X86. Ozkan Hans de Goede wrote: > I've been trying Glide3-cvs without USE_X86=1, but that doesn't work. > Now I understand why USE_X86=1 was forced in the makefile. So you really > should use USE_X86=1. > > I'm trying yto get it to work without this, but I don't know if I'll > succeed. > > Also nasm in Redhat used to have some problems and gcc-2.96 also might > be a problem. When is the last time you got Glide3-cvs to work? > > Regards, > > Hans > > |
From: Hans de G. <j.w...@hh...> - 2005-06-10 19:01:58
|
Hi, I now have fixed not only compilation but also linking of Glide3-cvs with cvg without USE_X86=1. I hope anon cvs syncs soon so you can test this. Please notice that in the past when you compiled Glide3-cvs for cvg you always got USE_X86=1, this was forced in the makefile because compiling without this set was broken. Besides that I wonder if you could also retest CVS with USE_X86=1 added, as this doesn't crash (works fine) for me. Regards, Hans |
From: O.Sezer <se...@gm...> - 2005-06-10 22:21:07
|
Hans de Goede wrote: > Hi, > > I now have fixed not only compilation but also linking of Glide3-cvs > with cvg without USE_X86=1. I hope anon cvs syncs soon so you can test > this. > > Please notice that in the past when you compiled Glide3-cvs for cvg you > always got USE_X86=1, this was forced in the makefile because compiling > without this set was broken. > > Besides that I wonder if you could also retest CVS with USE_X86=1 added, > as this doesn't crash (works fine) for me. > > Regards, > > Hans Hello Hans, This time my Voodoo2 works just fine with your latest changes using USE_X86=1. Thank you. Bad news is, Voodoo1 seems to need the same exorcism because, with the latest snapshot, it gives me a black screen without USE_X86. If using USE_X86, then my game (hexen2) starts-up fine, but when the first triangles are sent to the card, it just freezes. Snapshot from april 04 works fine (not using USE_X86, didn't try with it). Thanks again, Ozkan |
From: Hans de G. <j.w...@hh...> - 2005-06-11 06:28:11
|
O.Sezer wrote: > > Hello Hans, > > This time my Voodoo2 works just fine with your latest > changes using USE_X86=1. Thank you. Good to hear, but I didn't change anything when compiling with USE_X86=1 all the changes are #ifndef GL_X86 . I think that you probably did a make FX_GLIDE_HW=cvg realclean, or something which forced this and that this solved your problems. > Bad news is, Voodoo1 seems to need the same exorcism > because, with the latest snapshot, it gives me a black > screen without USE_X86. If using USE_X86, then my game > (hexen2) starts-up fine, but when the first triangles are > sent to the card, it just freezes. Snapshot from april > 04 works fine (not using USE_X86, didn't try with it). > Please try doing a "make FX_GLIDE_HW=sst1 realclean" before doing the normal make and try again. Regards, Hans |
From: O.Sezer <se...@gm...> - 2005-06-11 08:03:02
|
Hans de Goede wrote: >> This time my Voodoo2 works just fine with your latest >> changes using USE_X86=1. Thank you. > > > Good to hear, but I didn't change anything when compiling with USE_X86=1 > all the changes are #ifndef GL_X86 . I think that you probably did a > make FX_GLIDE_HW=cvg realclean, or something which forced this and that > this solved your problems. > >> Bad news is, Voodoo1 seems to need the same exorcism >> because, with the latest snapshot, it gives me a black >> screen without USE_X86. If using USE_X86, then my game >> (hexen2) starts-up fine, but when the first triangles are >> sent to the card, it just freezes. Snapshot from april >> 04 works fine (not using USE_X86, didn't try with it). >> > > Please try doing a "make FX_GLIDE_HW=sst1 realclean" before doing the > normal make and try again. Hi Hans, For Voodoo2, you may be right: My voodoo test box seems to have gone crazy and gave me a fried memory module yesterday, so my voodoo2 faults may be in error. As for the Voodoo1 case, no matter what I did I couldn't make 2005-06-10 snapshot to work. 2005-04-04: works with or without USE_X86=1 2005-06-10: without USE_X86: no way (black screen) with USE_X86: as I told before, as soon as I start drawing the scene the view freezes and I have to press ctrl+alt+backspace and then do a soft reboot to get my monitor back. In the log I got "FxMesa received unhandled signal 1" and "unhandled signal 15" Thanks, Ozkan |
From: Hans de G. <j.w...@hh...> - 2005-06-14 10:17:47
|
O.Sezer wrote: > As for the Voodoo1 case, no matter what I did I couldn't > make 2005-06-10 snapshot to work. > 2005-04-04: > works with or without USE_X86=1 > 2005-06-10: > without USE_X86: no way (black screen) > with USE_X86: as I told before, as soon as I start > drawing the scene the view freezes and I have to press > ctrl+alt+backspace and then do a soft reboot to get my > monitor back. In the log I got "FxMesa received unhandled > signal 1" and "unhandled signal 15" > I've checked the 04042005 Glide3 version out from CVS and I'm currently comparing a diff between the two. The first thing I've noticed is that I (accidently) changed the compiler flags from -O1 to -O2 can you edit sst1/glide3/src/makefile.linux and change the OPTFLAGS ?= -O2 -ffast-math -mcpu=pentium line to: OPTFLAGS ?= -O1 -ffast-math -mcpu=pentium Then do a realclean, followed by a build with USE_X86=1 set and test the result. That may explain your problems. I made this error because the other trees (h5 h3) do use -O2. I guess the -O1 in sst1 is there on purpose becaue -O2 miscompiles it? I hope this fixes it. Regards, Hans |
From: Hans de G. <j.w...@hh...> - 2005-06-16 19:02:30
|
O.Sezer wrote: > As for the Voodoo1 case, no matter what I did I couldn't > make 2005-06-10 snapshot to work. > 2005-04-04: > works with or without USE_X86=1 > 2005-06-10: > without USE_X86: no way (black screen) > with USE_X86: as I told before, as soon as I start > drawing the scene the view freezes and I have to press > ctrl+alt+backspace and then do a soft reboot to get my > monitor back. In the log I got "FxMesa received unhandled > signal 1" and "unhandled signal 15" > Hi, I've been busy carefully studying a diff between current CVS and that of 04042005 and I found I've introduced 2 bugs (BAD!). So this is entirely my fault. I did the warning fixes for sst1 last and I guess I was getting tired. Please checkout the latest CVS and try again with USE_X86=1 . Without USE_X86=1 has never been tested but this wat not nescesarry with the old version because the old version always assumed USE_X86=1. Regards, Hans |
From: O.Sezer <se...@gm...> - 2005-06-17 21:28:12
|
Hello Hans, Sorry for answering late, Hans de Goede wrote: > O.Sezer wrote: > >> As for the Voodoo1 case, no matter what I did I couldn't >> make 2005-06-10 snapshot to work. >> 2005-04-04: >> works with or without USE_X86=1 >> 2005-06-10: >> without USE_X86: no way (black screen) >> with USE_X86: as I told before, as soon as I start >> drawing the scene the view freezes and I have to press >> ctrl+alt+backspace and then do a soft reboot to get my >> monitor back. In the log I got "FxMesa received unhandled >> signal 1" and "unhandled signal 15" >> > > Hi, > > I've been busy carefully studying a diff between current CVS and that of > 04042005 and I found I've introduced 2 bugs (BAD!). So this is entirely > my fault. I did the warning fixes for sst1 last and I guess I was > getting tired. I now the story well ;) > Please checkout the latest CVS and try again with USE_X86=1 . Without > USE_X86=1 has never been tested but this wat not nescesarry with the old > version because the old version always assumed USE_X86=1. Latest -devel tree (including today's changes) seem to work fine for both voodoo2 and voodoo1 using X86=1. Thanks for your good work. Regards, Ozkan |
From: O.Sezer <se...@gm...> - 2005-08-26 19:35:49
|
Hello Hans, I's pretty sure this isn't something you intended, but my diff output says this: Binary files glide-devel-20050702/glide3x/cvg/glide3/tests/lava.3df and glide-devel-20050824/glide3x/cvg/glide3/tests/lava.3df differ FYI. Ozkan Sezer |