MPlayer.Slackbuild cant compile.
 

Im using Slackware-current and im trying to to enable the Slackbuild to use patented code as stated in the SLackBuild. I edited the script to show

USE_PATENTS=${USE_PATENTS:-"NO"}
to
USE_PATENTS="YES"

and it fails all the time with

MPlayer.SlackBuild: line 289: cd: /tmp/build/package-MPlayer/usr/share/mplayer/skins: No such file or directory
MPlayer.SlackBuild FAILED at line 289!

If i leave the Slackbuild script as is it compiles fine.

Any ideas on how to fix this ?

Was there any error in the /tmp/configure-MPlayer.log file? The skins directory is not being created. You should be able to trace the error in the log file.

The /tmp/configure-MPlayer.log doesnt show any errors but the
error.MPlayer.log shows exactley the same thing s as i posted.
MPlayer.SlackBuild FAILED at line 289!.

I tried adding this to the MPlayer.Slackbuild


# Install our default skin:
mkdir -p $PKG/usr/share/mplayer/skins <---
cd $PKG/usr/share/mplayer/skins

and it compiled and made a package but after its installed it wont work.

No icon and it wont even work through command line.

USE_PATENTS=${USE_PATENTS:-"YES"}

Seems like the answer to me.

the Bottom of the Slackbuild has this written in it.

I guess that somewhere earlier the process went off the rails. The difference when setting USE_PATENTS="YES" is that the SlackBuild script will try to checkout the MPlayer sources (the source tarball in Slackware is stripped of patent-encumbered source code). Perhaps this failed on your computer? Then, there could have been compilation issues that you failed to detect but which result in nothing getting installed (so that the directory $PKG/usr/share/mplayer/skins will be absent too).
Compile the package using this command:
which copies every line that gets written to the screen, into the file "build.log". Then, go through the build.log file to find out what went wrong.

Eric

Try linuxpokernut's idea. The worst that can happen is it still doesn't work.

There are these lines in the Slackbuild script:

Did you have the default skin source file Blue-1.7.tar.bz2 in your build directory?

yes i have Blue-1.7.tar.bz2 .

The problem is with that particular snapshot of MPlayer that you are trying to build.
Apparently, the part that gets stripped when building the Slackware package without patent issues, contains a bit of code which was added recently and which prevents successful compilation.

This has more information about your "error: static declaration of 'log2' follows non-static declaration" issue (look it up in your build log): http://lists.mplayerhq.hu/pipermail/...ly/077259.html

Using the latest SVN snapshot of MPlayer fixes your problem
Look for the VERSION definition in MPlayer.SlackBuild and change the value "r29390" to either one of these: "r29709" or "20090923". Both will checkout today's snapshot. Using this version, the MPlayer.SlackBuild script will compile a package with no errors.

Eric

Nevermind.

Scuzz, I had the same issue when I tried to use Eric's script. I must have tried it a half dozen times with different settings. I really wanted it to work for me but no joy.

I ended up using the 12.2 SlackBuild - mplayer (svn_20090413) with the latest player sources - mplayer-export-2009-09-11.tar.bz2. I changed the mplayer.SlackBuild as follows:

Maybe not the best solution but my MPlayer seems to be working just fine. Hope that helps.

P.S. I noticed Eric has replied while I was typing and it looks like he already identified what was happening. I might have to give those new instructions a test drive when I get a chance.

Hey! You did not have to remove your post - you have independently come to the same conclusion I made, that a current SVN snapshot works fine. We both posted around the same time... always better to get confirmation from two sources.

Eric

Seems easier to just install libdvdcss [1] than to rebuild mplayer...
[1] http://slackbuilds.org/repository/13...ies/libdvdcss/

And you would be correct.

I have to build MPlayer anyway with the --enable-lirc option so i thought this would be a better option. Turns out i was wrong again.


I tried to compile as you posted above and it compiled fine, But when i try starting MPlayer it just crashes with like 5 different errors on startup before dieing.

Thanks for all your help though.

Im going to just compile the basic source thats on my disk with lirc support and download libdvdcss

I also compiled MPlayer to see if it could fix my problem with gecko-mediaplayer plugin and I have the same problem. It compiles fine but crashes on startup. I'm looking into it right now. So far this is all I have to go on

MPlayer interrupted by signal 11 in module: unknown
- MPlayer crashed by bad usage of CPU/FPU/RAM.
Recompile MPlayer with --enable-debug and make a 'gdb' backtrace and
disassembly. Details in DOCS/HTML/en/bugreports_what.html#bugreports_crash.
- MPlayer crashed. This shouldn't happen.
It can be a bug in the MPlayer code _or_ in your drivers _or_ in your
gcc version. If you think it's MPlayer's fault, please read
DOCS/HTML/en/bugreports.html and follow the instructions there. We can't and
won't help unless you provide this information when reporting a possible bug.

That is 100% the exact response i got.

I'm using svn snapshot 29633 and I'm not having any issues with programs that use mplayer. I have Gnome player as well as the gecko-mediaplayer plugin installed and haven't seen any issues. Do you have a test case for the gecko-mediaplayer-plugin?

I just did EXACTLY what alien-bob suggested (ie update build script). It pulled down the latest code, into a directory and then failed, saying it could not find the tarball. So I simply did a 'tar -jcvf MPlayer-r29709.tar.bz2 MPlayer-r29709/'
and re-ran the build - and it built fine.

Then I did a manual test of a simple avi (divx) and it worked fine. I don't do gecko-* stuff - can't comment on that.

Actually gecko works fine on 32bit for me, but is unstable to the point of unusable on 64bit. Are you running 64?

Nope. Running 32 bit here.

We'll I got it to work with a band-aid fix. The reason I recompile mplayer is to get vdpau support since I have a nvidia card, that above error only seems to affect gui mplayer, if I run from mplayer from command line it works fine. So I just run gnome-mplayer now and it works fine. Still looking into fixes up as of now it works with gnome-mplayer and I have vdpau support :).

Hi Daedra,

I believe the default gui has been effectively abandoned by the MPlayer developers.

Andrew

this revision looks like has a working-for-me gui, don't know if it's last revision in which gui works (surely not).
if you checkout that mplayer svn revision now it will checkout also a newer libswscale (in integrated-ffmpeg), so also after exporting that mplayer revision (29587) it won't build (that's why I linked the .tar.xz with the checkout I've done on 30th of august, it has the correct ffmpeg svn revision).

i choose to just not build the default gui anymore, but this is a personal decision.
looks like it will be probably removed from mplayer code.

Thanks for the heads up on the gui thing. I'm just using gnome-mplayer GUI frontend now with gecko-media plugins. I also finally got vdpau working. I can't believe I had just heard about this. Before a 1080p trailer would generally eat around 30-40% of my CPU now its less than 3%. Anyone with a newer nvidia card should check it out, it's a definite improvement.

There is also a xine-vdpau you can checkout also.

BTW, I got gecko-mediaplayer plugins working under 64bit. Turns out the I had caching disabled, it now working.