On Wed, May 28, 2014 at 5:17 PM, Marcus Müller <[email protected]> wrote:
> -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > To explain: Binaries are generally linked against binaries, ie. > against a certain set of symbols only present in a certain build of a > binary; thus, usually libraries link against specific versionized > libraries. > > If you update a library, binaries linked against the old version are > bound to stop working. In most unixoid systems, this is circumvented > (sometimes) by having the ability to have multiple libraries in > different versions installed [1](libgrandmascheesecake.so.1.0.0, > libgrandmascheesecake.so.1.1.2) and a symlink from the general name to > the recent one (libgrandmascheesecake.so -> > libgrandmascheesecake.so.1.1.2). However, usually you don't want to > have conflicting versions, so package management usually goes miles to > ensure that all packages in a certain distribution version are built > against the same library version. > > Greetings, > Marcus > > [1] windows-y systems usually ship all the libraries in the same > directory as the executable, which is --from a storage point of view-- > quite like static linking. > Thank you very much.
_______________________________________________ Discuss-gnuradio mailing list [email protected] https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
