>>It's either this or they have to static link! This would turn it into
>>real big bloat-ware, it is very large. 5.0's installation program
>>is more complete, but you still have to set LD_LIBRARY_PATH and,
>>if you want their library cached, fix up /etc/ld.so.config.
> And what is the difference between static linking, and dynamic
> linking that requires a specially distributed shared library that
> must be used?
> I fail to see the difference. If the shared library isn't the
> one that everything else on the system uses, then IT ISN'T
> SHARED. In other words, if commercial program A required library
> B to be used, and only program A is using it, then nothing is
> sharing the library, and the application might as well statically
> link in the first place as it will consume the same resources,
> and perhaps be a bit slower due to dynamic linking.
Not at all :-)) It's not uncommon to have more then one executable in single
product (see BlackDown JDK for example). Even if there are special version
of glibc provided (actually just late version of glibc 2.0.7) it's still win
since few programs from the same product can use SHARED library...
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/