[MPlayer-users] compilation aborted with shared libavcodec

[D Richard Felker III]

On Wed, Sep 11, 2002 at 09:46:10PM +0200, Sylvain Petreolle wrote:
> [Automatic answer: RTFM (read DOCS, FAQ), also read DOCS/bugreports.html]
> > The problem is that you're trying to use a system-wide installed
> > libavcodec rather than compiling it as part of mplayer, AND you've
> > included liba52 in libavcodec. This will conflict with the copy of
> > liba52 inside mplayer and cause linking to fail. Either (preferably)
> > build libavcodec as part of mplayer (this will ensure that lavc cvs
> > gets updated to latest version whenever you update mplayer, which is
> > a
> > very good thing), or else build your system-wide copy of libavcodec
> > without liba52.
> > 
> System-wide are better, I think. This enable the to be used by every
> application that needs it.
> (NB: this is the thing that blocks m$'s Windows with bugs and bugs
> becvause every app installs its version of the library without doing a
> SIMPLE check ...)
> So must I remove the liba52 directory ?
> If so, another question points it out :
> is the liba52 included in mplayer up to date ?

No. Do not remove liba52 from mplayer! This will most likely not work
at all (not positive since I haven't read configure recently). Read
what I said! You have to either remove liba52 from libavcodec or else
build libavcodec as part of mplayer.

Again, the preferred method is to build it along with mplayer. The
windows analogy you are making is total nonsense and is not relevant
and amounts to blabbering back bits and pieces of what you've heard
without any real understanding of the issues at hand. MPlayer is NOT
going to install it's own version of the library and interfere with
other stuff like stupid windows programs; it is going to compile
libavcodec into the mplayer binary. In fact, the same would happen
with the system-wide copy you had, since it's .a (static lib) rather
than .so (shared).

*sigh*

Rich