I just destroyed my computer by installing a bad package.
SlackwareThis Forum is for the discussion of Slackware Linux.
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.
Hey, everyone. I think in the process of trying to compile kino and cinerella I installed all the goodies I need for Lives and kino. I ended up getting the older 1.1.1 version from slackbuilds and Lives from their site. Both compiled nicely. I grabbed the kino 1.1.1 from slackbuilds earlier in the week, but I was just trying to handle the tar.gz package on my own instead of using slackbuild build script, which turned out to help a lot. Newer version of kino complains about " ../frame.h:54:35: error: libswscale/swscale.h: No such file or directory" even though that directory and file exists and I even reinstalled ffmpeg with src2pkg to make sure things are where they should be. The same error message occurs when I compile the package on my own or when I edit the build script for it.
Mplayer is wonderful and a large part of my life. The svn version I currently have installed was compiled with all the special options, and the gigantic blueray mkv video files you find on usenet play nicely along with youtube videos from the site. Mencoder exists, but I don't use it directly. I'm glad it's installed for all this graphical video editing software, though.
Well, I'm off to read the lives and kino documentation. Thanks for the help, everyone.
rob.rice: I always build from source, but I am new to using slackbuilds. After many failed compiles, the only prepackaged, precompiled binary I broke down and tried was cinerella. Then I was trying to run it, and each time I ran it, it asked for something it needed to run. I was able to satisfy all of its needs, but messed up when I tried satisfying its last need: glibc_2.7. This is where I ran into problems.
Also, I was trying to install kino 1.3.1, not 1.1.1, so the slackbuilds kino wasn't my first choice. Both version couldn't compile on their own. Using the slackbuild script I was able to compile and install 1.1.1. I now see the value of those scripts on the site.
Wow, I'm honored to see your reply, rworkman. Certainly, your tutorial was very helpful and clear. In addition to adding another tool to my mental chest, the process has brought me closer to Slackware.
Unfortunately, though, I'm back to square one with trying to get something on my computer to edit video. I read @ work that texmex suggests Lives. I'll try compiling and installing that in a minute, but if there's a thousand dependency issues I'm going to give it a rest until tomorrow.
I successfully installed kino on a Slack 11 system some time ago. I know there were some dependency issues, but reasonably resolvable. I still have it running and use it for downloading editing dv data from our video camera.
Indeed, kino works great. It is the only video editing program I can use realistically @ the moment. I made this test video with it: http://www.youtube.com/watch?v=YK2jHMOuDpI , messing with joining clips, visual effects, music dubbing, etc. I could've had one song through all 3 clips, but I wanted to see if I could have the song switch, or if I can have multiple visual effects, including multiple in the same clip. Very cool software.