Alright I'm guessing my problem is with the library part of the install. I'm compiling the source here and I had been getting errors on the configure command about alerting the installer to the directory Xine would be installed in. I added the string where it told me too and seemed to solve the problem on that end. I didn't get any more error messages till it was time for the "make install" command. It has some permissions issues so I logged in as root and everything seemed to go ok but when I tried to install a front-end I was told that the libraries didn't make it it. I'm stuck on this.

the warnings about "add /usr/lib to your LD_LIBRARY_PATH etc...." are normal. Even if you install in prefix /usr you will get these warnings. Now for the libraries, what does configure complain about?

and if you did a standard ./configure, make, make install did you add /usr/local/lib to /etc/ld.so.conf and run ldconfig as root?

Post some errors, probably start with the configure ones, and continue on down.

You should be able to yum that as well, but that really doesn't teach you how to fix this does it?

Cool

I added /usr/local/lib to the end of the /etc/ld.so.conf file but I didn't run anything after that. And I tried entering ldconfig into the shell but as it turns out that isn't a command so I'll need help on that part too.

ldconfig must be run as root ( if you want to see what its linking run: ldconfig -v | more)

Should be one as root...

Try:
/sbin/ldconfig

Cool

Good to hear an echo... I think I'll chime out of this one, have fun!

Double-under-score J seems to be taking good care here.

Cool

The errors are gone aside from the one I get when I try to install a front-end

and this is it
"*** Could not run XINE test program, checking why...
*** The test program compiled, but did not run. This usually means
*** that the run-time linker is not finding XINE or finding the wrong
*** version of XINE. If it is not finding XINE, you'll need to set your
*** LD_LIBRARY_PATH environment variable, or edit /etc/ld.so.conf to point
*** to the installed location Also, make sure you have run ldconfig if that
*** is required on your system
***
*** If you have an old version installed, it is best to remove it, although
*** you may also be able to get things to work by modifying LD_LIBRARY_PATH
***
configure: error: *** You should install xine-lib first ***"

Now that it's linked itself up do I go ahead with the regular install?
I'd like to know before hand cause that's a long make file.

did configure finish without any errors? if so go ahead and try to compile ( its a long compile by the way)

as far as the error above, if you have an older version of xine-lib installed it will give you problems. So try to remove that one ( if there is one ) and do ./configure again. ( when its talking about overriding that with LD_LIBRARY_PATH lets avoid that for now, it can be done but it will cause you problems later ).

Ok it went in great. I had gone in orginally with the Xine-UI frontend but found it sucked and am now installing gxine. I see where the plugin is and should be able to handle it from here. If not I'll be back. Thanks for all the help this forum is great.

glad to help - post back if any problems ( I agree with you, the xine-ui is almost unusable for me. I gotta use totem or gxine).

oh yeah, to use the mplayer codecs for xine ( to play quicktime, realplayer, windows media, etc..files) go here and download the essential codecs package and extract it to /usr/lib/win32 (you will have to create the /usr/lib/win32 directory).

Ok well I'm 90% there.

In the gxine plugins folder there are a bunch of files I'd rather not go sorting around like crazy.
"gxineplugin.la jritypes.h Makefile.in npunix.lo plugin.c plugin.o
jri.h Makefile npapi.h npunix.o plugin.h
jri_md.h Makefile.am npunix.c npupp.h plugin.lo"

None of these is your average so plugin file so I'm a bit confused here.
And just from what I've tried on my own, it looks like it needs to be compiled so I tried a "make" command and nothing. Of course my complete knowledge here comes from what I know from other installiations so it's not that vast.

A 'make' in the top level directory should certainly produce something, as there is a Makefile in the listed files up there. You can read the README if there is one, if not, you can read the Makefile to see what's going on and maybe why nothing is being returned.

Cool

I can't find anything in the documentation about the plugins and I can't find any way to trigger the make file.