LinuxQuestions.org
Go Job Hunting at the LQ Job Marketplace
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices

Reply
 
LinkBack Search this Thread
Old 09-27-2013, 08:39 PM   #1
BoydRice
Member
 
Registered: Jul 2008
Location: Tacoma, WA
Distribution: Slackware64
Posts: 95

Rep: Reputation: 19
Error compiling ffmpeg via Slackbuilds.org using sbopkg


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.

Code:
doc/ffmpeg.pod around line 11765: Non-ASCII character seen before =encoding in '88'. Assuming UTF-8
POD document had syntax errors at /usr/bin/pod2man line 71.
make: *** [doc/ffmpeg.1] Error 255
 
Old 09-27-2013, 09:03 PM   #2
WhiteWolf1776
Member
 
Registered: Oct 2010
Location: Pittsburgh, PA
Distribution: Slackware
Posts: 169

Rep: Reputation: 46
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.
 
Old 09-28-2013, 01:23 AM   #3
ponce
Senior Member
 
Registered: Aug 2004
Location: Pisa, Italy
Distribution: Slackware
Posts: 2,315

Rep: Reputation: 816Reputation: 816Reputation: 816Reputation: 816Reputation: 816Reputation: 816Reputation: 816
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.
Old 09-28-2013, 03:16 PM   #4
cisneros
Member
 
Registered: Jul 2012
Distribution: Slackware
Posts: 95

Rep: Reputation: 5
i compiled it with the lastest version from the ffmpeg site and using the same slackbuild, no problem at all so far.
 
Old 09-28-2013, 04:10 PM   #5
Kallaste
Member
 
Registered: Nov 2011
Posts: 343

Rep: Reputation: Disabled
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.
Old 09-28-2013, 09:08 PM   #6
BoydRice
Member
 
Registered: Jul 2008
Location: Tacoma, WA
Distribution: Slackware64
Posts: 95

Original Poster
Rep: Reputation: 19
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!
 
Old 11-10-2013, 10:12 PM   #7
astrogeek
Senior Member
 
Registered: Oct 2008
Distribution: Slackware: 12.1, 13.0, 13.1, 13.37, 14.0, 64-14, -current
Posts: 1,511

Rep: Reputation: 509Reputation: 509Reputation: 509Reputation: 509Reputation: 509Reputation: 509
Quote:
Originally Posted by ponce View Post
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).
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...
Code:
sed -i 's//x/' doc/filters.texi
That allowed it to complete...

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

Last edited by astrogeek; 11-10-2013 at 11:13 PM.
 
Old 11-10-2013, 11:44 PM   #8
ponce
Senior Member
 
Registered: Aug 2004
Location: Pisa, Italy
Distribution: Slackware
Posts: 2,315

Rep: Reputation: 816Reputation: 816Reputation: 816Reputation: 816Reputation: 816Reputation: 816Reputation: 816
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 )

Code:
git clone git://slackbuilds.org/slackbuilds.git slackbuilds-clone
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

Last edited by ponce; 11-10-2013 at 11:45 PM.
 
1 members found this post helpful.
Old 11-11-2013, 12:04 AM   #9
astrogeek
Senior Member
 
Registered: Oct 2008
Distribution: Slackware: 12.1, 13.0, 13.1, 13.37, 14.0, 64-14, -current
Posts: 1,511

Rep: Reputation: 509Reputation: 509Reputation: 509Reputation: 509Reputation: 509Reputation: 509
Quote:
Originally Posted by ponce View Post
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 )

Code:
git clone git://slackbuilds.org/slackbuilds.git slackbuilds-clone
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
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...

Last edited by astrogeek; 11-11-2013 at 12:36 AM.
 
Old 11-12-2013, 10:54 AM   #10
hpfeil
Member
 
Registered: Nov 2010
Location: Tucson, Arizona US
Distribution: Slackware Current, custom kernel, amd64, Beyond LinuxFromScratch
Posts: 115
Blog Entries: 1

Rep: Reputation: Disabled
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!
 
Old 11-14-2013, 11:36 AM   #11
hpfeil
Member
 
Registered: Nov 2010
Location: Tucson, Arizona US
Distribution: Slackware Current, custom kernel, amd64, Beyond LinuxFromScratch
Posts: 115
Blog Entries: 1

Rep: Reputation: Disabled
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.
 
Old 11-17-2013, 11:59 PM   #12
seroabsoluto
LQ Newbie
 
Registered: Apr 2010
Posts: 1

Rep: Reputation: 0
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
 
Old 11-18-2013, 12:02 AM   #13
ponce
Senior Member
 
Registered: Aug 2004
Location: Pisa, Italy
Distribution: Slackware
Posts: 2,315

Rep: Reputation: 816Reputation: 816Reputation: 816Reputation: 816Reputation: 816Reputation: 816Reputation: 816
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
 
Old 11-18-2013, 12:12 AM   #14
astrogeek
Senior Member
 
Registered: Oct 2008
Distribution: Slackware: 12.1, 13.0, 13.1, 13.37, 14.0, 64-14, -current
Posts: 1,511

Rep: Reputation: 509Reputation: 509Reputation: 509Reputation: 509Reputation: 509Reputation: 509
Quote:
Originally Posted by seroabsoluto View Post
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
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!
 
  


Reply

Tags
ffmpeg, slackbuilds


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off
Trackbacks are Off
Pingbacks are On
Refbacks are Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
[SOLVED] Slackware64 14, problems with compiling packages from slackbuilds.org Chelyuk Slackware 33 10-05-2012 12:21 AM
SlackBuilds.org and sbopkg suggestion vharishankar Slackware 2 11-02-2011 09:14 PM
ffmpeg slackbuilds.org script failure TL_CLD Slackware 7 07-16-2010 12:45 AM
[SOLVED] ffmpeg install error from SlackBuilds eraosso Slackware 7 11-05-2009 07:23 PM
error compiling lablgtk on Slack 11 using SlackBuild from slackbuilds.org BCarey Slackware 1 02-22-2008 10:57 AM


All times are GMT -5. The time now is 08:40 PM.

Main Menu
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration