[vdr] why I must first compile xine-lib£¬not ffmpeg?

Niels Wagenaar n.wagenaar at xs4all.nl
Mon Feb 9 08:27:41 CET 2009


Op Ma, 9 februari, 2009 08:07, schreef LinHai:
>
> when I first compile xine-lib is OK£¬second compile ffmpeg  is OK.
>
> IF I first compile ffmpeg is OK£¬second compile xine-lib  is failure.
>
> the syslog:
>
> make[2]: *** [xineplug_decode_faad_la-xine_faad_decoder.lo] Error 1
> make[2]: Leaving directory `/root/xine-lib-1-2-926ee2edf0d8/src/audio_dec'
> make[1]: *** [all-recursive] Error 1
> make[1]: Leaving directory `/root/xine-lib-1-2-926ee2edf0d8/src'
> make: *** [all-recursive] Error 1
>
> why ,who can tell me?

Based upon assumption, I think you're using the SVN/Trunk editions of
xinelib 1.2 and FFMpeg.

In that case, it's simple. In your first 'example' xinelib links/compiles
to an older and allready installed version of ffmpeg, you then install a
newer version of ffmpeg (prepare for problems with xinelib!). With your
2nd 'example' you've updated ffmpeg first and then xinelib will try to
compile/link against the updated ffmpeg libraries, which will then fail.

Sollution for this is simple. Stick to the stable xinelib 1.1.x editions
and *do not* use the --external-ffmpeg configure flag.

I've got the feeling that the ffmpeg trunk has been updated again and that
it broke the of xinelib 1.2. Figures, since it's all bleeding edge we're
talking here and it has happened before ;)

Regards,

Niels Wagenaar







More information about the vdr mailing list