Hi All,

I am trying to build VLC via Slackbuilds with sbopkg. I keep getting the following error when trying to compile ffmpeg. I am running Slackware64 -current using the Slackware 14 repo from Slackbuilds.org. Any ideas or suggestions? Error below.

perl issues... go to ffmpeg site and update the slackbuild to compile latest version, should be 2.0. I'm running it now, works great with -current.

if you update it for a newer major version (1.x, 2.x), most of the stuff on SBo depending on it probably won't build/work anymore.

locally, I've updated it for version 0.11.4 and wrote a little patch removing the disturbing char (you can patch -p3 the build script on SBo with this).

1 members found this post helpful.

i compiled it with the lastest version from the ffmpeg site and using the same slackbuild, no problem at all so far.

Or you could grab AlienBOB's package off his restricted slackbuilds page. He has ffmpeg and vlc already built. Easier.

1 members found this post helpful.

Thanks All, I tried upgrading the Slackbuilds repo to the unsupported git one, got some different errors so I gave up and installed AlienBob's packages. Marking this solved. thanks!

I am trying to accomplish the same thing and would prefer to build rather than use Alien Bob's pre-built package in this case.

Your patch link above is broken - could you clue me in on what that problem is please, ponce?

Thanks
[*** UPDATE ***]

I managed to stumble my way through the code and found the offending character. Rathar than make a patch I simply added the following line to the Slackbuild just after the archive is unpacked and we have changed into the ffmpeg tree...
That allowed it to complete...

The character is #215 Hex #0d7 and occurs only in one place in one file.

I've removed it because pprkut opted to go forth to ffmpeg-2.1 in SlackBuilds.org's git master branch (that will become the one dedicated to 14.1).

if you want to follow that choice (and I think it will be the most sane decision as SBo packages will be built/tested against that), just clone locally the git master repository and use its scripts (that will help also the testing to go toward a release of a 14.1 repo )

to update them, go in the cloned folder and use "git pull".

or, if you use sbopkg, you can also setup that as a repository to build stuff through it: I've prepared a very small guide for that

http://pastebin.com/jRPYQsVL

1 members found this post helpful.

Actually, I am rebuilding all my own SBo packages today for 14.1, and most others I use, and thought I looked for a new ffmpeg and did not find it... I'll look again.

... building now...

I'm reminded of the ffmpeg-libav split. I just did a kdiff3 on ffmpeg-2.1/libavcodec/ vs. libav-0.8.9/libavcodec/. A quick glance at the result showed no green boxes for both files. Either red boxes on one with green boxes on the other (libav-0.8.9 is 11/04 while ffmpeg-2.1 is 10/11), those will need a manual comparison; there are files on one tree missing from the other, some ffmpeg, others libav: the entire x86 folders are different, ffmpeg missing .asm files, libav missing .c files for example. I only mention it because the libav `configure --help` lists an option to include ffmpeg or not. I haven't pursued the matter, perhaps you need both trees in the same compile folder, or maybe libav looks for an installed ffmpeg?

There's a fork therein, with no clue as to which one is being actively developed or why files are missing from one and not the other. You may find me late at night with a candle burning on top of my roll-top desk pouring over the two changelogs, comparing files, or, more likely, asleep dreaming of writing my own multimedia program out of merged code; part ffmpeg, part libav.

https://lwn.net/Articles/423705/
https://lists.ffmpeg.org/pipermail/f...ry/106508.html

On the bright side, 14.1 works flawlessly as advertised. No complaints, just kudos!

My post regarding libav vs ffmpeg was meant only as information, not recommendations. My personal preference is ffmpeg because it has more features. When I compiled the libav-0.8.9 package, a number of issues presented themselves. There are libraries in the source tree that will halt `configure` because it expects to find those libraries already installed. After I finally had all of the features with source code in the libav tree removed from my configure command, I suspect that I could have left all of the `configure --help` options behind; the script is smart enough to find what it needs. Make was fun, screen-full after screen-full of warnings flew by, most were pointing out the use of deprecated symbols, some were variables declared yet never used. A full re-write against GTK3 might help. Ffmpeg's make was much less fun. Herr Niedermayer's project management skills aside, he knows ffmpeg.

I have compile ffmpeg from slackbuilds.org, generated this error:

warning: Must specify a title with a title command or @top
doc/syntax.texi:147: warning: Accent command `@"' must not be followed by whitespace
POD doc/ffmpeg.pod
MAN doc/ffmpeg.1
doc/ffmpeg.pod around line 11765: Non-ASCII character seen before =encoding in '8�8'. Assuming UTF-8
POD document had syntax errors at /usr/bin/pod2man line 71.
make: *** [doc/ffmpeg.1] Error 255

you probably are building it using the script for slackware-14.0 on slackware-14.1: either you wait until the repository for 14.1 goes online or you follow these instructions

See my own post #7 above, click here to build using the SBo 14.0 script, or follow ponce's instructions to get the new slackbuild from the pending SBo repo.

I have built ffmpeg 2.1 from the unreleased SBo script (per ponce) and it builds fine - but will not be compatible with other apps from older SBo scripts.

But it looks like the SBo 14.1 repo is shaping up quickly, lots of work going into it!