gdk-pixbuf-loaders is GTK+2.

OK I was suspecting that but wasn't sure, thanks for the remark. So there really aren't many extra dependencies after all.

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.

here is the hard lesion match the program to the O/S
do not even think about matching the O/S to the program

Build from source

had you used the force and built from source

you would never had this problem in the first place

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.

Thanks for your feedback.

Glad to see another success story on recovering from a botched glibc upgrade :-)

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.

Thanks,
Anithen

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.

Boguś Żaba

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.