i would say that Debian has a pretty well established system to avoid
breakage of applications due to library incompatibilities. I'm dense. Would you mind pointing out the part of the Pd-l2ork build systemwhere Ivica is linking the wrong way, and maybe explain what to replace thatcode with in order to leverage this "well established system" such that a binaryfrom 2013 works on Jessie today? Thanks,Jonathan
On Monday, September 21, 2015 3:19 AM, IOhannes m zmoelnig <zmoelnig@iem.at> wrote:
On 2015-09-21 03:42, Ivica Ico Bukvic wrote:
I think that was because it was built with libMagick++4 whereas 14.04 and newer Ubuntu versions have libMagick++5. I am not sure why this matters (sounds to me like something may be improperly symlinked system-wise).
i would say that Debian has a pretty well established system to avoid breakage of applications due to library incompatibilities.
part of this scheme is to rename library packages (e.g. "libMagick++4" vs "libMagick++5") if and only if the two libraries are binary incompatible. usually this means that some previously exported symbols have vanished in the newer version.
a specific application might not use those symbols at all and would thus not be affected by the incompatibility. but using symlinks (system-wide!) is certainly the right approach to break your system, and thus should be avoided.
there are two solutions for this problem:
- ship all dependencies (the w32 and OSX way)
- link against the proper libraries (the linux distro way)
fgmadrt IOhannes
Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list