Comment 32 for bug 1300211

Can someone please explain why /usr/include/asm is needed? It seems to me neither gcc -m32 nor gcc -m64 use it (both finding the ones in /usr/include/i386-linux-gnu and /usr/include/x86_64-linux-gnu instead).

arm-linux-gnueabihf-gcc finds it which is not correct, but can be fixed easily enough by sym-linking /usr/include/arm-linux-gnueabihf to /usr/arm-linux-gnueabihf/include.

From what I can see, the only things ever finding /usr/include/asm are things which should definitely not be using it (cross compilers). If that is correct, removing that symlink from gcc-multilib should not break anything that's not already broken. And with it removed, the conflicts would no longer be necessary.

What am I missing?