Multiarch paths and toolchain implications
ams at codesourcery.com
Mon Aug 2 13:21:59 BST 2010
On 02/08/10 12:46, Ulrich Weigand wrote:
> The second half of the section "Loading/running an executable" is about
> thw HWCAP stuff (look for "capability suffix"). In the summary I have
> this point:
> * If capability-optimized ISA/ABI-compatible library variants are desired,
> they can be build just as today, only under the (same) multiarch
> suffix. They could be packaged either within a single pacakge,
> or else using multiple packages (of the same multiarch type).
> If you feel this could be made clearer, I'd appreciate any suggestions :-)
OK, I'm clearly blind and incapable of performing a text search
competently (I swear I did one)!
It is buried a little deep, but it is there. I guess I'd like to see a
flow of how a binary loads libraries:
1. User launches binary.
2. Kernel selects a suitable execution environment (native/qemu).
3. Kernel reads .interp and loads the multiarch dynamic linker:
4. Dynamic linker uses HWCAP to find the most appropriate libc.so.
Anyway, that's just my personal taste. The information is there, if I
read it any time other than Monday morning, so I think the document is good.
We should post it on the Linaro wiki, probably.
More information about the linaro-toolchain