SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
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!.
the Bottom of the Slackbuild has this written in it.
Code:
** If you are unaffected by patent concerns because you hold the required
** licenses and permission to use the patented code, or reside in a
** location where this is not a concern, and wish to include the patented
** and restricted code (you take all legal responsibility for doing so),
** then edit this SlackBuild script and change the line:
** USE_PATENTS=${USE_PATENTS:-"NO"}
** to:
** USE_PATENTS="YES"
**
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:
Code:
./MPlayer.SlackBuild 2>&1 | tee build.log
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.
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!.
and it compiled and made a package but after its installed it wont work.
No icon and it wont even work through command line.
There are these lines in the Slackbuild script:
Quote:
DEFSKIN=${DEFSKIN:-"Blue"} # Download more skins at the following url:
SKINVER=${SKINVER:-"1.7"} # http://www.mplayerhq.hu/design7/dload.html
...
...
# The default skin to use (we need to add at least one)
SOURCE[1]="$SRCDIR/${DEFSKIN}-${SKINVER}.tar.bz2"
SRCURL[1]="http://www.mplayerhq.hu/MPlayer/skins/${DEFSKIN}-${SKINVER}.tar.bz2"
Did you have the default skin source file Blue-1.7.tar.bz2 in your build directory?
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.
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.
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 ?
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.
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.
Quote:
Originally Posted by Alien Bob
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.
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
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.