Date: Fri, 19 Sep 2003 00:55:19 -0500 From: Dan Nelson <dnelson@allantgroup.com> To: FreeBSD Hackers <FreeBSD-Hackers@FreeBSD.org> Subject: Re: Relinking binaries to new .so libs when versions change? Message-ID: <20030919055519.GL51544@dan.emsphone.com> In-Reply-To: <20030919010534.GE1234@hal9000.halplant.com> References: <20030919010534.GE1234@hal9000.halplant.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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@allantgroup.com
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030919055519.GL51544>