Relinking binaries to new .so libs when versions change?

[Dan Nelson]

In the last episode (Sep 18), Andrew J Caines said:
> Again, a port update of a library has bumped a .so version [in this case
> libatk-1.0.so.200 -> libatk-1.0.so.400]. This leaves a bunch of binaries
> linked to the old .so which won't start.

how did you update the port?   Portupgrade moves old libraries into
/usr/local/lib/compat/pkg so old programs can still link to them.  Or
you could run portupgrade -R, which will upgrade all the packages
dependent on the one you list.

> Is there an elegant and quick way to relink a given binary to a
> different version of a particular .so, eg. "mvld foo foo.so.1
> foo.so.2"?

Version numbers get bumped for a reason :)  Running the wrong version
library will usually result in a coredump or runtime linking error.

-- 
	Dan Nelson
	dnelson at allantgroup.com