Bug 606002 - libvpx-0.9.0 is too old for FFmpeg-0.6, update to 0.9.1
Summary: libvpx-0.9.0 is too old for FFmpeg-0.6, update to 0.9.1
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: libvpx
Version: rawhide
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Tom "spot" Callaway
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-06-19 21:26 UTC by Dominik 'Rathann' Mierzejewski
Modified: 2010-07-15 21:04 UTC (History)
4 users (show)

Fixed In Version: libvpx-0.9.1-2.fc12
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-07-07 17:41:50 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Dominik 'Rathann' Mierzejewski 2010-06-19 21:26:55 UTC
Description of problem:
FFmpeg-0.6 fails to build against libvpx-0.9.0. I've prepared my own 0.9.1 package and FFmpeg builds fine against it. Please update.

Version-Release number of selected component (if applicable):
libvpx-0.9.0-5.fc12

How reproducible:
Always

Steps to Reproduce:
1. unpack FFmpeg-0.6 source
2. ./configure --enable-libvpx
  
Actual results:
ERROR: libvpx not found

Expected results:
Should build normally.

Additional info:
check_cc
BEGIN /tmp/ffconf.LXt4ankr.c
    1   
    2   #include <vpx/vpx_encoder.h>
    3   #include <vpx/vp8cx.h>
    4   int main(int argc, char **argv){
    5       return (long) vpx_codec_enc_init_ver;
    6   }
END /tmp/ffconf.LXt4ankr.c
gcc -D_ISOC99_SOURCE -D_POSIX_C_SOURCE=200112 -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -DPIC -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector --param=ssp-buffer-size=4 -m64 -mtune=generic -std=c99 -fomit-frame-pointer -fPIC -pthread -I/usr/include/dirac -I/usr/include/schroedinger-1.0 -I/usr/include/liboil-0.3 -c -o /tmp/ffconf.cENFYd8T.o /tmp/ffconf.LXt4ankr.c
In file included from /tmp/ffconf.LXt4ankr.c:2:
/usr/include/vpx/vpx_encoder.h:84: error: expected '=', ',', ';', 'asm' or '__attribute__' before 'vpx_codec_pts_t'
/usr/include/vpx/vpx_encoder.h:132: error: expected specifier-qualifier-list before 'vpx_codec_pts_t'
/usr/include/vpx/vpx_encoder.h:142: error: expected specifier-qualifier-list before 'uint64_t'
In file included from /tmp/ffconf.LXt4ankr.c:2:
/usr/include/vpx/vpx_encoder.h:690: error: expected declaration specifiers or '...' before 'vpx_codec_pts_t'
ERROR: libvpx not found

Comment 1 Tom "spot" Callaway 2010-06-24 14:04:50 UTC
Sorry for the delay here, was on vacation. Updates coming now.

Comment 2 Fedora Update System 2010-06-28 18:57:44 UTC
libvpx-0.9.1-2.fc12 has been submitted as an update for Fedora 12.
http://admin.fedoraproject.org/updates/libvpx-0.9.1-2.fc12

Comment 3 Fedora Update System 2010-06-28 18:58:55 UTC
libvpx-0.9.1-2.fc13 has been submitted as an update for Fedora 13.
http://admin.fedoraproject.org/updates/libvpx-0.9.1-2.fc13

Comment 4 Fedora Update System 2010-06-28 23:36:59 UTC
libvpx-0.9.1-2.fc13 has been pushed to the Fedora 13 testing repository.  If problems still persist, please make note of it in this bug report.
 If you want to test the update, you can install it with 
 su -c 'yum --enablerepo=updates-testing update libvpx'.  You can provide feedback for this update here: http://admin.fedoraproject.org/updates/libvpx-0.9.1-2.fc13

Comment 5 Fedora Update System 2010-06-29 15:30:23 UTC
libvpx-0.9.1-2.fc12 has been pushed to the Fedora 12 testing repository.  If problems still persist, please make note of it in this bug report.
 If you want to test the update, you can install it with 
 su -c 'yum --enablerepo=updates-testing update libvpx'.  You can provide feedback for this update here: http://admin.fedoraproject.org/updates/libvpx-0.9.1-2.fc12

Comment 6 Fedora Update System 2010-07-07 17:41:39 UTC
libvpx-0.9.1-2.fc13 has been pushed to the Fedora 13 stable repository.  If problems still persist, please make note of it in this bug report.

Comment 7 Fedora Update System 2010-07-15 21:04:27 UTC
libvpx-0.9.1-2.fc12 has been pushed to the Fedora 12 stable repository.  If problems still persist, please make note of it in this bug report.


Note You need to log in before you can comment on or make changes to this bug.