Okay...
Calling all techno geeks out there...
If any of you all know anything about Linux, here's my problem, it's a
small one...but it's annoying as hell and it has me stumped. This may seem
trivial, but it's driving me nuts. lol
I've got three different installs of Linux - Slackware, Gentoo, and Red
Hat, on three disks. I've been trying to build a program called Xine so I
can play all my DivX files and DVD's through it, sort of like a media
player for X. All three installs are using the 2.4 Kernel, Slackware and
Gentoo slightly newer, but not by much. I tried Totem, but it uses the
Xine libraries...and so does Kaffeine and a few other GUI's.
I ran a ./configure, and make install on all the lib files, then ran a
make and install on the program source. Within less than 15 minutes
each for the Gentoo and Slackware disks, I had it configured and working
correctly through my user accounts. With Slackware, the build and install
went smoothly...Xine came up and played beautifully, with Gentoo, the
same. Kaffeine worked great, and so did Totem...even though I can't play
some DVDs. No biggie...I can figure that out in time.
But with Red Hat, I've had to grep the individual files and delete them
after each install so I can try rebuilding over and over again...no go, it
crashes each time. I've tried different source tarballs, and even tried
rebuilding the src.rpm, but it still craps out on me halfway through the
build.
I've tried installing from different RPMs, it fails on me...and I've tried
editing my ld.so.conf to point to the separate libraries, but for some
oddball reason, Xine tells me that it can't find them...and so does
Kaffeine when I try to run a ./configure on it.
When I eventually got Xine to compile, I installed it okay...no errors...I
try to run it and I get this:
**********
This is xine (X11 gui) - a free video player v0.9.22.
(c) 2000-2003 The xine Team.
Built with xine library 1.0.0 (1-rc0a)
Found xine library version: 1.0.0(1-beta8).
xine: relocation error: xine: undefined symbol: xine_engine_set_param
**********
I haven't a clue what the above error means.
At one point, it told me that it couldn't find the libraries...and I tried
editing my ld.so.conf to point to the separate libraries, but for some
oddball reason, Xine still told me that it couldn't find them...and so did
Kaffeine when I would try to run a ./configure on it. Then suddenly...I
must have done something right, because Xine found the libraries, but
Kaffeine still wouldn't ./configure even when I pointed it to them.
Now...I'm *really* determined, and getting highly annoyed...this is
driving me crazy...because it *should* work.
If I haven't confused anyone who knows what the hell I'm talking about,
then I would appreciate any input, no matter how silly it might
sound...this is driving me batty.
Thanks in advance.
<snip>
90% of that is greek, and linux doesn't have registeries but any way a silly
suggesting. and apologies if you have done this.
Reset one machine to a totally clean slate.
Install only the bare necessities for testing with Red Hat.
fingers crossed because there can't be any more misaligned pointers. And
don't let it communicate with any other machine if possibly just in case
there's a rogue out there.
if it did actually work once, and doesn't again, you possibly have rogue
pointers corrupting your layout of where to find what.
Sounds like you're having a gorgeous xmas break
Marc
Broken - 28 Dec 2004 07:06 GMT
> <snip>
>
> 90% of that is greek, and linux doesn't have registeries but any way a silly
> suggesting. and apologies if you have done this.
No suggestion is silly. :)
> Reset one machine to a totally clean slate.
> Install only the bare necessities for testing with Red Hat.
Something I haven't tried yet, but something I've considered...the problem
is, that Linux isn't that easy to install. Plus, getting my hardware to
work after a fresh install isn't on my list of happy things to do...LOL
But...I can't deny, that I love doing stuff like that. (BG)
> fingers crossed because there can't be any more misaligned pointers. And
> don't let it communicate with any other machine if possibly just in case
> there's a rogue out there.
True, my server is Linux also. It's doubtful that it's affecting it, but
it is possible.
> if it did actually work once, and doesn't again, you possibly have rogue
> pointers corrupting your layout of where to find what.
That's exactly what's driving me nuts...I've used this program before.
It's been a while, but I've used it in Red Hat. The only thing I can think
of is that something I've installed since has possibly overwritten one of
the conf files, or added an entry that doesn't belong. Corrupted files in
Linux is extremely rare, because of the way it writes to it's file
system...but it's not entirely impossible
> Sounds like you're having a gorgeous xmas break
LOL...I accidentally sent this to the wrong group, it wasn't meant for
here...sorry about that.
Besides, I thrive on stuff like this...challenges make computers much more
interesting. That's why I switched to Linux in the first place. :)
> Marc
Thank you Marc
Marc - 28 Dec 2004 07:30 GMT
<snip>
> Something I haven't tried yet, but something I've considered...the problem
> is, that Linux isn't that easy to install. Plus, getting my hardware to
> work after a fresh install isn't on my list of happy things to do...LOL
LOL
>> if it did actually work once, and doesn't again, you possibly have rogue
>> pointers corrupting your layout of where to find what.
[quoted text clipped - 10 lines]
> LOL...I accidentally sent this to the wrong group, it wasn't meant for
> here...sorry about that.
interesting to get something different.
> Besides, I thrive on stuff like this...challenges make computers much more
> interesting. That's why I switched to Linux in the first place. :)
Don't have the time to even think of that :(
>> Marc
>
> Thank you Marc
Oh well, a break for what I'm supposed to be doing
Marc
Hi,
> I ran a ./configure, and make install on all the lib files, then ran a
> make and install on the program source. Within less than 15 minutes
This is a tad confusing. What lib files? Are we talking libs that the program
requires (dependencies) or from within the lib directory within the source?
Unless it is some weird install/configure system, a configure - make - make
install from within the main source dir should install any libs it needs.
(configure with your options thatis :) )
> But with Red Hat, I've had to grep the individual files and delete them
grep to delete? Not sure of this one either.. grep looks for certain expressions
within a file, not a file in a directory... locate/whereis/find perhaps?
Why do you have to delete them all the time? best bet..during configure, specify
a prefix such as
./configure --prefix=/usr/local/xine1
once installed simply create a symlink to it like: (this is optional..read on..)
ln -s /usr/local/xine1 /usr/local/xine
Now, having installed in the above directories, it wont likely be in your $PATH
so you would need to fix that up later. owever, if things go wrong or it does
not work, this is where the advantage is.
EVERYTHING wll be located within that one dir (/usr/local/xine1) all the libs,
includes, binaries and whatever else. So rather than looking in /usr/bin
/usr/sbin /usr/lib etc for all of the files a standard install does, just rm -rf
/usr/local/xine1, OR make your next install /usr/local/xine2 during configure.
If I am not making sense, let me know :)
> after each install so I can try rebuilding over and over again...no go, it
> crashes each time. I've tried different source tarballs, and even tried
What kind of crash? Is it segfaulting? Showing any debug/errors? Is it core
dumping? Also, while we are at it, what version of Redhat anyway?
> rebuilding the src.rpm, but it still craps out on me halfway through the
> build.
With what error?
> I've tried installing from different RPMs, it fails on me...and I've tried
What failure when installing from RPM?(I take it you are talking binary RPM?
> editing my ld.so.conf to point to the separate libraries, but for some
> oddball reason, Xine tells me that it can't find them...and so does
> Kaffeine when I try to run a ./configure on it.
You did run ldconfig afterwards? also, configure --help
This will show you other options, such as specifying a path to your includes and
libs.. Tried specifying them here?
> When I eventually got Xine to compile, I installed it okay...no errors...I
> try to run it and I get this:
[quoted text clipped - 8 lines]
>
> I haven't a clue what the above error means.
It means that the program is calling on a lib file for a certain function symbol
but it cannot find it
To see if a lib contains a required function you can run the nm binary on it..
nm /path/to/lib
Googling on the exact error produces many results.. Have a look through them
also!
> At one point, it told me that it couldn't find the libraries...and I tried
> editing my ld.so.conf to point to the separate libraries, but for some
[quoted text clipped - 5 lines]
> Now...I'm *really* determined, and getting highly annoyed...this is
> driving me crazy...because it *should* work.
Yes, it *should* work, considering xine was once packaged with RedHat. I think
it stopped after the 7.xx series. Again, with all the lib issues, try specifying
the path to the libs during configure....
Maybe you have it working already, but if not, just need a few more specifics as
above and it may help find where the issue is :)
Brad
Traveler - 29 Dec 2004 05:30 GMT
> Hi,
>
[quoted text clipped - 6 lines]
> configure - make - make install from within the main source dir should
> install any libs it needs. (configure with your options thatis :) )
No, not exactly, you have to configure, make, and make install the libs
separately. It's one of the dependencies, and the program won't configure
without doing this first. Rarely have I encountered a program like this
that doesn't require the lib files to be installed first. The source comes
as a separate download. The lib is a much larger download than the source.
>> But with Red Hat, I've had to grep the individual files and delete them
>
> grep to delete? Not sure of this one either.. grep looks for certain
> expressions within a file, not a file in a directory...
> locate/whereis/find perhaps?
Yes, it can. You can grep to find individual files as well as expressions
within them. Running a find -name can do the same thing. Using -r on grep
can yield all kinds of desirable results. -H can not only print matching
content, but the name of the file. I don't use whereis because it's buggy
and I've never bothered with locate. I also used find to get the location
of the files.
> Why do you have to delete them all the time? best bet..during configure,
> specify a prefix such as
>
> ./configure --prefix=/usr/local/xine1 once installed simply create a
> symlink to it like: (this is optional..read on..)
Because configure searches for copies of the same install. Without
deleting them...I can't get a fresh install from scratch.
> ln -s /usr/local/xine1 /usr/local/xine
>
[quoted text clipped - 8 lines]
> /usr/local/xine2 during configure. If I am not making sense, let me know
> :)
That makes perfect sense, and it's something I hadn't thought of...good
suggestion...thanks.
>> after each install so I can try rebuilding over and over again...no go,
>> it crashes each time. I've tried different source tarballs, and even
>> tried
>
> What kind of crash? Is it segfaulting? Showing any debug/errors? Is it
> core dumping? Also, while we are at it, what version of Redhat anyway?
None of the above, it's giving me an error level during the make. No core
dump, it just doesn't finish with the compile.
It doesn't make a difference now anyway, because I got it to install...now
I need to narrow down the reasons why it won't run.
Incidentally: Red Hat 9.1
>> rebuilding the src.rpm, but it still craps out on me halfway through
>> the build.
>
> With what error?
The same as above, it just doesn't finish the compile. Irrelevant now,
because I found an rpm that actually works.
>> I've tried installing from different RPMs, it fails on me...and I've
>> tried
>
> What failure when installing from RPM?(I take it you are talking binary
> RPM?
RedHat Package Manager, and I found out why...there were dependency issues
that I've since corrected, but the program still won't run.
>> editing my ld.so.conf to point to the separate libraries, but for some
>> oddball reason, Xine tells me that it can't find them...and so does
>> Kaffeine when I try to run a ./configure on it.
>
> You did run ldconfig afterwards? also, configure --help
Yes, I ran ldconfig. :)
configure --help doesn't work in Red Hat, all you get is an error message.
man configure within the source directory will give you the options for
configure.
> This will show you other options, such as specifying a path to your
> includes and libs.. Tried specifying them here?
Message output from make on xine-lib:
***************************
xine-config will be installed to /usr/local/bin
This path is not in your search path. This means it is possible
that xine-config will not be found when you try to compile a
program using xine-lib. This will result in build failures.
If this happens, you should add $final_bindir to
the environment variable PATH like that:
export PATH=/usr/local/bin:\$PATH"
Note that this is only needed for compilation. It is not needed
to have xine-config in your search path at runtime. (Although
it will not cause any harm either.)
***************************
After updating with ldconfig, I get closer only by the original error that
I mentioned before, after installing and trying to run Xine.
>> When I eventually got Xine to compile, I installed it okay...no
>> errors...I try to run it and I get this:
[quoted text clipped - 15 lines]
> Googling on the exact error produces many results.. Have a look through
> them also!
Thank you, it's the first time I've seen that error...and it had me
scratching my head. :)
> > At one point, it told me that it couldn't find the libraries...and I
> > tried
[quoted text clipped - 11 lines]
> think it stopped after the 7.xx series. Again, with all the lib issues,
> try specifying the path to the libs during configure...
It stopped being standard before that...I used 7.1 for a while, and it was
never installed. So I had to install it from scratch, and yes, I did have
it working before. That's what puzzles me. I've been using Red Hat for
years now, and I *used* to buy it religiously, before they dumped the
desktop.
I'm waiting on a copy of Fedora Core, it should prove to be quite
interesting.
It's just one of those weird things that I have to figure out through
trial and error.
> Maybe you have it working already, but if not, just need a few more
> specifics as above and it may help find where the issue is :)
I'm not exactly new to Linux, I've been using it extensively for about six
years now, I'm no expert, but I know my way around it pretty well. Every
now and then, something so simple as this drives me totally nuts.
I will definitely try your suggestions...they give me something to work
with. Thank you very much for your attention to this...I appreciate
anything that might help.
> Brad
Broke
toto - 29 Dec 2004 15:43 GMT
LOL. Are you having an identity crisis?
--
Dorothy
There is no sound, no cry in all the world
that can be heard unless someone listens ..
The Outer Limits
Broken - 30 Dec 2004 03:39 GMT
> LOL. Are you having an identity crisis?
shaddup
enigma - 30 Dec 2004 13:51 GMT
>> LOL. Are you having an identity crisis?
>
> shaddup
i figured out who it was by the headers, but it gave me a
start... my usenet stalker used Traveler as a nym.
lee
Broken - 31 Dec 2004 04:32 GMT
>>> LOL. Are you having an identity crisis?
>>
[quoted text clipped - 3 lines]
> start... my usenet stalker used Traveler as a nym.
> lee
LOL...nope, I'm not a stalker. I just forgot to switch nyms...lol