From: MW <wil...@bt...> - 2004-04-27 11:40:04
|
Hi, I'm unable to get xine-lib 1.0rc3c working on my system, and I'm not sure if the problem relates to xine-lib or the X.org monolithic tree. Basically, my system is as follows: LFS 5.0, P4 Dell Inspiron 8200 laptop with NVIDIA card and driver version 5336. Trying to start xine results in a message stating that all X video drivers failed, no valid video drivers. The X.Org build of X11 creates .so and .so.1 libraries for Xv and XvMC, but does not create .a libraries for either of these two modules. When it comes to compiling xine-lib, I'm warned that these two libraries are needed for Xv output, but that they're not found. Searching the /usr/X11R6/lib directory locates both of these libraries in .so format so I'm unsure why I'm getting this error. The xine-lib configure script seems to be searching for libXv.a and libXvMC.a, but I thought that .a libraries were only needed if you weren't building shared libraries. I'm confused and could use any advice that's out there. I've already tried doing an ld --whole-archive -static -o libXv.a libXv.so.1 but get a whole bunch of 'undefined reference' errors: ld: warning: cannot find entry symbol _start; not setting start address libXv.so: undefined reference to `XGetErrorDatabaseText' libXv.so: undefined reference to `memmove' libXv.so: undefined reference to `memcpy' libXv.so: undefined reference to `malloc' libXv.so: undefined reference to `XextAddDisplay' libXv.so: undefined reference to `_XFlushGCCache' libXv.so: undefined reference to `strncpy' libXv.so: undefined reference to `XextFindDisplay' libXv.so: undefined reference to `_XReply' libXv.so: undefined reference to `XextCreateExtension' libXv.so: undefined reference to `sprintf' libXv.so: undefined reference to `_XSetLastRequestRead' libXv.so: undefined reference to `_XEatData' libXv.so: undefined reference to `_XFlush' libXv.so: undefined reference to `_XSend' libXv.so: undefined reference to `_XRead' libXv.so: undefined reference to `XextRemoveDisplay' libXv.so: undefined reference to `XMissingExtension' libXv.so: undefined reference to `free' I'm now stuck, my tiny brain can take no more... Mark |
From: Michael R. <mr...@us...> - 2004-04-27 15:20:06
Attachments:
Xv-shared.patch
|
Hi Mark, > I'm unable to get xine-lib 1.0rc3c working on my system, and I'm not > sure if the problem relates to xine-lib or the X.org monolithic tree. > Basically, my system is as follows: > > LFS 5.0, P4 Dell Inspiron 8200 laptop with NVIDIA card and driver > version 5336. > > Trying to start xine results in a message stating that all X video > drivers failed, no valid video drivers. > > The X.Org build of X11 creates .so and .so.1 libraries for Xv and XvMC, > but does not create .a libraries for either of these two modules. When > it comes to compiling xine-lib, I'm warned that these two libraries are > needed for Xv output, but that they're not found. I attached a patch against the xine-lib configure script, which adds two new options: --with-xv-lib and --with-xvmc-lib. If you configure like that: ./configure --with-xv-lib=shared --with-xvmc-lib=shared it might work (not tested). Could you try that, please? Remember that you need autoconf and automake installed, because the patch requires the configure script and the Makefiles to be rebuilt. Michael -- /* Binary compatibility is good American knowhow fuckin' up. */ 2.2.16 /usr/src/linux/arch/sparc/kernel/sunos_ioctl.c |
From: M. B. <ser...@ne...> - 2004-04-28 02:53:49
|
hi >=20 > I attached a patch against the xine-lib configure script, which adds two = new=20 > options: --with-xv-lib and --with-xvmc-lib. If you configure like that: >=20 > ./configure --with-xv-lib=3Dshared --with-xvmc-lib=3Dshared >=20 I would like try xvmc on savage where I can read more about this vo xvmc thanks=20 --=20 S=E9rgio M. B. |
From: Michael R. <mr...@us...> - 2004-04-28 18:30:26
|
Hi, > > I attached a patch against the xine-lib configure script, which adds two > > new options: --with-xv-lib and --with-xvmc-lib. If you configure like > > that: > > > > ./configure --with-xv-lib=shared --with-xvmc-lib=shared > > I would like try xvmc on savage where I can read more about this vo xvmc It is similar to Xv. It is either supported by the driver or not. If it is, using it in xine should be completely transparent. But I don't think a lot of drivers actually support XvMC. Michael -- I am Bill of Borg. Resistance izkx GPF 0x5654 8820 Application RESIST.EXE has performed an illegal operation and will be shut down. |
From: M. B. <ser...@ne...> - 2004-04-28 19:09:23
|
On Wed, 2004-04-28 at 19:30, Michael Roitzsch wrote: > Hi, >=20 > > > I attached a patch against the xine-lib configure script, which adds = two > > > new options: --with-xv-lib and --with-xvmc-lib. If you configure like > > > that: > > > > > > ./configure --with-xv-lib=3Dshared --with-xvmc-lib=3Dshared > > > > I would like try xvmc on savage where I can read more about this vo xvm= c >=20 > It is similar to Xv. It is either supported by the driver or not. If it i= s,=20 > using it in xine should be completely transparent. But I don't think a lo= t of=20 > drivers actually support XvMC. As far as I know, its one 2D acceleration, writes directly on video card like dri does , in a slow card this can be good, the only drive thats (as far I know ) that support XvMC is NVIDIA. >=20 > Michael --=20 S=E9rgio M. B. |
From: Michael R. <mr...@us...> - 2004-04-28 19:18:38
|
Hi, > > It is similar to Xv. It is either supported by the driver or not. If it > > is, using it in xine should be completely transparent. But I don't think > > a lot of drivers actually support XvMC. > > As far as I know, its one 2D acceleration, writes directly on video card > like dri does , in a slow card this can be good, the only drive thats > (as far I know ) that support XvMC is NVIDIA. Actually, XvMC is far more sophisticated. The name stands for XVideo Motion Compensation and it offloads two major parts of the MPEG decoding process, namely the motion compensation and the IDCT stage to the graphics card. So XvMC partly does MPEG decoding in hardware. It is most helpful with high definition MPEG streams, which are hard to decode even for today's processors. Michael -- The dark ages were caused by the Y1K problem. |
From: M. B. <ser...@ne...> - 2004-04-28 19:41:19
|
On Wed, 2004-04-28 at 20:18, Michael Roitzsch wrote: > Hi, >=20 > > > It is similar to Xv. It is either supported by the driver or not. If = it > > > is, using it in xine should be completely transparent. But I don't th= ink > > > a lot of drivers actually support XvMC. > > > > As far as I know, its one 2D acceleration, writes directly on video car= d > > like dri does , in a slow card this can be good, the only drive thats > > (as far I know ) that support XvMC is NVIDIA. >=20 > Actually, XvMC is far more sophisticated. The name stands for XVideo Moti= on=20 > Compensation and it offloads two major parts of the MPEG decoding process= ,=20 > namely the motion compensation and the IDCT stage to the graphics card. S= o=20 > XvMC partly does MPEG decoding in hardware. It is most helpful with high=20 > definition MPEG streams, which are hard to decode even for today's=20 > processors. ok, and what about trying this with Savage XvMC drive on my notebook ? >=20 > Michael --=20 S=E9rgio M. B. |
From: MW <wil...@bt...> - 2004-04-28 19:46:30
|
Michael, I'm running the following versions of autoconf and automake: Autoconf 2.5.7 Automake 1.7.6 The configure options weren't showing the new 'shared library' options so I did a 'make clean', followed by a straight configure without any options. When I next ran 'configure --help' the new options were showing up. I used them and it found my libXv.so and libXvMC.so (although the configure script still reports them as static at the end of the configure process) However, when I go to build the library, it stops building almost immediately with the following error: cpu_accel.c: In function `arch_accel': cpu_accel.c:100: error: can't find a register in class `BREG' while reloading `asm' cpu_accel.c:106: error: can't find a register in class `BREG' while reloading `asm' cpu_accel.c:117: error: can't find a register in class `BREG' while reloading `asm' cpu_accel.c:121: error: can't find a register in class `BREG' while reloading `asm' make[3]: *** [cpu_accel.lo] Error 1 make[3]: Leaving directory `/usr/src/xine-lib-1-rc3c/src/xine-utils' make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory `/usr/src/xine-lib-1-rc3c/src' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/usr/src/xine-lib-1-rc3c' make: *** [all] Error 2 I unset all my CFLAG, CXXFLAG, CPPFLAG optimisations prior to doing anything with xine-lib, as I've found in the past it doesn't like my '-march=pentium4' optimisations. Again, your assistance would be much appreciated. P.S. Sorry it's taken me so long to reply to you, I've been at work all day. Mark |
From: Michael R. <mr...@us...> - 2004-04-28 19:50:26
|
Hi, > > > > It is similar to Xv. It is either supported by the driver or not. If > > > > it is, using it in xine should be completely transparent. But I don't > > > > think a lot of drivers actually support XvMC. > > > > > > As far as I know, its one 2D acceleration, writes directly on video > > > card like dri does , in a slow card this can be good, the only drive > > > thats (as far I know ) that support XvMC is NVIDIA. > > > > Actually, XvMC is far more sophisticated. The name stands for XVideo > > Motion Compensation and it offloads two major parts of the MPEG decoding > > process, namely the motion compensation and the IDCT stage to the > > graphics card. So XvMC partly does MPEG decoding in hardware. It is most > > helpful with high definition MPEG streams, which are hard to decode even > > for today's processors. > > ok, and what about trying this with Savage XvMC drive on my notebook ? You have to install the XvMC library for the Savage chip and then recompile xine-lib against it. For now it is probably easiest to link from libXvMC.a to libsavageXvMC.a for xine to find it. When everything is compiled and installed, run xine with -VXvMC. Michael -- Zero Administration: There is nothing you can do to fix it. |
From: M. B. <ser...@ne...> - 2004-04-30 01:33:06
|
Hi, On Wed, 2004-04-28 at 20:50, Michael Roitzsch wrote: > > > > ok, and what about trying this with Savage XvMC drive on my notebook ? >=20 > You have to install the XvMC library for the Savage chip and then recompi= le=20 > xine-lib against it. For now it is probably easiest to link from libXvMC.= a to=20 > libsavageXvMC.a for xine to find it. When everything is compiled and=20 > installed, run xine with -VXvMC. I am trying to understand the code of XvMC in CVS of dri trunk tree, and it does=20 /usr/X11R6/lib/libXvMC.a /usr/X11R6/lib/libI810XvMC.a /usr/X11R6/lib/libsavageXvMC.a Does the 3 libs, so doing what you are saying I have to delete libXvMC.a which doesn't seems correct for me Any suggestion ? --=20 S=E9rgio M. B. |
From: Michael R. <mr...@us...> - 2004-04-28 21:03:53
|
Hi Mark, > When I next ran 'configure --help' the new options were showing up. I > used them and it found my libXv.so and libXvMC.so (although the > configure script still reports them as static at the end of the > configure process) That's good news. (Thanks for the remark about the wrong static in the plugin report. I fixed this here.) > However, when I go to build the library, it stops building almost > immediately with the following error: > > cpu_accel.c: In function `arch_accel': > cpu_accel.c:100: error: can't find a register in class `BREG' while > reloading `asm' > cpu_accel.c:106: error: can't find a register in class `BREG' while > reloading `asm' > cpu_accel.c:117: error: can't find a register in class `BREG' while > reloading `asm' > cpu_accel.c:121: error: can't find a register in class `BREG' while > reloading `asm' > make[3]: *** [cpu_accel.lo] Error 1 > make[3]: Leaving directory `/usr/src/xine-lib-1-rc3c/src/xine-utils' > make[2]: *** [all-recursive] Error 1 > make[2]: Leaving directory `/usr/src/xine-lib-1-rc3c/src' > make[1]: *** [all-recursive] Error 1 > make[1]: Leaving directory `/usr/src/xine-lib-1-rc3c' > make: *** [all] Error 2 Really strange. This file has nothing to do with XvMC. Where you able to build xine-lib before our XvMC experiments? > I unset all my CFLAG, CXXFLAG, CPPFLAG optimisations prior to doing > anything with xine-lib, as I've found in the past it doesn't like my > '-march=pentium4' optimisations. The correct variable would be CFLAGS (note the last 'S'), have you just misspelled them above or are you maybe compiling with additional flags? (Unsetting them after ./configure is useless. The value at ./configure-time is stored in ./config.status.) > P.S. Sorry it's taken me so long to reply to you, I've been at work all > day. Don't appologize for that. We all have lives outside xine development. ;) Michael -- "When you say "I wrote a program that crashed Windows", people just stare at you blankly and say "Hey, I got those with the system, *for free*." -Linus Torvalds |
From: MW <wil...@bt...> - 2004-04-28 22:00:33
|
Michael Roitzsch wrote: >Hi Mark, > > > >>However, when I go to build the library, it stops building almost >>immediately with the following error: >> >>cpu_accel.c: In function `arch_accel': >>cpu_accel.c:100: error: can't find a register in class `BREG' while >>reloading `asm' >>cpu_accel.c:106: error: can't find a register in class `BREG' while >>reloading `asm' >>cpu_accel.c:117: error: can't find a register in class `BREG' while >>reloading `asm' >>cpu_accel.c:121: error: can't find a register in class `BREG' while >>reloading `asm' >>make[3]: *** [cpu_accel.lo] Error 1 >>make[3]: Leaving directory `/usr/src/xine-lib-1-rc3c/src/xine-utils' >>make[2]: *** [all-recursive] Error 1 >>make[2]: Leaving directory `/usr/src/xine-lib-1-rc3c/src' >>make[1]: *** [all-recursive] Error 1 >>make[1]: Leaving directory `/usr/src/xine-lib-1-rc3c' >>make: *** [all] Error 2 >> >> > >Really strange. This file has nothing to do with XvMC. Where you able to build >xine-lib before our XvMC experiments? > > > I was able to build xine-lib prior to this. However, just to check this I extracted a new (unpatched) copy of xine-lib in a different directory and ran a make clean. I don't get any errors when rebuilding after a make clean with the unpatched version of xine-lib. After patching the source tree, a make clean takes *much* longer than it did previously, and there are lots of lines similar to the following: /bin/sh /home/packages/xine-lib-1-rc3c/missing --run automake-1.6 --gnu src/post/planar/Makefile I've just included the one line as an example, but I don't remember seeing the --run automake-1.6 text prior to applying the patch. Is the fact my automake is 1.7 likely to cause it problems? When I try to rebuild post patch, I find I'm getting the same errors reported above. Just out of interest, I remember seeing a compiler flag scrolling by when originally building xine-lib (before I applied the patch) along the lines of -DRUNTIME_DETECT_CPU. That compiler flag doesn't appear at any point before this error message occurs. As the error seems to be saying it can't find a register, could the problem be that xine-utils are trying to build for a different CPU target? >>I unset all my CFLAG, CXXFLAG, CPPFLAG optimisations prior to doing >>anything with xine-lib, as I've found in the past it doesn't like my >>'-march=pentium4' optimisations. >> >> > >The correct variable would be CFLAGS (note the last 'S'), have you just >misspelled them above or are you maybe compiling with additional flags? >(Unsetting them after ./configure is useless. The value at ./configure-time is >stored in ./config.status.) > > > Sorry, this was just a typo. I meant CFLAGS... (though I did double-check just in case) Mark |
From: Michael R. <mr...@us...> - 2004-05-01 20:47:17
|
Hi Mark, > >>cpu_accel.c: In function `arch_accel': > >>cpu_accel.c:100: error: can't find a register in class `BREG' while > >>reloading `asm' > >>cpu_accel.c:106: error: can't find a register in class `BREG' while > >>reloading `asm' > >>cpu_accel.c:117: error: can't find a register in class `BREG' while > >>reloading `asm' > >>cpu_accel.c:121: error: can't find a register in class `BREG' while > >>reloading `asm' > >>make[3]: *** [cpu_accel.lo] Error 1 > >>make[3]: Leaving directory `/usr/src/xine-lib-1-rc3c/src/xine-utils' > >>make[2]: *** [all-recursive] Error 1 > >>make[2]: Leaving directory `/usr/src/xine-lib-1-rc3c/src' > >>make[1]: *** [all-recursive] Error 1 > >>make[1]: Leaving directory `/usr/src/xine-lib-1-rc3c' > >>make: *** [all] Error 2 > > I was able to build xine-lib prior to this. However, just to check this > I extracted a new (unpatched) copy of xine-lib in a different directory > and ran a make clean. I don't get any errors when rebuilding after a > make clean with the unpatched version of xine-lib. > > After patching the source tree, a make clean takes *much* longer than it > did previously, and there are lots of lines similar to the following: > > /bin/sh /home/packages/xine-lib-1-rc3c/missing --run automake-1.6 > --gnu src/post/planar/Makefile That is because all the Makefile.in's are being rebuilt because you changed the configure script by patching it. > When I try to rebuild post patch, I find I'm getting the same errors > reported above. Could you post the complete compiler command here, please? If possible, both the failing one and the correctly compiling one? (To make this easier to catch, instead of doing a make from the toplevel, just go into src/xine-util and type "make cpu_accel.lo > command" and post the file "command".) > Just out of interest, I remember seeing a compiler flag scrolling by > when originally building xine-lib (before I applied the patch) along the > lines of -DRUNTIME_DETECT_CPU. That compiler flag doesn't appear at any > point before this error message occurs. As the error seems to be saying > it can't find a register, could the problem be that xine-utils are > trying to build for a different CPU target? Sharp eyes! That's -DRUNTIME_CPUDETECT which is a compiler flag only used for ffmpeg. This has nothing to do with our problem. Michael -- HARDFAIL("Not enough magic."); 2.4.0-test2 /usr/src/linux/drivers/block/nbd.c |
From: Michael R. <mr...@us...> - 2004-05-01 20:41:22
Attachments:
xvmc-arguments.patch
|
Hi S=E9rgio, > > You have to install the XvMC library for the Savage chip and then > > recompile xine-lib against it. For now it is probably easiest to link > > from libXvMC.a to libsavageXvMC.a for xine to find it. When everythin= g is > > compiled and installed, run xine with -VXvMC. > > I am trying to understand the code of XvMC in CVS of dri trunk tree, > and it does > /usr/X11R6/lib/libXvMC.a > /usr/X11R6/lib/libI810XvMC.a > /usr/X11R6/lib/libsavageXvMC.a > > Does the 3 libs, so doing what you are saying I have to delete libXvMC.= a > which doesn't seems correct for me > Any suggestion ? I think you are right. There is a general libXvMC plus a hardware specifi= c=20 one. (The same is hardcoded for nVidia into xine-lib now.) So I think you= =20 will need the libsavageXvMC.a and the libXvMC.a. libI810XvMC.a seems to b= e=20 for another chipset (Intel i810?). I attached a patch to xine-lib's configure.ac. Could you please apply tha= t?=20 Problem is that you need to rebuild the configure script afterwards. For=20 that, you need to have autoconf installed. Just go to the top dir of the=20 source tree and type "autoconf". ./configure --help should list the new=20 argument --with-xvmc-hw-lib then. You should run configure with=20 --with-xvmc-hw-lib=3DlibsavageXvMC.a and then make as usual. Michael --=20 panic("CPU too expensive - making holiday in the ANDES!"); 2.2.16 /usr/src/linux/arch/mips/kernel/traps.c |
From: M. B. <ser...@ne...> - 2004-05-30 06:32:41
|
Finally I had time to test this ./configure --with-xvmc-lib=3Dshared --with-xvmc-hw-lib=3DlibsavageXvMC.so First impression XvMCNIVIDIA is not correct=20 - Xv (XVideo *static*) - XvMC (XVideo *static*) - XvMCNVIDIA (XVideo *static*) but no luck , just a blue window=20 libmpeg2: output port has XvMC capability Start XvMCPutSurface: dest=3D0, desty=3D0, destw=3D200, desth=3D150 On Sat, 2004-05-01 at 21:40, Michael Roitzsch wrote:=20 > Hi S=E9rgio, >=20 > > > You have to install the XvMC library for the Savage chip and then > > > recompile xine-lib against it. For now it is probably easiest to link > > > from libXvMC.a to libsavageXvMC.a for xine to find it. When everythin= g is > > > compiled and installed, run xine with -VXvMC. > > > > I am trying to understand the code of XvMC in CVS of dri trunk tree, > > and it does > > /usr/X11R6/lib/libXvMC.a > > /usr/X11R6/lib/libI810XvMC.a > > /usr/X11R6/lib/libsavageXvMC.a > > > > Does the 3 libs, so doing what you are saying I have to delete libXvMC.= a > > which doesn't seems correct for me > > Any suggestion ? >=20 > I think you are right. There is a general libXvMC plus a hardware specifi= c=20 > one. (The same is hardcoded for nVidia into xine-lib now.) So I think you= =20 > will need the libsavageXvMC.a and the libXvMC.a. libI810XvMC.a seems to b= e=20 > for another chipset (Intel i810?). >=20 > I attached a patch to xine-lib's configure.ac. Could you please apply tha= t?=20 > Problem is that you need to rebuild the configure script afterwards. For=20 > that, you need to have autoconf installed. Just go to the top dir of the=20 > source tree and type "autoconf". ./configure --help should list the new=20 > argument --with-xvmc-hw-lib then. You should run configure with=20 > --with-xvmc-hw-lib=3DlibsavageXvMC.a and then make as usual. >=20 > Michael --=20 S=E9rgio M. B. |
From: MW <wil...@bt...> - 2004-05-06 09:33:08
|
Michael Roitzsch wrote: > Hi Mark, > > >>Thanks for your assistance, you were absolutely right in saying that the >>libtool script was missing the -DPIC flag. The xine-lib now builds and >>installs absolutely fine. > > > That's good news. From the next release you will have the required > configure-option out of the box, so no re-libtoolizing will be necessary. > > >>However, when I try to run xine, I get the 'All available video drivers >>failed' message before it instantly exits. It's enough to make you want >>to run MPlayer... ;) > > > Please don't do that... > What video drivers have been built at all? Look for xineplug_vo_out_* in the > xine plugin directory ($prefix/lib/xine/plugins/1.0.0). If there are no X11 > plugins at all (xv, xshm, xvmc), xine has not found the required X11 headers. > Was X11 installed to the standard location? > > Michael > Hi Michael, The following are what I have: /usr/lib/xine/plugins/1.0.0/xineplug_vo_out_dxr3.so /usr/lib/xine/plugins/1.0.0/xineplug_vo_out_fb.so /usr/lib/xine/plugins/1.0.0/xineplug_vo_out_none.so /usr/lib/xine/plugins/1.0.0/xineplug_vo_out_sdl.so /usr/lib/xine/plugins/1.0.0/xineplug_vo_out_vidix.so /usr/lib/xine/plugins/1.0.0/xineplug_vo_out_xshm.so /usr/lib/xine/plugins/1.0.0/xineplug_vo_out_xv.so /usr/lib/xine/plugins/1.0.0/xineplug_vo_out_xvmc.so X11 is in the traditional /usr/X11R6 location. As I've said previously, the only thing 'abnormal' about my X11 is that I'm using the X.org 'monolithic' build rather than the xfree86 build. I can't deny I'm puzzled, I've never had any problems running xine on my older systems that have had xfree86 4.3.0, it does seem to be switching to the X.org build that has given me all this trouble. Am I the only person doing this? Mark |
From: Michael R. <mr...@us...> - 2004-05-06 19:40:21
|
Hi Mark, > > What video drivers have been built at all? Look for xineplug_vo_out_* in > > the xine plugin directory ($prefix/lib/xine/plugins/1.0.0). If there are > > no X11 plugins at all (xv, xshm, xvmc), xine has not found the required > > X11 headers. Was X11 installed to the standard location? > > The following are what I have: > > /usr/lib/xine/plugins/1.0.0/xineplug_vo_out_dxr3.so > /usr/lib/xine/plugins/1.0.0/xineplug_vo_out_fb.so > /usr/lib/xine/plugins/1.0.0/xineplug_vo_out_none.so > /usr/lib/xine/plugins/1.0.0/xineplug_vo_out_sdl.so > /usr/lib/xine/plugins/1.0.0/xineplug_vo_out_vidix.so > /usr/lib/xine/plugins/1.0.0/xineplug_vo_out_xshm.so > /usr/lib/xine/plugins/1.0.0/xineplug_vo_out_xv.so > /usr/lib/xine/plugins/1.0.0/xineplug_vo_out_xvmc.so Could you post the output of "xine --verbose=3 -VXv" please? And please check, if the Xv and XShm plugins actually link: Does this give any hints about unresolved symbols? ldd -r /usr/lib/xine/plugins/1.0.0/xineplug_vo_out_xshm.so ldd -r /usr/lib/xine/plugins/1.0.0/xineplug_vo_out_xv.so > X11 is in the traditional /usr/X11R6 location. As I've said previously, > the only thing 'abnormal' about my X11 is that I'm using the X.org > 'monolithic' build rather than the xfree86 build. > > I can't deny I'm puzzled, I've never had any problems running xine on my > older systems that have had xfree86 4.3.0, it does seem to be switching > to the X.org build that has given me all this trouble. Am I the only > person doing this? Possibly. Michael -- The computer revolution is over. The computers won. |