On Sat, 20 Feb 2016, Bruce Fischl wrote:
hmmm, the only thing that worries me about dynamic linking is that it will add variability to the outputs. Zeke has spent endless amounts of time tracking down e.g. mac vs. pc differences in math libs and such. Won't dynamic linking just make that a much more prevalent problem?
nope -- I am not talking about dynamically linking external libraries ATM, but first about the internal ones, where the common code where instead of absorbing the same .a or .o blobs into multiple binaries, there would be a set of internal dynamic libraries which those binaries would be linked against, so there will no copies of binary code among different binaries. I guess https://www.gnu.org/software/automake/manual/html_node/Libtool-Convenience-L... is a quick intro into those.
As for linking against external libraries -- those could be bundled along with rpath pointing to their location or LD_LIBRARY_PATH override assuring they are picked up (instead of possibly available identically named system-wide ones).
So overall it is possible to achieve absent variability while using dynamic linking and allowing for possibility of the flexibility ;)
Cheers