DISQUS

DISQUS Hello! Encoded is using DISQUS, a powerful comment system, to manage its comments. Learn more.

Community Page

Encoded

my digital life by gregory tomlinson
Jump to original thread »
Author

Installing FFMPEG on CentOS 5

Started by gregory · 6 months ago

I recently had the need to install FfMpeg for a project I am working on. After Googling for some time I learned a little bit about the ffmpeg project. The most interesting thing I learned was their are no formal releases of the project. So I just downloaded it from SVN using the following command: ... Continue reading »

6 comments

  • WHen I try to compile I get the following error:

    In file included from libavdevice/v4l.c:32:
    /usr/include/linux/videodev.h:56: error: syntax error before "ulong"
    /usr/include/linux/videodev.h:72: error: syntax error before '}' token
    libavdevice/v4l.c: In function `grab_read_header':
    libavdevice/v4l.c:77: error: storage size of 'tuner' isn't known
    libavdevice/v4l.c:141: error: invalid application of `sizeof' to incomplete type `video_tuner'
    libavdevice/v4l.c:148: error: invalid application of `sizeof' to incomplete type `video_tuner'
    libavdevice/v4l.c:77: warning: unused variable `tuner'
    make: *** [libavdevice/v4l.o] Error 1



    Do you have any idea what the problem is?
  • I get the EXACT same error on Centos 4.6
  • So I decided to export an arbitrary revision number (14000), and it worked!

    So somewhere between 14000 and 15290 (HEAD as of this writing) something got BORKED. But what can you expect from a project with no stable releases?
  • @ retry

    you might try checking this post: http://gregorytomlinson.com/encoded/2008/06/11/...

    Some of this has been discussed there
  • Yeah but my problem wasn't related to trying to get extra codecs working. It's an error in some device code in the core ffmpeg. I was getting that error with a vanilla configuration.
  • commented out line 56 (ulong blah) and it compiled.

    can't tell you if it worked, though... and that's almost certainly the wrong way to fix it.

Add New Comment

Returning? Login