On Thursday 01 April 2004 19:24, Fryderyk Dziarmagowski wrote:
> Hello,
>
> I got following problem with tdfx snapshots:
>
> [EMAIL PROTECTED] fritz]$ LIBGL_DEBUG=1 glxgears
> libGL error: dlopen /usr/X11R6/lib/modules/dri/tdfx_dri.so failed
> (/usr/X11R6/lib/modules/dri/tdfx_dri.so: undefined symb
Hello,
I got following problem with tdfx snapshots:
[EMAIL PROTECTED] fritz]$ LIBGL_DEBUG=1 glxgears
libGL error: dlopen /usr/X11R6/lib/modules/dri/tdfx_dri.so failed
(/usr/X11R6/lib/modules/dri/tdfx_dri.so: undefined symbol:
_mesa_init_driver_functions) libGL error: unable to find driver:
tdfx_
Ian Romanick wrote:
Craig Sowadski wrote:
I am getting the following error when trying to run any DRI/GL program
using snapshots staring at with radeon-20040304-linux.i386.tar.bz2
until present:
X Error of failed request: BadValue (integer parameter out of range
for operation)
Major opcode o
Ian Romanick wrote:
If the code in t_vtx_x86.c is not built, then t_vtx_x86_gcc.S must not
be built either. The code in the .S references symbols in the .c.
That's why I put the #ifdef around all the code in the .S in version
1.3. I guess my cvs log message wasn't clear enough. :( I'm fixing
Craig Sowadski wrote:
I am getting the following error when trying to run any DRI/GL program
using snapshots staring at with radeon-20040304-linux.i386.tar.bz2 until
present:
X Error of failed request: BadValue (integer parameter out of range for
operation)
Major opcode of failed request: 1
John Dennis wrote:
Hmm... I can't seem to find a working bugzilla for DRI, instead things
seem to be directed here. I just opened the following bug for xorg, it
fixes various pieces of code that need to set execute permission on data
memory. Some of these are in DRI and Mesa, it would be great if c
Hmm... I can't seem to find a working bugzilla for DRI, instead things
seem to be directed here. I just opened the following bug for xorg, it
fixes various pieces of code that need to set execute permission on data
memory. Some of these are in DRI and Mesa, it would be great if could
get these fixe
On Thu, 01 Apr 2004 16:28:43 +0100
Keith Whitwell <[EMAIL PROTECTED]> wrote:
> Felix Kühling wrote:
> > Hi,
> >
> > in the DRI build system t_vtx_x86_gcc.S ends up being compiled this
> > command:
> >
> > gcc -c -o t_vtx_x86_gcc.o t_vtx_x86_gcc.S
> >
> > The defined like -DUSE_X86_ASM are not t
Felix Kühling wrote:
Hi,
in the DRI build system t_vtx_x86_gcc.S ends up being compiled this
command:
gcc -c -o t_vtx_x86_gcc.o t_vtx_x86_gcc.S
The defined like -DUSE_X86_ASM are not there because they are defined as
CFLAGS which are not used for compiling assembler sources files. Because
of the
Felix Kühling wrote:
Hi,
when linking the radeon and r200 drivers I get these errors:
radeon_vtxtmp_x86.o(.data+0x18c): In function `_x86_Vertex3fv':
: multiple definition of `_x86_Vertex3fv'
../../../../../../lib/GL/mesa/tnl/t_vtx_x86_gcc.o(.data+0x80): first defined here
radeon_vtxtmp_x86.o(.da
Hi,
when linking the radeon and r200 drivers I get these errors:
radeon_vtxtmp_x86.o(.data+0x18c): In function `_x86_Vertex3fv':
: multiple definition of `_x86_Vertex3fv'
../../../../../../lib/GL/mesa/tnl/t_vtx_x86_gcc.o(.data+0x80): first defined here
radeon_vtxtmp_x86.o(.data+0x1d3): In functio
Hi,
in the DRI build system t_vtx_x86_gcc.S ends up being compiled this
command:
gcc -c -o t_vtx_x86_gcc.o t_vtx_x86_gcc.S
The defined like -DUSE_X86_ASM are not there because they are defined as
CFLAGS which are not used for compiling assembler sources files. Because
of the conditional statemen
12 matches
Mail list logo
