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
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 --
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/X1
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
>
> 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
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
>
> 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 re
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
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
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: structu
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: struc
11 matches
Mail list logo
