: Re: [MPlayer-users] mplayer takes all RAM over a few days

[Martin Simmons]

>>>>> On Thu, 6 Oct 2005 22:07:35 -0400, Rich Felker <dalias at aerifal.cx> said:

> On Thu, Oct 06, 2005 at 11:15:26AM -0400, The Wanderer wrote:
> > RC wrote:
> > 
> > >On Thu, 06 Oct 2005 09:00:33 -0400 The Wanderer
> > ><inverseparadox at comcast.net> wrote:
> > >
> > >>(Well... you could hardlink every file in the directories
> > >>individually, whether manually (impractical!) or by script, but
> > >>that seems like a lot more effort than it would be worth.)
> > >
> > >"lndir"
> > >
> > >Symlinks, not hardlinks, but it should work.
> > 
> > I'm aware of lndir, yes. As you noted, it creates symlinks, and I was
> > specifically talking about hardlinks - since allegedly, for whatever
> > reason (in this case, perhaps datestamp/timestamp differences, meaning
> > that changes in the target files won't be noticed as "file altered" for
> > the symlinks by make?), symlinks will not work.

> I read the configure script and can't figure out why it would fail
> with symlinks... Does anyone have an idea?

I think the problem is in make, not configure.

Using lndir to point into an ffmpeg that has been configured/built standalone
will also create symlinks to all the .o/.a files from that configuration and
mplayer's make will not recompile them.

__Martin