Comment 13 for bug 343602

The proposed changes "worked" on my babbage board in that the resulting libc6 and libc6-vfp packages would still work as before, I could run and reboot the system just fine.

"LD_HWCAP_MASK=0x1040 ldconfig" passes (NEON + VFP), but doesn't change anything as obviously I don't have NEON libs.

I created /lib/neon and copied /lib/vfp/libm.so* to it and ran the above ldconfig; then I got:
% ldconfig -p | grep libm.so
        libm.so.6 (libc6, hwcap: 0x0000000000001000, OS ABI: Linux 2.6.16) => /lib/neon/libm.so.6
        libm.so.6 (libc6, hwcap: 0x0000000000000040, OS ABI: Linux 2.6.16) => /lib/vfp/libm.so.6
        libm.so.6 (libc6, OS ABI: Linux 2.6.16) => /lib/libm.so.6
        libm.so (libc6, OS ABI: Linux 2.6.16) => /usr/lib/libm.so

vim uses libm; I don't know how the selection is performed:
% ldd /usr/bin/vim | grep libm
        libm.so.6 => /lib/vfp/libm.so.6 (0x402e6000)

ideally, neon would imply vfp and turn on this hwcap; I don't know how to achieve this with the current hwcap system. The best is probably to let neon version conflict with vfp versions, but it's suboptimal.