I appied the savage patches at http://freedesktop.org/~fxkuehl/savage/
to the latest cvs. The DRM and the 3d drivers build fine, but when I try
to build the ddx/xserver, I get this error:
86Server-DXF86VIDMODE
-DXvMCExtension -DSMAR
Am Di, den 26.10.2004 schrieb Daniel J. Michael um 16:08:
> I appied the savage patches at http://freedesktop.org/~fxkuehl/savage/
> to the latest cvs. The DRM and the 3d drivers build fine, but when I try
> to build the ddx/xserver, I get this error:
> 86Server-DXF
Well, it seemed to install fine, but direct rendering is disabled. I
also get this error in my Xorg.0.log:
Symbol SavageInitStreamsNew from module
/usr/X11R6/lib/modules/drivers/savage_drv.o is unresolved!
Symbol SavageInitStreams2000 from module
/usr/X11R6/lib/modules/drivers/savage_drv.o is un
Hi,
Felix I had also problem to compile your patches
and after check and recheck if isn't my fault,
I get the conclusion that
I can compile mesa with make in /opt/trunk/Mesa, but can't compile it if I try compile from xorg cvs ( with extra/Mesa linked to /opt/trunk/Mesa).
sorry for unfinish
On Thu, 2004-10-28 at 18:58, Sérgio M. Basto wrote:
> Hi,
> Felix I had also problem to compile your patches
> and after check and recheck if isn't my fault,
> I get the conclusion that
> I can compile mesa with make in /opt/trunk/Mesa, but can't compile it
> if I try compile from xorg cvs ( with
Am Do, den 28.10.2004 schrieb Daniel J. Michael um 16:56:
> Well, it seemed to install fine, but direct rendering is disabled. I
> also get this error in my Xorg.0.log:
> Symbol SavageInitStreamsNew from module
> /usr/X11R6/lib/modules/drivers/savage_drv.o is unresolved!
> Symbol SavageInitStream
Am Fr, den 29.10.2004 schrieb Sérgio M. Basto um 13:04:
> On Thu, 2004-10-28 at 18:58, Sérgio M. Basto wrote:
> > Hi,
> > Felix I had also problem to compile your patches
> > and after check and recheck if isn't my fault,
> > I get the conclusion that
> > I can compile mesa with make in /opt/trun
You are correct about the unresolved symbols, they seem to happen with
the cvs code also (but I think they must be new in the last couple of
weeks sometime). Here is the output of my LIBGL_DEBUG=verbose glxinfo:
[EMAIL PROTECTED] ~ $ LIBGL_DEBUG=verbose glxinfo
name of display: :0.0
libGL: XF86DR
On Fri, 2004-10-29 at 18:35, Felix Kühling wrote:
> Yes, that's how it works now. We can't fix the Xorg tree to compile with
> the latest Mesa source since that would break the build of the Mesa
> version that is included in the Xorg tree. ?
so if you could *NOT* compile GL on Xorg, we save some t
Am Sa, den 30.10.2004 schrieb Daniel J. Michael um 0:51:
> You are correct about the unresolved symbols, they seem to happen with
> the cvs code also (but I think they must be new in the last couple of
> weeks sometime). Here is the output of my LIBGL_DEBUG=verbose glxinfo:
> [EMAIL PROTECTED] ~
The latest Mesa did the trick. Thanks for the help. So far the drivers
are working just fine (although I've only tested woith glxgears and
narmal x useage so far). As far as these errors are concerned:
Symbol SavageInitStreamsNew from module
/usr/X11R6/lib/modules/drivers/savage_drv.o is unresol
On Sat, 2004-10-30 at 04:06 +0100, Sérgio wrote:
> Can we change configuration of Xorg, for compile and install xorg
> without compile any source of Mesa and/or GLx ?
You could try BuildGLXLibrary and/or BuildXF86DRI. I'm not sure of all
the implications, but it sounds like the right direction.
12 matches
Mail list logo
