I found this one out the hard way. The problem occurs when the update results 
in a shared library being installed with a different revision number. 
Dependent code still references the library with the old number, yet, with 
the "make replace" you delete the old and install the new.

On Tuesday 05 October 2004 09:22 am, Pavel Cahyna wrote:
> On Mon, 04 Oct 2004 17:43:41 +0000, Richard Rauch wrote:
> >  * Use "make replace" on key libraries that you know or
> >    suspect will need to be updated.  (Note that this is a
> >    bit dangerous, but lets you get the library updated
> >    without rebuilding everything that it requires.)
>
> Why is it a bit dangerous? I never saw an explanation.
>
> Bye Pavel

-- 

John R. Shannon
john@johnrshannon.com