Quote:
Originally Posted by knc1
The K3, v-3.2.1 image I am looking at looks to have a number of "strange things" about its library installation. Both in the compiler search path(s) and the runtime loader's search path(s).
Almost as if lab126 was only concerned about making their own software work and to H... with anyone else's.
For instance, the contents of /etc/ld.so.conf does not correspond to the library installation locations - unless they have some "invented here" program diddling with the run-time loader.
Unfortunately, my K3 is "out of service" for a photo shoot, so I can't actually check its behavior.
|
Another good reason to static link all your apps so they don't need any external loadable libraries. I like static linking so my apps will run on any eink kindle, with no worries about library version mismatch errors, but missing symlinks and other amazon screwups is yet another reason to static link.