Re: Relinking binaries to new .so libs when versions change?

Dan, Thanks for your reply. 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]. how did you update the port? ... Or you could run portupgrade -R, which will upgrade all the packages dependent on the one you list. # portupgrade

Relinking binaries to new .so libs when versions change?

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. Other recent examples include libxmms.so and libintl.so. Is there an elegant and quick way to relink a given

Re: Relinking binaries to new .so libs when versions change?

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