Hello Everyone,

Since upgrading to KDE 4.8, it has been a nightmare trying to get and anything multimedia related installed, most of which was removed during the install.

I cannot install any video editor (Cinelerra, Kdenlive) from corrupted or missing dependencies. In another thread while trying to install Cinelerra, it was recommended that I remove Cinelerra Which was looking for an old version of the x264 libraries, then x264, and ffmpeg. I did all of this and the only thing I have been able to re-install was x264. ffmpeg fails because of a missing texlive. So I went looking for that and found it was a 1.3GB install! What in the world is that? Why would ffmpeg need that?

Can anyone give me some advice on reinstalling ffmpeg, which is a dependency of Cinelerra which is my ultimate aim.

Any help is appreciated.

Bob

from slackbuilds.org's readme

Thank you, I read that as well. My question is that no other version of ffmpeg I have ever installed needed texlive, the most recent was Alien Bob's version (0.5). Why does it need it now? And if I have to install it, can it be installed from my home directory because I would not have room in /tmp.

Bob

you can build it also with tetex (already in slackware), texlive is only an alternative.

The exact reason for my question. Tetex IS installed but the build from SBopkg failed with a requirement for tetex or tetxlive. I can re-install Alien Bob's version, but would have rather had everything from SBo so that I can get a clean attempt to reinstall Cinelerra. If it is acceptable to build with just tetex, why isn't the build finding its presence?

Bob

Hi Bob

Using ffmpeg does not require texlive or tex at all. It is just while compiling ffmpeg, that tex (or texlive) must be present in order to compile the manpages for ffmpeg.

Note that tex is part of Slackware, so if you did a full install then you will not have to install the 3rd party texlive at all.
If you don't care about man pages, then you can also wrap the lines in the ffmpeg.SlackBuild which search for and compress the man pages, in ( ) like this:
This effectively prevents the SlackBuild script from exiting prematurely in case no man page could be found below $PKG/usr/man

Eric

1 members found this post helpful.

Thanks, Eric.

If you don't mind, can you tell me where to put this? Do I put it inside the build script or just wrap that section of the script?

Thanks for your help.

Bob

I think because you haven't become root with
that gives you a login root shell instead of just

Thank you, I finally installed ffmpeg, but, once again it was all to no avail. Cinelerra STILL will not compile.

Once again, I kept getting:

throughout the compile, ending in failure.

I probably should just give up. It's been weeks of trying to get either Cinelerra or Kdenlive installed again. I have both installed on a Ubuntu install on another machine, so I guess I am relegated to using that. I tried so hard to get them installed on Slack because when I used to have them they ran so much better in Slack.

Oh well.....

Thanks for your help

Bob

Hi Bob,
I had the same problem days ago, but at the end I got cinelerra-2.1.5 (and also kino) working with the latest kde-4.8.2 compiled by Pat.
I'm using ffmpeg-0.6.3-x86_64-1alien. I can't remember what exactly I have done.. I'm not sure but I faced that compilation problem too, and that issue should be caused by this bug http://sources.gentoo.org/cgi-bin/vi...patch?view=log

I think that you have to build v. 2.1.5 and not 2.2.0 because you have to apply patches against ffmpeg and vfl1 removal (the bug above http://sources.gentoo.org/cgi-bin/vi...nelerra/files/), which are both included in the SBo tar.

In addition, if you use Eric's multilib, you may have to add this to your configure

In my case it was looking for X libraries in /lib instead of /lib64.

@bob: FYI, I had all the deps installed here on 64-current multilib, so I tried a build using slackbuilds.org's script and adding only the line above to the configure (shouldn't be needed on pure 32 or 64 slackware) and all went fine.

It just complained, but only after starting the application, to increase a proc value (/proc/sys/kernel/shmmax) this way
done it (as root) and now it's happy

Thank for the reply, but I was building 2.1.5. I don't believe I need any patches as I am using a pure 32bit system (no multilibs). It looked like a gcc error, not sure as I don't have too much experience in investigating failed builds.

I believe I might try getting the source file from the Cinelerra-CV site and using scr2pkg to make a slackpkg. It couldn't hurt, nothing else has seemed to help.

Thanks again,

Bob

Thanks, yes, that is common on Slack to have to enter that line before starting Cinelerra. When I had it installed last time I had to do it each time I started Cinelerra. Problem is, I just can't get it installed at all. I am not using multilib, I am on a strictly 32bit system.

Thanks again

Bob

Well, creating a package with src2pkg at least gave the appearance that it was installing. But when I run it,

I have libavcodec libraries installed. This is no longer worth it. I don't remember ever having this much trouble getting anything installed.

those patches should be applyed in any case, you can find them in the SBo