[Ffmpeg-devel] Shared libraries install script broken in cvs

Jacob Meuser jakemsr
Fri Dec 16 05:41:28 CET 2005

On Fri, Dec 16, 2005 at 12:21:13AM +0000, M?ns Rullg?rd wrote:
> "John C. McCabe-Dansted" <gmatht at gmail.com> writes:
> > On Friday 16 December 2005 11:53, M?ns Rullg?rd wrote:
> >> Diego Biurrun <diego at biurrun.de> writes:
> >> > OK, let me ask more directly: Are you in favor of dropping ldconfig and
> >> > creating those symlinks ourselves?
> >>
> >> I'd be happy with it.  It would save me the trouble of creating the
> >> links myself, or running ldconfig manually.  If someone is strongly
> >> opposed to this idea, I'm fine with using modified makefiles myself.
> >
> > Another way would be to explicitly tell ldconfig what our lib path is. E.g. 
> > running
> > 	ldconfig $(libdir)
> > Also fixes the problem.
> That will still fail trying to update the cache file if you are not
> root.

I would prefer that the ldconfig lines be dropped and symlinks not be
created at all.  really, people should know that they need to update
the cache when they add libraries, and they should know how to do
that on whatever OS they are using.

> It should also be noted that on FreeBSD, ldconfig never creates any
> links at all.  All it does is update a cache file.  The versioned
> filenames must exist before ldconfig is run.

same with OpenBSD.  there is no need for libfoo.so -> libfoo.so.X.X
symlinks, and it is preferred that all shared libraries have real
version numbers.  proper shared library versioning is important for
all OSes, actually:


I really think that trying to do this right for all OSes FFmpeg is
usable on is just going to create a mess (ever wonder why libtool is
7000 lines of shell?).

<jakemsr at jakemsr.com>

More information about the ffmpeg-devel mailing list