Re: [Dri-devel] mach64 binaries: do not work

2002-03-12 Thread Sergey V. Udaltsov
Well.. this can take a few days since I have to get some time to mess with these scripts. Sorry. Take your time. Stabilizing things after 0-0-3 branching has definitely much higher priority. It is not a big problem to rebuild these objects. But - just to make it easier - could you please make

Re: [Dri-devel] mach64 binaries: do not work

2002-03-12 Thread Sergey V. Udaltsov
make -f Makefile.linux mach64.o Thanks. I did not know. I just did make I just noticed the error about dynamic loading: libGL cannot load /usr/X11R6-DRI/lib/modules/dri/mach64_dri.so. I think it is the error in your build scripts. They should use X11R6 directory instead, arent' they? After I

Re: [Dri-devel] mach64 binaries: do not work

2002-03-12 Thread José Fonseca
On 2002.03.12 11:18 Sergey V. Udaltsov wrote: make -f Makefile.linux mach64.o Thanks. I did not know. I just did make There is a problem in the i8x0 modules source with the most recent kernels. I already had received a report of this problem which I forwarded to this list, since it's

[Dri-devel] mach64 binaries: do not work

2002-03-11 Thread Sergey V. Udaltsov
Hi all There are problems with the bleeding edge binaries: 1. First of all, the kernel module cannot be loaded because of some unresolved symbols. And even when I do rm *.o, make, the resulting mach64.o has some unresolved symbols (on depmod)! I do not know how it is possible. insmod -f manages

Re: [Dri-devel] mach64 binaries: do not work

2002-03-11 Thread Jose Fonseca
On Mon, 2002-03-11 at 14:37, Sergey V. Udaltsov wrote: Hi all There are problems with the bleeding edge binaries: 1. First of all, the kernel module cannot be loaded because of some unresolved symbols. And even when I do rm *.o, make, the resulting The .o shouldn't be packaged, or even

Re: [Dri-devel] mach64 binaries: do not work

2002-03-11 Thread Sergey V. Udaltsov
The .o shouldn't be packaged, or even built. I'll have to check why this is happening. Well, hope the next version will be free of these wrong object files. Could you please past the output of insmod to see what are the failed symbols? Well, now it is OK. Sorry for disturbing on this issue.