FFmbc v0.2 Make Fails - x264 (r1318) error

[GoogleCodeExporter]

What steps will reproduce the problem?

1. Download x264 from Git. Problem occurs with r1318

2. Configure FFmbc:

aptitude install build-essential subversion git-core yasm libgpac-dev
libdirac-dev libgsm1-dev libschroedinger-dev libspeex-dev libvorbis-dev
libopenjpeg-dev libdc1394-dev libsdl1.2-dev zlib1g-dev texi2html
libfaac-dev libfaad-dev libmp3lame-dev libtheora-dev libxvidcore4-dev
libopencore-amrnb-dev libopencore-amrwb-dev

3. make install

4. Make then fails with the following error:

libavcodec/libx264.c: In function ‘encode_nals’:
libavcodec/libx264.c:75: warning: implicit declaration of function
‘x264_nal_encode’
libavcodec/libx264.c: In function ‘X264_init’:
libavcodec/libx264.c:190: error: ‘x264_param_t’ has no member named
‘b_bframe_pyramid’
make: *** [libavcodec/libx264.o] Error 1


What is the expected output? What do you see instead?

Expected FFmbc to build without errors.


What version of the product are you using? On what operating system?


Running Ubuntu Karmic Koala Netbook Remix on a Asus EeePC 1005HA

Original issue reported on code.google.com by phillclarke@gmail.com on 6 Nov 2009 at 4:38

[GoogleCodeExporter]

Stupid me copied and pasted the incorrect thing. I was configuring FFmbc with 
the
following:

/configure --enable-gpl --enable-postproc --enable-pthreads --enable-libfaac
--enable-libfaad --enable-libmp3lame --enable-libtheora --enable-libx264
--enable-shared --enable-nonfree --enable-libvorbis --enable-libgsm 
--enable-libspeex
--enable-libschroedinger --enable-libdirac --enable-avfilter 
--enable-avfilter-lavf
--enable-libdc1394 --enable-libopenjpeg --enable-libopencore-amrnb
--enable-libopencore-amrwb --enable-version3 

Original comment by phillclarke@gmail.com on 6 Nov 2009 at 4:47

[GoogleCodeExporter]

You have to use an older x264 version. This won't be fixed until next release 
(0.3)

Original comment by baptiste...@gmail.com on 10 Nov 2009 at 1:26

• Changed state: WontFix

[GoogleCodeExporter]

Yes you are absolutely right .. even i did face this Issue.. 

turned out it worked fine with the older version of x264 source.. 

Original comment by kishore....@gmail.com on 30 Nov 2009 at 10:18