Re: [Ekiga-list] H.264 codec issue fixed?

["Paulo R. Panhoto" <paulo voicetechnology com br>]

I am new to patching things this way, sorry for that. Anyway, I tried to
apply the patch to the dowloaded version (3.6.6) and to SVN HEAD
version. Both cases failed with this message:

paulo panhoto-lnx:~/sources/opal> patch -p0 <
~/Download/opal-fix_build.patch
patching file b/include/h323/h323ep.h
Hunk #1 FAILED at 60.
1 out of 1 hunk FAILED -- saving rejects to file b/include/h323/h323ep.h.rej
patching file b/plugins/video/H.264/shared/h264frame.cxx
Hunk #1 FAILED at 86.
Hunk #2 FAILED at 99.
2 out of 2 hunks FAILED -- saving rejects to file
b/plugins/video/H.264/shared/h264frame.cxx.rej


On 24/11/09 11:02, Eugen Dedu wrote:
> Paulo R. Panhoto wrote:
>   
>> Hello,
>>
>> I built ptlib/opal/ekiga from scratch along with ffmpeg/x264 to enable
>> the extra codecs. The packages ptlib/opal/ekiga were downloaded from the
>> website and ffmpeg/x264 were downloaded from version control (latest).
>> Everything compiled fine and, when I tried to run Ekiga, I've got these
>> messages:
>>
>> paulo panhoto-lnx:/usr/lib/opal-3.6.6/codecs/video> ekiga -d 5 2>&1 |
>> grep H264
>>         dyna.cxx(390)    H264    DYNA    Successfully loaded libavcodec
>> library and verified functions
>> h264pipe_unix.cxx(301)    H264    IPC    PP: Found GPL process
>> executable in  /usr/lib/opal-3.6.6/codecs/video/h264_video_pwplugin_helper
>> x264loader_unix.cxx(114)    H264    DYNA    Trying to open x264 library
>> libx264.so.79
>> x264loader_unix.cxx(131)    H264    DYNA    Successfully loaded
>> libx264.so.79
>> x264loader_unix.cxx(57)    H264    DYNA    Failed to load x264_encoder_open
>> h264helper_unix.cxx(127)    H264    IPC    CP: Failed to load dynamic
>> library - exiting
>> h264pipe_unix.cxx(113)    H264    IPC    PP: GPL Process returned
>> failure on initialization - plugin disabled
>>    h264-x264.cxx(838)    H264    Codec    Disabled
>>
>> After some web search, I found this link:
>> <https://bugzilla.gnome.org/show_bug.cgi?id=596006>, which relates to
>> the problem.
>>
>> What I didn't understand is whether the website sources include the
>> patch created for this bug or if I should get opal from the VCS.
>>     
> Hi,
>
> The patch given in this bug is not (yet) committed (elsewhere the bug
> would have been closed).  Apply it and tell us if it works for you.
>
> Thanks,
>