Re: Problems compiling.
Adam K Kirchhoff wrote: > For the past day or two I've been getting the following error when trying to > compile DRI from Mesa CVS: > > gcc -c -I. -I../../../include -I../../../include/GL/internal > -I../../../src/mesa/main -I../../../src/mesa/glapi > -I../../../src/mesa/drivers/dri/common `pkg-config --cflags libdrm` > -I/usr/X11R6/include -DPTHREADS -DUSE_EXTERNAL_DXTN_LIB=1 -DIN_DRI_DRIVER > -DGLX_DIRECT_RENDERING -DHAVE_ALIAS -DXF86VIDMODE -D_REENTRANT > -UIN_DRI_DRIVER -Wmissing-prototypes -g -std=c99 -Wundef -fPIC -ffast-math > -I/usr/X11R6/include -DPTHREADS -DUSE_EXTERNAL_DXTN_LIB=1 -DIN_DRI_DRIVER > -DGLX_DIRECT_RENDERING -DHAVE_ALIAS -DXF86VIDMODE -D_REENTRANT > -UIN_DRI_DRIVER glxcmds.c -o glxcmds.o > glxcmds.c:1726: warning: no previous prototype for 'glXSwapIntervalMESA' > glxcmds.c:1758: warning: no previous prototype for 'glXGetSwapIntervalMESA' > glxcmds.c:1788: warning: no previous prototype for 'glXBeginFrameTrackingMESA' > glxcmds.c:1808: warning: no previous prototype for 'glXEndFrameTrackingMESA' > glxcmds.c:1829: warning: no previous prototype for 'glXGetFrameUsageMESA' > glxcmds.c:1857: warning: no previous prototype for 'glXQueryFrameTrackingMESA' > glxcmds.c:2595: warning: no previous prototype for 'glXBindTexImageEXT' > glxcmds.c: In function `glXBindTexImageEXT': > glxcmds.c:2618: error: `X_GLXvop_BindTexImageEXT' undeclared (first use in > this function) > glxcmds.c:2618: error: (Each undeclared identifier is reported only once > glxcmds.c:2618: error: for each function it appears in.) > glxcmds.c: At top level: > glxcmds.c:2636: warning: no previous prototype for 'glXReleaseTexImageEXT' > glxcmds.c: In function `glXReleaseTexImageEXT': > glxcmds.c:2659: error: `X_GLXvop_ReleaseTexImageEXT' undeclared (first use in > this function) > gmake: *** [glxcmds.o] Error 1 > *** Error code 1 You need to upgrade your proto/GL -- the fix hit Xorg CVS a day or two ago. Donnie signature.asc Description: OpenPGP digital signature
Re: Problems compiling.
Adam K Kirchhoff wrote: For the past day or two I've been getting the following error when trying to compile DRI from Mesa CVS: gcc -c -I. -I../../../include -I../../../include/GL/internal -I../../../src/mesa/main -I../../../src/mesa/glapi -I../../../src/mesa/drivers/dri/common `pkg-config --cflags libdrm` -I/usr/X11R6/include -DPTHREADS -DUSE_EXTERNAL_DXTN_LIB=1 -DIN_DRI_DRIVER -DGLX_DIRECT_RENDERING -DHAVE_ALIAS -DXF86VIDMODE -D_REENTRANT -UIN_DRI_DRIVER -Wmissing-prototypes -g -std=c99 -Wundef -fPIC -ffast-math -I/usr/X11R6/include -DPTHREADS -DUSE_EXTERNAL_DXTN_LIB=1 -DIN_DRI_DRIVER -DGLX_DIRECT_RENDERING -DHAVE_ALIAS -DXF86VIDMODE -D_REENTRANT -UIN_DRI_DRIVER glxcmds.c -o glxcmds.o glxcmds.c:1726: warning: no previous prototype for 'glXSwapIntervalMESA' glxcmds.c:1758: warning: no previous prototype for 'glXGetSwapIntervalMESA' glxcmds.c:1788: warning: no previous prototype for 'glXBeginFrameTrackingMESA' glxcmds.c:1808: warning: no previous prototype for 'glXEndFrameTrackingMESA' glxcmds.c:1829: warning: no previous prototype for 'glXGetFrameUsageMESA' glxcmds.c:1857: warning: no previous prototype for 'glXQueryFrameTrackingMESA' glxcmds.c:2595: warning: no previous prototype for 'glXBindTexImageEXT' glxcmds.c: In function `glXBindTexImageEXT': glxcmds.c:2618: error: `X_GLXvop_BindTexImageEXT' undeclared (first use in this function) glxcmds.c:2618: error: (Each undeclared identifier is reported only once glxcmds.c:2618: error: for each function it appears in.) glxcmds.c: At top level: glxcmds.c:2636: warning: no previous prototype for 'glXReleaseTexImageEXT' glxcmds.c: In function `glXReleaseTexImageEXT': glxcmds.c:2659: error: `X_GLXvop_ReleaseTexImageEXT' undeclared (first use in this function) gmake: *** [glxcmds.o] Error 1 *** Error code 1 Stop in /home/adamk/saved/source/Mesa/src. This has been happening on two machines, one running Debian and one running FreeBSD. You need to get the latest glxproto.h file from X.org CVS. See http://cvs.freedesktop.org/xorg/proto/GL/glxproto.h?r1=1.6&r2=1.7 -Brian --- 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://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642 -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
Problems compiling.
For the past day or two I've been getting the following error when trying to compile DRI from Mesa CVS: gcc -c -I. -I../../../include -I../../../include/GL/internal -I../../../src/mesa/main -I../../../src/mesa/glapi -I../../../src/mesa/drivers/dri/common `pkg-config --cflags libdrm` -I/usr/X11R6/include -DPTHREADS -DUSE_EXTERNAL_DXTN_LIB=1 -DIN_DRI_DRIVER -DGLX_DIRECT_RENDERING -DHAVE_ALIAS -DXF86VIDMODE -D_REENTRANT -UIN_DRI_DRIVER -Wmissing-prototypes -g -std=c99 -Wundef -fPIC -ffast-math -I/usr/X11R6/include -DPTHREADS -DUSE_EXTERNAL_DXTN_LIB=1 -DIN_DRI_DRIVER -DGLX_DIRECT_RENDERING -DHAVE_ALIAS -DXF86VIDMODE -D_REENTRANT -UIN_DRI_DRIVER glxcmds.c -o glxcmds.o glxcmds.c:1726: warning: no previous prototype for 'glXSwapIntervalMESA' glxcmds.c:1758: warning: no previous prototype for 'glXGetSwapIntervalMESA' glxcmds.c:1788: warning: no previous prototype for 'glXBeginFrameTrackingMESA' glxcmds.c:1808: warning: no previous prototype for 'glXEndFrameTrackingMESA' glxcmds.c:1829: warning: no previous prototype for 'glXGetFrameUsageMESA' glxcmds.c:1857: warning: no previous prototype for 'glXQueryFrameTrackingMESA' glxcmds.c:2595: warning: no previous prototype for 'glXBindTexImageEXT' glxcmds.c: In function `glXBindTexImageEXT': glxcmds.c:2618: error: `X_GLXvop_BindTexImageEXT' undeclared (first use in this function) glxcmds.c:2618: error: (Each undeclared identifier is reported only once glxcmds.c:2618: error: for each function it appears in.) glxcmds.c: At top level: glxcmds.c:2636: warning: no previous prototype for 'glXReleaseTexImageEXT' glxcmds.c: In function `glXReleaseTexImageEXT': glxcmds.c:2659: error: `X_GLXvop_ReleaseTexImageEXT' undeclared (first use in this function) gmake: *** [glxcmds.o] Error 1 *** Error code 1 Stop in /home/adamk/saved/source/Mesa/src. This has been happening on two machines, one running Debian and one running FreeBSD. 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://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642 -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-users] Re: problems compiling xorg cvs Re: drm CVS state...
On Tue, 2005-01-04 at 22:28 +, Sergio Monteiro Basto wrote: > On Tue, 2005-01-04 at 22:07 +, Dave Airlie wrote: > > > > > > After think a little and put dri working with kernel 2.4. > > > The only solution, that I see, to not private users of savage with > > > kernel 2.4, have dri. Is do 2 directory on Xorg tree, one with the code > > > before 2005-01-01 and other for kernel 2.6 > > > > Not really a good idea, the old code was not releaseable or secure, 2.4 is > > a fixes only tree, why do people want new drivers for it? if you are > > running production machines on it you won't want a dodgy DRM driver on > > it... > > > > you can always use CVS to checkout the old code... > > > > Dave. > > Ok I accept that, about releaseable and dodgy DRM drive, I agree. > > but just a tough, about security, nowadays it common say, errors are > security problems, I don't see how could drm be insecure. > DRM can be insecure because some hardware supports things like blitting any chunk of system memory from anywhere to anywhere. So you can't just let apps do anything, you have to verify the command stream somehow. Lee --- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and FREE -- well, almosthttp://www.thinkgeek.com/sfshirt -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-users] Re: problems compiling xorg cvs Re: drm CVS state...
> > Ok I accept that, about releaseable and dodgy DRM drive, I agree. > > but just a tough, about security, nowadays it common say, errors are > security problems, I don't see how could drm be insecure. Well if you have a multi-user machine, and they have access to the insecure drm, they can write some code to get the graphics card to DMA some root only RAM somewhere else, so things like passwd file contents etc can be gotten at ... it requires some knowledge of the graphics card but it is not beyond a decent hacker... (average script kiddie might have some issues...) Dave. -- David Airlie, Software Engineer http://www.skynet.ie/~airlied / airlied at skynet.ie pam_smb / Linux DECstation / Linux VAX / ILUG person --- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and FREE -- well, almosthttp://www.thinkgeek.com/sfshirt -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-users] Re: problems compiling xorg cvs Re: drm CVS state...
On Tue, 2005-01-04 at 22:07 +, Dave Airlie wrote: > > > > After think a little and put dri working with kernel 2.4. > > The only solution, that I see, to not private users of savage with > > kernel 2.4, have dri. Is do 2 directory on Xorg tree, one with the code > > before 2005-01-01 and other for kernel 2.6 > > Not really a good idea, the old code was not releaseable or secure, 2.4 is > a fixes only tree, why do people want new drivers for it? if you are > running production machines on it you won't want a dodgy DRM driver on > it... > > you can always use CVS to checkout the old code... > > Dave. Ok I accept that, about releaseable and dodgy DRM drive, I agree. but just a tough, about security, nowadays it common say, errors are security problems, I don't see how could drm be insecure. -- Sérgio M.B. --- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and FREE -- well, almosthttp://www.thinkgeek.com/sfshirt -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-users] Re: problems compiling xorg cvs Re: drm CVS state...
> > After think a little and put dri working with kernel 2.4. > The only solution, that I see, to not private users of savage with > kernel 2.4, have dri. Is do 2 directory on Xorg tree, one with the code > before 2005-01-01 and other for kernel 2.6 Not really a good idea, the old code was not releaseable or secure, 2.4 is a fixes only tree, why do people want new drivers for it? if you are running production machines on it you won't want a dodgy DRM driver on it... you can always use CVS to checkout the old code... Dave. -- David Airlie, Software Engineer http://www.skynet.ie/~airlied / airlied at skynet.ie pam_smb / Linux DECstation / Linux VAX / ILUG person --- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and FREE -- well, almosthttp://www.thinkgeek.com/sfshirt -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-users] Re: problems compiling xorg cvs Re: drm CVS state...
redirecting to devel ML On Mon, 2005-01-03 at 23:38 +, Sergio Monteiro Basto wrote: > If you're still using Linux 2.4 you need to upgrade that first. After think a little and put dri working with kernel 2.4. The only solution, that I see, to not private users of savage with kernel 2.4, have dri. Is do 2 directory on Xorg tree, one with the code before 2005-01-01 and other for kernel 2.6 thanks, -- Sérgio M.B. --- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and FREE -- well, almosthttp://www.thinkgeek.com/sfshirt -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: problems compiling xorg cvs Re: drm CVS state...
On Mon, 2005-01-03 at 00:18 +0100, Felix Kühling wrote: > Looks like this was caused by my update of the Savage DDX driver in the > X.org tree without also upating the Mesa driver in the X.org tree. At > the moment the Mesa driver in X.org's extras/Mesa can't be compiled with > the current Savage DDX. It is my understanding that this will be cleaned > up when X.org imports Mesa sources the next time, which will happen at > least once before the next major release. Since the Savage driver is > being worked on you don't want to work with constantly outdated sources > in extras/Mesa anyway. > > The recommended way to proceed is to disable the build of the Savage DRI > driver in the X.org tree (it should be disabled by default, since Savage > is a DevelDRIDriver) and build the Savage DRI driver directly from Mesa > CVS. The instructions at http://dri.freedesktop.org/wiki/Building should > work for you. > now glxinfo | grep dire direct rendering: No OpenGL renderer string: Mesa GLX Indirect > [snip] > > Regards, > Felix > -- Sérgio M.B. --- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and FREE -- well, almosthttp://www.thinkgeek.com/sfshirt -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: problems compiling xorg cvs Re: drm CVS state...
Am So, den 02.01.2005 schrieb Sergio Monteiro Basto um 23:18: > savage_xmesa.c: In function `savageInitDriver': > savage_xmesa.c:111: error: structure has no member named `frontPitch' > savage_xmesa.c:113: error: structure has no member named > `frontBitmapDesc' > savage_xmesa.c:121: error: structure has no member named > `backBitmapDesc' > savage_xmesa.c:123: error: structure has no member named > `depthBitmapDesc' > savage_xmesa.c:136: error: structure has no member named `agpTextures' > savage_xmesa.c:138: error: structure has no member named `agpTextures' > savage_xmesa.c:142: error: structure has no member named `backbuffer' > savage_xmesa.c:147: error: structure has no member named `depthbuffer' > savage_xmesa.c: In function `savageCreateContext': > savage_xmesa.c:313: error: structure has no member named `registers' > savage_xmesa.c:314: error: structure has no member named `registers' > savage_xmesa.c:315: error: structure has no member named `registers' > savage_xmesa.c:323: error: structure has no member named `agpTextures' > savage_xmesa.c:324: error: structure has no member named `agpTextures' > savage_xmesa.c:325: error: structure has no member named `agpTextures' > savage_xmesa.c:334: error: structure has no member named `agpTextures' > savage_xmesa.c:338: error: structure has no member named `BCIcmdBuf' > savage_xmesa.c:339: error: structure has no member named `registers' > savage_xmesa.c:341: error: structure has no member named `registers' > savage_xmesa.c:342: error: structure has no member named `BCIcmdBuf' > savage_xmesa.c:344: error: structure has no member named `aperture' > savage_xmesa.c:345: error: structure has no member named `aperture' > make[6]: *** [savage_xmesa.o] Error 1 > make[6]: Leaving directory > `/usr/src/opt/xorgcvs2/build/lib/GL/mesa/drivers/dri/savage' > make[5]: *** [all] Error 2 > make[5]: Leaving directory > `/usr/src/opt/xorgcvs2/build/lib/GL/mesa/drivers/dri' > make[4]: *** [all] Error 2 > make[4]: Leaving directory `/usr/src/opt/xorgcvs2/build/lib/GL' > make[3]: *** [all] Error 2 > make[3]: Leaving directory `/usr/src/opt/xorgcvs2/build/lib' > make[2]: *** [all] Error 2 > make[2]: Leaving directory `/usr/src/opt/xorgcvs2/build' > make[1]: *** [World] Error 2 > make[1]: Leaving directory `/usr/src/opt/xorgcvs2/build' > make: *** [World] Error 2 > > > > any help ? Looks like this was caused by my update of the Savage DDX driver in the X.org tree without also upating the Mesa driver in the X.org tree. At the moment the Mesa driver in X.org's extras/Mesa can't be compiled with the current Savage DDX. It is my understanding that this will be cleaned up when X.org imports Mesa sources the next time, which will happen at least once before the next major release. Since the Savage driver is being worked on you don't want to work with constantly outdated sources in extras/Mesa anyway. The recommended way to proceed is to disable the build of the Savage DRI driver in the X.org tree (it should be disabled by default, since Savage is a DevelDRIDriver) and build the Savage DRI driver directly from Mesa CVS. The instructions at http://dri.freedesktop.org/wiki/Building should work for you. [snip] Regards, Felix -- | Felix Kühling <[EMAIL PROTECTED]> http://fxk.de.vu | | PGP Fingerprint: 6A3C 9566 5B30 DDED 73C3 B152 151C 5CC1 D888 E595 | --- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and FREE -- well, almosthttp://www.thinkgeek.com/sfshirt -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
problems compiling xorg cvs Re: drm CVS state...
savage_xmesa.c: In function `savageInitDriver': savage_xmesa.c:111: error: structure has no member named `frontPitch' savage_xmesa.c:113: error: structure has no member named `frontBitmapDesc' savage_xmesa.c:121: error: structure has no member named `backBitmapDesc' savage_xmesa.c:123: error: structure has no member named `depthBitmapDesc' savage_xmesa.c:136: error: structure has no member named `agpTextures' savage_xmesa.c:138: error: structure has no member named `agpTextures' savage_xmesa.c:142: error: structure has no member named `backbuffer' savage_xmesa.c:147: error: structure has no member named `depthbuffer' savage_xmesa.c: In function `savageCreateContext': savage_xmesa.c:313: error: structure has no member named `registers' savage_xmesa.c:314: error: structure has no member named `registers' savage_xmesa.c:315: error: structure has no member named `registers' savage_xmesa.c:323: error: structure has no member named `agpTextures' savage_xmesa.c:324: error: structure has no member named `agpTextures' savage_xmesa.c:325: error: structure has no member named `agpTextures' savage_xmesa.c:334: error: structure has no member named `agpTextures' savage_xmesa.c:338: error: structure has no member named `BCIcmdBuf' savage_xmesa.c:339: error: structure has no member named `registers' savage_xmesa.c:341: error: structure has no member named `registers' savage_xmesa.c:342: error: structure has no member named `BCIcmdBuf' savage_xmesa.c:344: error: structure has no member named `aperture' savage_xmesa.c:345: error: structure has no member named `aperture' make[6]: *** [savage_xmesa.o] Error 1 make[6]: Leaving directory `/usr/src/opt/xorgcvs2/build/lib/GL/mesa/drivers/dri/savage' make[5]: *** [all] Error 2 make[5]: Leaving directory `/usr/src/opt/xorgcvs2/build/lib/GL/mesa/drivers/dri' make[4]: *** [all] Error 2 make[4]: Leaving directory `/usr/src/opt/xorgcvs2/build/lib/GL' make[3]: *** [all] Error 2 make[3]: Leaving directory `/usr/src/opt/xorgcvs2/build/lib' make[2]: *** [all] Error 2 make[2]: Leaving directory `/usr/src/opt/xorgcvs2/build' make[1]: *** [World] Error 2 make[1]: Leaving directory `/usr/src/opt/xorgcvs2/build' make: *** [World] Error 2 any help ? On Sun, 2005-01-02 at 12:16 +0100, Felix Kühling wrote: > Am So, den 02.01.2005 schrieb Sergio Monteiro Basto um 2:42: > > On Fri, 2004-12-31 at 16:02 +0100, Felix Kühling wrote: > > > > > I was going to change mesa/src/mesa/drivers/dri/Makefile.template to use > > > the share-core directory for DRM includes. This will be needed for the > > > new Savage DRM as it lives in linux-core/shared-core only. With your > > > assessment of the status of the 2.4 DRM it looks like it will never be > > > backported to Linux 2.4. > > > > with this all applied, just left us > > checkout drm and mesa cvs and apply > > http://freedesktop.org/~fxkuehl/savage/savage_xorg_20041229.diff > > on xorg tree to test it ? > > You don't need any of my previous patches. Just cvs update Xorg HEAD and > recompile the Savage driver from there. Actually the patches are > incompatible with the versions that I finally committed to CVS. So be > sure you don't mix them or you will get unpredictable behavior. From now > on I will keep the binary interfaces compatible though. > > > > > I just check-out mesa and drm and compile with > > make linux-dri-x86 > > and > > cp lib/savage_dri.so /usr/X11R6/lib/modules/dri/savage_dri.so > > and recompile drm for my kernel 2.4.29-pre1, after reboot (to be sure > > that savage kernel module is loaded again), all works normally. > > The new Savage driver lives in drm/shared-core and drm/linux-core. This > means it can only be compiled for Linux 2.6.x kernels. I'm not planning > a backport to 2.4. > > > > > thanks, > -- Sérgio M.B. --- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and FREE -- well, almosthttp://www.thinkgeek.com/sfshirt -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
