On Sun, 2008-07-06 at 23:18 -0700, Roland McGrath wrote: > > Using dsocaps gives you the best of both worlds. You can freely choose > new strings in the kernel without the ld.so code having to know about > them (which is not true of AT_PLATFORM, but may be true of how you are > thinking about "strings are nice"). You do have to map all the > possibilities that a single kernel build can produce into distinct bits. > But, there are 32 unallocated bits to start with. Moreover, those bit > assignments are not part of any permanent ABI like bits in AT_* values. > They just have to match up between this kernel build and the ld.conf.d > file installed along with it--kernel hackers and kernel packagers have > to coordinate, not kernel hackers and userland hackers.
I'm not sure... if ld.conf.d isn't parse of the kernel source tree then it -will- end in tears... Ben. _______________________________________________ Linuxppc-dev mailing list Linuxppc-dev@ozlabs.org https://ozlabs.org/mailman/listinfo/linuxppc-dev
