Debian the dri-devel snapshots
The DRI snapshots can be used with the Xorg packages in Debian experimental. I've edited the wiki to reflect this. Hope that's OK! I've got the r200 snapshot working happily[1]. cheers, Phil [1] PageFlip seems broken however -- rendering errors with Quake4[2] at least, which go away when PageFlip is turned off. [2] No, Quake4 is not playable with an r200 :) -- http://www.kantaka.co.uk/ .oOo. public key: http://www.kantaka.co.uk/gpg.txt --- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_id=7637alloc_id=16865op=click -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: Debian the dri-devel snapshots
The DRI snapshots can be used with the Xorg packages in Debian experimental. I've edited the wiki to reflect this. Hope that's OK! I've got the r200 snapshot working happily[1]. cheers, Phil [1] PageFlip seems broken however -- rendering errors with Quake4[2] at least, which go away when PageFlip is turned off. [2] No, Quake4 is not playable with an r200 :) Depends on what you mean by playable. The framerate sucks, there are definite graphical glitches, but the game launches and loads the first level, at least :-) Adam --- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_id=7637alloc_id=16865op=click -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
[Dri-devel] Snapshots broken due to missing texutil.h
Hi, snapshots are broken due to a missing texutil.h: gcc-3.3 -c -O2 -gstabs+ -ansi -pedantic -Wall -Wpointer-arith -Wstrict-prototypes -Wmissing-prototypes -Wmissing-declarations -Wredundant-decls -Wnested-externs -Wundef -pipe -g -I../../../../../../exports/include/X11 -I../../../../../../include/extensions -I/home/projects/dri/snapshots/src/Mesa/src/mesa -I/home/projects/dri/snapshots/src/Mesa/src/mesa/main -I/home/projects/dri/snapshots/src/Mesa/src/mesa/glapi -I/home/projects/dri/snapshots/src/Mesa/src/mesa/shader -I/home/projects/dri/snapshots/src/Mesa/include -I/home/projects/dri/snapshots/src/Mesa/src/mesa/drivers/dri/common -I/home/projects/dri/snapshots/src/Mesa/src/mesa/drivers/dri/i830 -I../../../../../../lib/GL/dri-I../../../../../../exports/include/X11 -I../../../../../../lib/GL/glx -I../../../../../../lib/GL/include -I../../../../../../programs/Xserver/GL/dri -I../../../../../../programs/Xserver/hw/xfree86/os-support -I/home/projects/dri/snapshots/src/drm/shared -I../../../../../../programs/Xserver/hw/xfree86/drivers/i810 -I../../../../../../lib/GL/dri/drm -I../../../../../.. -I../../../../../../exports/include -I/usr/X11R6/include -Dlinux -D__i386__ -D_POSIX_C_SOURCE=199309L -D_POSIX_SOURCE -D_XOPEN_SOURCE -D_BSD_SOURCE -D_SVID_SOURCE -D_GNU_SOURCE -DFUNCPROTO=15 -DNARROWPROTO -DXTHREADS -D_REENTRANT -DXUSE_MTSAFE_API-DMALLOC_0_RETURNS_NULL -DGLXEXT -DXF86DRI -DGLX_DIRECT_RENDERING -DGLX_USE_DLOPEN -DGLX_USE_MESA -DUSE_X86_ASM -DUSE_MMX_ASM -DUSE_3DNOW_ASM -DUSE_SSE_ASM i830_texstate.c i830_texstate.c:45:21: texutil.h: No such file or directory make[6]: *** [i830_texstate.o] Error 1 make[6]: Leaving directory `/home/fxkuehl/snapshots/build/HEAD/xc/lib/GL/mesa/drivers/dri/i830' make[5]: *** [all] Error 2 make[5]: Leaving directory `/home/fxkuehl/snapshots/build/HEAD/xc/lib/GL/mesa/drivers/dri' make[4]: *** [all] Error 2 make[4]: Leaving directory `/home/fxkuehl/snapshots/build/HEAD/xc/lib/GL' make[3]: *** [all] Error 2 make[3]: Leaving directory `/home/fxkuehl/snapshots/build/HEAD/xc/lib' make[2]: *** [all] Error 2 make[2]: Leaving directory `/home/fxkuehl/snapshots/build/HEAD/xc' make[1]: *** [World] Error 2 make[1]: Leaving directory `/home/fxkuehl/snapshots/build/HEAD/xc' make: *** [World] Error 2 make: Leaving directory `/home/fxkuehl/snapshots/build/HEAD/xc' I suppose this is related to Brian's new texture management code. It looks like the i830 driver (and maybe others) need to be updated. Regards, Felix --- This SF.net email is sponsored by: The Robotic Monkeys at ThinkGeek For a limited time only, get FREE Ground shipping on all orders of $35 or more. Hurry up and shop folks, this offer expires April 30th! http://www.thinkgeek.com/freeshipping/?cpg=12297 -- ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-devel] Snapshots
Just to let everybody know that all snapshots are failing ATM. I get the following error on all logs: gcc -m32 -o xf86cfg -O2 -fno-strength-reduce -fno-strict-aliasing -ansi -pedantic -Wall -Wpointer-arith -Wstrict-prototypes -Wmissing-prototypes -Wmissing-declarations -Wredundant-decls -Wnested-externs -Wundef -pipe -g -L../../../../../exports/lib -L/usr/X11R6/lib accessx.ocards.o config.ocard-cfg.o expert.o help.o interface.o keyboard-cfg.o libc_wrapper.o loader.o loadmod.o monitor-cfg.o mouse-cfg.o options.o screen-cfg.oscreen.o startx.ostubs.o text-mode.o vidmode.o xf86config.o -lxkbui -lxkbfile -lxf86config -lXxf86misc -lXxf86vm -lXaw -lXmu -lXt -lSM -lICE -lXext -lX11 -lXt -lSM -lICE -lXpm -L../loader -lxloader -L../dummylib -ldummy -rdynamic -ldl -lXext -lX11 -lncurses -lm -Wl,-rpath-link,../../../../../exports/lib help.o(.text+0x9f): In function `Help': /home/jfonseca/projects/dri/snapshots/build/HEAD/xc/programs/Xserver/hw/xfree86/xf86cfg/help.c:81: undefined reference to `XawTextSourceClearEntities' help.o(.text+0x3bd): In function `StartHelp': /home/jfonseca/projects/dri/snapshots/build/HEAD/xc/programs/Xserver/hw/xfree86/xf86cfg/help.c:141: undefined reference to `XawTextSinkConvertPropertyList' help.o(.text+0x94a): In function `Html_ModeEnd': /home/jfonseca/projects/dri/snapshots/build/HEAD/xc/programs/Xserver/hw/xfree86/xf86cfg/help.c:536: undefined reference to `XawTextSourceClearEntities' help.o(.text+0xce4): In function `Html_AddEntities': /home/jfonseca/projects/dri/snapshots/build/HEAD/xc/programs/Xserver/hw/xfree86/xf86cfg/help.c:637: undefined reference to `XawTextSinkCopyProperty' help.o(.text+0xd18):/home/jfonseca/projects/dri/snapshots/build/HEAD/xc/programs/Xserver/hw/xfree86/xf86cfg/help.c:641: undefined reference to `XawTextSinkGetProperty' help.o(.text+0xd34):/home/jfonseca/projects/dri/snapshots/build/HEAD/xc/programs/Xserver/hw/xfree86/xf86cfg/help.c:641: undefined reference to `XawTextSinkCombineProperty' help.o(.text+0xd63):/home/jfonseca/projects/dri/snapshots/build/HEAD/xc/programs/Xserver/hw/xfree86/xf86cfg/help.c:651: undefined reference to `XawTextSinkAddProperty' help.o(.text+0xe75):/home/jfonseca/projects/dri/snapshots/build/HEAD/xc/programs/Xserver/hw/xfree86/xf86cfg/help.c:687: undefined reference to `XawTextSourceAddEntity' help.o(.text+0xeea):/home/jfonseca/projects/dri/snapshots/build/HEAD/xc/programs/Xserver/hw/xfree86/xf86cfg/help.c:691: undefined reference to `XawTextSourceAddEntity' help.o(.text+0xf4c):/home/jfonseca/projects/dri/snapshots/build/HEAD/xc/programs/Xserver/hw/xfree86/xf86cfg/help.c:649: undefined reference to `XawTextSinkCombineProperty' help.o(.text+0xf6e):/home/jfonseca/projects/dri/snapshots/build/HEAD/xc/programs/Xserver/hw/xfree86/xf86cfg/help.c:644: undefined reference to `XawTextSinkCombineProperty' help.o(.text+0x1065): In function `Html_Commit': /home/jfonseca/projects/dri/snapshots/build/HEAD/xc/programs/Xserver/hw/xfree86/xf86cfg/help.c:774: undefined reference to `XawTextSourceAddEntity' help.o(.text+0x2dd3): In function `Html_AArgs': /home/jfonseca/projects/dri/snapshots/build/HEAD/xc/programs/Xserver/hw/xfree86/xf86cfg/help.c:1583: undefined reference to `XawTextSinkCopyProperty' help.o(.text+0x2e37): In function `Html_FontArgs': /home/jfonseca/projects/dri/snapshots/build/HEAD/xc/programs/Xserver/hw/xfree86/xf86cfg/help.c:1606: undefined reference to `XawTextSinkCopyProperty' collect2: ld returned 1 exit status I really don't know what changed on my system to cause this, but it seems better to upload to XFree 4.3.0 on Debian experimental to avoid rebuilding all the X server. This will take a couple of days so no snapshots until then. Jose Fonseca --- This SF.net email is sponsored by: SF.net Giveback Program. SourceForge.net hosts over 70,000 Open Source Projects. See the people who have HELPED US provide better services: Click here: http://sourceforge.net/supporters.php ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-devel] Snapshots
On Tue, 2003-10-14 at 00:37, Jos Fonseca wrote: Just to let everybody know that all snapshots are failing ATM. I get the following error on all logs: gcc -m32 -o xf86cfg -O2 -fno-strength-reduce -fno-strict-aliasing -ansi -pedantic -Wall -Wpointer-arith -Wstrict-prototypes -Wmissing-prototypes -Wmissing-declarations -Wredundant-decls -Wnested-externs -Wundef -pipe -g -L../../../../../exports/lib -L/usr/X11R6/lib accessx.o cards.o config.ocard-cfg.o expert.o help.o interface.o keyboard-cfg.o libc_wrapper.o loader.o loadmod.o monitor-cfg.o mouse-cfg.o options.o screen-cfg.oscreen.o startx.ostubs.o text-mode.o vidmode.o xf86config.o -lxkbui -lxkbfile -lxf86config -lXxf86misc -lXxf86vm -lXaw -lXmu -lXt -lSM -lICE -lXext -lX11 -lXt -lSM -lICE -lXpm -L../loader -lxloader -L../dummylib -ldummy -rdynamic -ldl -lXext -lX11 -lncurses -lm -Wl,-rpath-link,../../../../../exports/lib help.o(.text+0x9f): In function `Help': /home/jfonseca/projects/dri/snapshots/build/HEAD/xc/programs/Xserver/hw/xfree86/xf86cfg/help.c:81: undefined reference to `XawTextSourceClearEntities' You don't need xf86cfg for the snapshots, do you? I always build with #define BuildXFree86ConfigTools NO in host.def (maybe it should be that way in the repository?). -- Earthling Michel Dnzer \ Debian (powerpc), XFree86 and DRI developer Software libre enthusiast \ http://svcs.affero.net/rm.php?r=daenzer --- This SF.net email is sponsored by: SF.net Giveback Program. SourceForge.net hosts over 70,000 Open Source Projects. See the people who have HELPED US provide better services: Click here: http://sourceforge.net/supporters.php ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
[Dri-devel] Snapshots
Hi, there were 2 reports from snapshot users on dri-users that DRI was disabled with the new configuration stuff. In at least one case the problem was that libexpat was not installed on the system. Could the snapshot build be changed to link the drivers statically with libexpat? In either case I'll add a note in the FAQ. On a related note, there seem to be no trunk snapshots. Only in bleeding-edge there are snapshots available. Regards, Felix __\|/_____ ___ - Felix ___\_e -_/___/ __\___/ __\_ You can do anything, Kühling (_\Ä// /_/ /) just not everything [EMAIL PROTECTED] \___/ \___/ Uat the same time. --- This SF.net email is sponsored by: SF.net Giveback Program. SourceForge.net hosts over 70,000 Open Source Projects. See the people who have HELPED US provide better services: Click here: http://sourceforge.net/supporters.php ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-devel] Snapshots
Felix, On Fri, Oct 10, 2003 at 10:06:51AM +0200, Felix Kühling wrote: Hi, there were 2 reports from snapshot users on dri-users that DRI was disabled with the new configuration stuff. In at least one case the problem was that libexpat was not installed on the system. Could the snapshot build be changed to link the drivers statically with libexpat? In either case I'll add a note in the FAQ. I suppose so. Does any body here knows how to specify which library (static or dynamic) the linker should use? (I always just do -lname and never thought much about it...) On a related note, there seem to be no trunk snapshots. Only in bleeding-edge there are snapshots available. I checked the logs. It was breaking because the Xaw headers couldn't be found on my system. It should be fixed now. Jose Fonseca --- This SF.net email is sponsored by: SF.net Giveback Program. SourceForge.net hosts over 70,000 Open Source Projects. See the people who have HELPED US provide better services: Click here: http://sourceforge.net/supporters.php ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-devel] Snapshots
On Fri, 10 Oct 2003 10:17:23 +0100 José Fonseca [EMAIL PROTECTED] wrote: Felix, On Fri, Oct 10, 2003 at 10:06:51AM +0200, Felix Kühling wrote: Hi, there were 2 reports from snapshot users on dri-users that DRI was disabled with the new configuration stuff. In at least one case the problem was that libexpat was not installed on the system. Could the snapshot build be changed to link the drivers statically with libexpat? In either case I'll add a note in the FAQ. I suppose so. Does any body here knows how to specify which library (static or dynamic) the linker should use? (I always just do -lname and never thought much about it...) The linker option for libexpat is defined in config/cf/X11.tmpl. You could try changing EXPATLIB = -lexpat to EXPATLIB = -Wl,-Bstatic -lexpat -Wl,-Bdynamic On a related note, there seem to be no trunk snapshots. Only in bleeding-edge there are snapshots available. I checked the logs. It was breaking because the Xaw headers couldn't be found on my system. It should be fixed now. It had one positive side effect, people were actually using the config snapshots. ;-) Jose Fonseca Felix __\|/_____ ___ - Felix ___\_e -_/___/ __\___/ __\_ You can do anything, Kühling (_\Ä// /_/ /) just not everything [EMAIL PROTECTED] \___/ \___/ Uat the same time. --- This SF.net email is sponsored by: SF.net Giveback Program. SourceForge.net hosts over 70,000 Open Source Projects. See the people who have HELPED US provide better services: Click here: http://sourceforge.net/supporters.php ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
[Dri-devel] snapshots
Should we stop producing snapshots temporarily until the xaa/compiler/who-knows-what problems are resolved? There seem to be a lot of complaints about the ones up there now... Keith --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-devel] snapshots
On Sat, Sep 28, 2002 at 03:24:56PM +0100, Keith Whitwell wrote: Should we stop producing snapshots temporarily until the xaa/compiler/who-knows-what problems are resolved? There seem to be a lot of complaints about the ones up there now... Keith I have no problem stopping the snapshot builds, but that won't do help much as people will probably download the latest available. We also haven't recived feedback regarding non-radeon cards. Spite of that, I'm going now try to obtain snapshots using RedHat's compat-gcc and put them in a seperate dir so that we can seperate the two distinct changes happening here: XAA binary compatibility and gcc 3.2. I'll announce it when done. José Fonseca --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-devel] snapshots
We also haven't recived feedback regarding non-radeon cards. I would be happy to give some feedback on mach64 - but I am using Leif's spanshots now (2.96-built AFAIK) - just because they give me xvideo. Leif, are you still using 2.96 or moving to 3.x? Regards, Sergey --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-devel] snapshots
I'm using 2.96, so I think I may have to start including all the DRI stuff in my patched XV binaries to avoid binary compatibility problems. This can also be caused by changes to the SAREA in the DRI branch, so I think it might be easier to keep things in sync that way. I got one report from someone who was having problems with mach64_dri.so, maybe a glibc version mismatch problem? He said using LIBGL_DEBUG with glxinfo indicated that mach64_dri.so needed glibc 2.3. My binaries are built with glibc 2.2.4, but I'm not sure yet if that was the problem. Again this was with my patched X sever binaries on top of the DRI snapshot. I haven't tried the snapshots and I haven't heard from anyone using the vanilla snapshots without my patches yet, so I'm not sure if there are any problems there. --Leif On 28 Sep 2002, Sergey V. Udaltsov wrote: We also haven't recived feedback regarding non-radeon cards. I would be happy to give some feedback on mach64 - but I am using Leif's spanshots now (2.96-built AFAIK) - just because they give me xvideo. Leif, are you still using 2.96 or moving to 3.x? Regards, Sergey --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel -- Leif Delgass http://www.retinalburn.net --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-devel] snapshots
I haven't tried the snapshots and I haven't heard from anyone using the vanilla snapshots without my patches yet, so I'm not sure if there are any problems there. Well, at least I can confirm that in my mostly 3.1-based system (at least the kernel and XFree are 3.1-built) your 2.96-based snapshots do work without any hassle. So probably 3.x snapshots would not be that bad for 2.96 folks?... Sergey --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-devel] Snapshots now being built with gcc 3.2
On Fri, 2002-09-27 at 04:25, Andy Dustman wrote: Still getting the same problem with the r200. Interestingly, the amount of memory used for textures has gone up recently, from about 93 MB to 113 MB. Most obvious feature of this is what looks like a NULL pointer reference at the end. Also there is a load/unload/load of the xaa module. (WW) module minor version (0) is less than the required minor version (1) Hmmm, Michel, is this what you expect? Andy, you can download from my site http://cpotha.net/dri_resume.html my latest snapshot just for the included libxaa.a and libGL* - copy these out over your dri.sf.net installation. One other thing: There is a variable in the dripkg.sh script, PKG_MINIMAL=1, which is causing GL and core libraries not to be included the snapshot. Commenting this out reveals that the non-shared libraries are not getting built anyway. As above, you can get more up to date libGL.* thingies from my snapshot. HTH, Charl -- charl p. botha http://cpbotha.net/ http://visualisation.tudelft.nl/ --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-devel] Snapshots now being built with gcc 3.2
On Wed, Sep 25, 2002 at 10:32:32PM -0400, Andy Dustman wrote: On Tue, 2002-09-24 at 09:25, José Fonseca wrote: I've updated my workstation to the RedHat Linux 7.3.94 beta, which has gcc 3.2. So now forward the snapshots will be built with this version. AFAIK this shouldn't pose any problem to the users since the key issue is that the kernel modules are compiled with the same version of gcc that compiled the kernel, and that still holds true. If the kernel modules were the only issue, you'd be right. Unfortunately the other important component of the snapshots is the DRI shared library. Since (for those who haven't heard) GCC 3.2 breaks binary compatibility with earlier versions, the shared libraries don't work. My X server dies on signal 11 almost immediately (during drm initialization). So these snapshots will only work if your X server is compiled with GCC 3.2. Also I've noticed that the shared library is now twice the size (or more) than it used to be (went from about 5 MB to 12 MB). AFAIK the announced breakeage concerned C++ only. Since very few people seem to have GCC 3.2 at the moment (I do have a Gentoo 1.4-pre1 box that does, but haven't tried DRI snaps on it yet), can we please have some built with the old gcc? Most likely Red Hat provides this in a gcc-compat package. I'm trying now to build some myself from CVS, but didn't have much luck last night (result didn't run). The ability of gcc-3.2 to generate more efficient code to Pentium III and IV, being able to generate SSE and SSE2 instructions automatically was one of the main reasons why I installed Redhat beta, since I do lot of numerical stuff. This together with the new gnome2 desktop. Unfortunately I don't have other machine were I can build those snapshots, and SourceForge compiler farm fails to build the snapshots except for some cards (ATI cards IIRC) due to an outdate Xfree installed on the system. RedHat does indeed provides a compat-gcc package. I'll see what I can do to use it within my scripts. Nevertheless it would be good to be sure about these binary compatabilities, since the widespread of gcc-3.2 will happen very soon. José Fonseca --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-devel] Snapshots now being built with gcc 3.2
On Thu, 2002-09-26 at 03:40, Charl P. Botha wrote: serious note, have you tried replacing your libxaa.a yet to eliminate the possibility of that signal 11 that we've been seeing with the last few snapshots? You could also try a snapshot of today or later, because Michel has fixed the XAA problem which resulted in the Sig11. I'll certainly try another snapshot. My own snapshot attempt at last night looks like it had nearly the same signal 11 problem, although it got slightly further than the snapshots on the websites. Neither one actually crashes the machine, but the video goes dead: The monitor no longer syncs up and switching VTs doesn't help. -- Andy Dustman PGP: 0x930B8AB6 @ .net http://dustman.net/andy Cogito, ergo sum. -- Rene Descartes I yam what I yam and that's all what I yam. -- Popeye --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-devel] Snapshots now being built with gcc 3.2
On Thu, 2002-09-26 at 19:22, José Fonseca wrote: AFAIK the announced breakeage concerned C++ only. Well, there is some c++ code in libnurbs, and so apparently libGLU.so. However it appears that wouldn't affect the DRI snapshots. RedHat does indeed provides a compat-gcc package. I'll see what I can do to use it within my scripts. If the segfaults I'm getting actually are related to XAA, then it really may not matter. I'm trying (again) to make my own snapshot build (with gcc 2.96), but I'll also try one of yours. Nevertheless it would be good to be sure about these binary compatabilities, since the widespread of gcc-3.2 will happen very soon. Most likely, yes, since Red Hat 8.0 and Gentoo 1.4 will both have it; I don't think most other Linux distributions will stay too far behind (except maybe Debian, but at least they have 3.0 in stable and 3.2 in testing). Is it possible you have changed some of your compiler options? The snapshots are about twice the size they used to be. -- Andy Dustman PGP: 0x930B8AB6 @ .net http://dustman.net/andy Cogito, ergo sum. -- Rene Descartes I yam what I yam and that's all what I yam. -- Popeye --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-devel] Snapshots now being built with gcc 3.2
Am Freitag, 27. September 2002 03:20 schrieb Andy Dustman: On Thu, 2002-09-26 at 19:22, José Fonseca wrote: AFAIK the announced breakeage concerned C++ only. Well, there is some c++ code in libnurbs, and so apparently libGLU.so. However it appears that wouldn't affect the DRI snapshots. RedHat does indeed provides a compat-gcc package. I'll see what I can do to use it within my scripts. If the segfaults I'm getting actually are related to XAA, then it really may not matter. I'm trying (again) to make my own snapshot build (with gcc 2.96), but I'll also try one of yours. Nevertheless it would be good to be sure about these binary compatabilities, since the widespread of gcc-3.2 will happen very soon. Most likely, yes, since Red Hat 8.0 and Gentoo 1.4 will both have it; I don't think most other Linux distributions will stay too far behind (except maybe Debian, but at least they have 3.0 in stable and 3.2 in testing). I think they are ahead. This world is not (US-) America alone... Mandrake 9.0 (October) SuSE 8.1 (30. September) http://www.suse.de/de/private/products/suse_linux/i386/new_features.html UnitedLinux Beta Cheers, Dieter -- Dieter Nützel Graduate Student, Computer Science University of Hamburg Department of Computer Science @home: Dieter.Nuetzel at hamburg.de (replace at with @) --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-devel] Snapshots now being built with gcc 3.2
On Thu, 2002-09-26 at 20:50, Andy Dustman wrote: On Thu, 2002-09-26 at 03:40, Charl P. Botha wrote: serious note, have you tried replacing your libxaa.a yet to eliminate the possibility of that signal 11 that we've been seeing with the last few snapshots? You could also try a snapshot of today or later, because Michel has fixed the XAA problem which resulted in the Sig11. I'll certainly try another snapshot. My own snapshot attempt at last night looks like it had nearly the same signal 11 problem, although it got slightly further than the snapshots on the websites. Neither one actually crashes the machine, but the video goes dead: The monitor no longer syncs up and switching VTs doesn't help. Still getting the same problem with the r200. Interestingly, the amount of memory used for textures has gone up recently, from about 93 MB to 113 MB. Most obvious feature of this is what looks like a NULL pointer reference at the end. Also there is a load/unload/load of the xaa module. (II) Loading sub module xaa (II) LoadModule: xaa (II) Loading /usr/X11R6/lib/modules/libxaa.a (II) Module xaa: vendor=The XFree86 Project compiled for 4.2.0, module version = 1.0.0 ABI class: XFree86 Video Driver, version 0.5 (WW) module minor version (0) is less than the required minor version (1) (II) UnloadModule: xaa (II) Unloading /usr/X11R6/lib/modules/libxaa.a (II) Loading sub module xaa (II) LoadModule: xaa (II) Loading /usr/X11R6/lib/modules/libxaa.a (II) Module xaa: vendor=The XFree86 Project compiled for 4.2.0, module version = 1.0.0 ABI class: XFree86 Video Driver, version 0.5 (**) RADEON(0): Using AGP 1x mode (II) RADEON(0): AGP Fast Write disabled by default ... (II) RADEON(0): [drm] created radeon driver at busid PCI:1:0:0 (II) RADEON(0): [drm] added 8192 byte SAREA at 0xd892b000 (II) RADEON(0): [drm] mapped SAREA 0xd892b000 to 0x40013000 (II) RADEON(0): [drm] framebuffer handle = 0xd000 (II) RADEON(0): [drm] added 1 reserved context for kernel (II) RADEON(0): [agp] Mode 0x1f000201 [AGP 0x8086/0x7190; Card 0x1002/0x514c] (II) RADEON(0): [agp] 32768 kB allocated with handle 0xe092f000 (II) RADEON(0): [agp] ring handle = 0xe000 (II) RADEON(0): [agp] Ring mapped at 0x48234000 (II) RADEON(0): [agp] ring read ptr handle = 0xe0101000 (II) RADEON(0): [agp] Ring read ptr mapped at 0x40015000 (II) RADEON(0): [agp] vertex/indirect buffers handle = 0xe0102000 (II) RADEON(0): [agp] Vertex/indirect buffers mapped at 0x48335000 (II) RADEON(0): [agp] AGP texture map handle = 0xe0302000 (II) RADEON(0): [agp] AGP Texture map mapped at 0x48535000 (II) RADEON(0): [drm] register handle = 0xe900 (II) RADEON(0): [dri] Visual configs initialized (II) RADEON(0): CP in BM mode (II) RADEON(0): Using 32 MB AGP aperture (II) RADEON(0): Using 1 MB for the ring buffer (II) RADEON(0): Using 2 MB for vertex/indirect buffers (II) RADEON(0): Using 29 MB for AGP textures (II) RADEON(0): Memory manager initialized to (0,0) (1408,8191) (II) RADEON(0): Largest offscreen area available: 1408 x 7141 (II) RADEON(0): Will use back buffer at offset 0xc5c000 (II) RADEON(0): Will use depth buffer at offset 0xf2e000 (II) RADEON(0): Will use 112640 kb for textures at offset 0x120 (==) RADEON(0): Backing store disabled (==) RADEON(0): Silken mouse enabled Screen to screen bit blits Solid filled rectangles Solid filled trapezoids 8x8 mono pattern filled trapezoids 8x8 color pattern filled rectangles CPU to Screen color expansion Solid Lines Dashed Lines Image Writes Driver provided ScreenToScreenBitBlt replacement Driver provided FillSolidRects replacement Driver provided WriteBitmap replacement Driver provided NonTEGlyphRenderer replacement (II) (null)(0): Acceleration enabled Fatal server error: Caught signal 11. Server aborting ** With the 20020926 official snapshot, the last line is the Silken mouse message. Otherwise the log appears to be the same. One other thing: There is a variable in the dripkg.sh script, PKG_MINIMAL=1, which is causing GL and core libraries not to be included the snapshot. Commenting this out reveals that the non-shared libraries are not getting built anyway. 20020920 is the last snapshot that works at all for me (for r200 and radeon). -- Andy Dustman PGP: 0x930B8AB6 @ .net http://dustman.net/andy Cogito, ergo sum. -- Rene Descartes I yam what I yam and that's all what I yam. -- Popeye --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-devel] Snapshots now being built with gcc 3.2
On Tue, 2002-09-24 at 09:25, José Fonseca wrote: I've updated my workstation to the RedHat Linux 7.3.94 beta, which has gcc 3.2. So now forward the snapshots will be built with this version. AFAIK this shouldn't pose any problem to the users since the key issue is that the kernel modules are compiled with the same version of gcc that compiled the kernel, and that still holds true. If the kernel modules were the only issue, you'd be right. Unfortunately the other important component of the snapshots is the DRI shared library. Since (for those who haven't heard) GCC 3.2 breaks binary compatibility with earlier versions, the shared libraries don't work. My X server dies on signal 11 almost immediately (during drm initialization). So these snapshots will only work if your X server is compiled with GCC 3.2. Also I've noticed that the shared library is now twice the size (or more) than it used to be (went from about 5 MB to 12 MB). Since very few people seem to have GCC 3.2 at the moment (I do have a Gentoo 1.4-pre1 box that does, but haven't tried DRI snaps on it yet), can we please have some built with the old gcc? Most likely Red Hat provides this in a gcc-compat package. I'm trying now to build some myself from CVS, but didn't have much luck last night (result didn't run). -- Andy Dustman PGP: 0x930B8AB6 @ .net http://dustman.net/andy Cogito, ergo sum. -- Rene Descartes I yam what I yam and that's all what I yam. -- Popeye --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
[Dri-devel] Snapshots now being built with gcc 3.2
Hi guys. Yep, vacations ended. I've updated my workstation to the RedHat Linux 7.3.94 beta, which has gcc 3.2. So now forward the snapshots will be built with this version. AFAIK this shouldn't pose any problem to the users since the key issue is that the kernel modules are compiled with the same version of gcc that compiled the kernel, and that still holds true. Strangely, when testing the snapshots scripts with the new setup I noticed that only radeon and r200 drivers are being built on the HEAD (as there is no errors on the build log). Keith, I know you've been merging r200-0-2-branch, so do you know anything about this? The Mach64 development on my side is still on hold. Besides the hassle of returning from vacations, and have a lot of stuff to do, my laptop's hard drive is busted so I've been working at the univeristy were I don't have any Mach64 card near me. Hopefully I should receive a new drive shortly. Jose Fonseca --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-devel] Snapshots now being built with gcc 3.2
Hi Jose I've updated my workstation to the RedHat Linux 7.3.94 beta, which has gcc 3.2. So now forward the snapshots will be built with this version. AFAIK this shouldn't pose any problem to the users since the key issue is that the kernel modules are compiled with the same version of gcc that compiled the kernel, and that still holds true. Is it your workstation which is used to built snapshots? I thought it was SF machnery... The Mach64 development on my side is still on hold. Besides the hassle of returning from vacations, and have a lot of stuff to do, my laptop's hard drive is busted so I've been working at the univeristy were I don't have any Mach64 card near me. Hopefully I should receive a new drive shortly. Sad. Really expected fast mach progress after your return. With security resolved and gatos merged (thanks to Leif again) it could go into XFree86 HEAD... Anyway, glad to hear from you again Sergey --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
