On Fri, 2010-10-08 at 09:22 -0700, Arjan van de Ven wrote: > On 10/8/2010 6:41 AM, Mathieu Desnoyers wrote: > because that is not workable... at least nobody has shown to be able to > make this work. > libraries (after compilation) live in /lib or /usr/lib (or lib64 I > suppose)..... > what mechanism ensures that a user who compiles his kernel gets a > library compatible with that kernel in /usr/lib? > and can said library deal with older kernels too? And distro kernels? Perhaps we should have "make install" of a kernel also install this library? Have two libraries? One that is linked to the app, the other that can search for another library to link on load too (like a kernel.ld.so) Then we could see the kernel version, and search for a library that is compatible, and load that one. The app only needs to worry about loading the generic library. The generic library can test for compatible libraries for the kernel. Could just be.. libkernel.ld.so which then loads.. /lib/modules/2.6.36/libkernel.so Just a little brain storming. -- Steve -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
