Andrew Stubbs <a...@codesourcery.com> wrote:
> 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:
> /lib/${mulitarch}/ld.so.
>
> 4. Dynamic linker uses HWCAP to find the most appropriate libc.so.
I thought that's basically the flow of the "Loading/running an executable"
sections ... I've added sub-section headers to maybe make it a bit
clearer.
> We should post it on the Linaro wiki, probably.
It's now on:
https://wiki.linaro.org/WorkingGroups/ToolChain/MultiarchPaths
Mit freundlichen Gruessen / Best Regards
Ulrich Weigand
--
Dr. Ulrich Weigand | Phone: +49-7031/16-3727
STSM, GNU compiler and toolchain for Linux on System z and Cell/B.E.
IBM Deutschland Research & Development GmbH
Vorsitzender des Aufsichtsrats: Martin Jetter | Geschäftsführung: Dirk
Wittkopp
Sitz der Gesellschaft: Böblingen | Registergericht: Amtsgericht
Stuttgart, HRB 243294
_______________________________________________
linaro-toolchain mailing list
linaro-toolchain@lists.linaro.org
http://lists.linaro.org/mailman/listinfo/linaro-toolchain
