On Feb 28, 2012, at 8:29 AM, Jeremy Huntwork wrote:
> On 2/28/12 10:42 AM, Andrew Benton wrote:
>> Multilib is only of use if you want to run legacy binaries such as
>> windows programs with wine.
>
> Building Xen from source also required a 32bit libc, presumably for
> supporting 32-bit hosts, although I didn't dig very far to determine why
> specifically.
To support 32-bit HVM guests, Xen uses a 32-bit toolchain (including glibc-32
and dev86) to build something they call hvmloader which emulates BIOS at boot.
This has not been ported to 64-bit--and it's very much not in the critical path.
"32-bit HVM guests"--read: Windows non-64-bit platforms.
* * *
As for the "64-bit" works in practice...BIND is an example of a downstream app
that seems to want to look in /lib64. Whether it's looking for ld64.so.1,
ld-linux-x86-64.so.2, or something else even, I can't say. I do know that it
doesn't work when the root symlink (/lib64 -> /lib) isn't there. But I don't
know what other symlink dependencies it has, if any. I suppose there's also a
possibility that BIND could be build differently from the BLFS book, but I'm
not sure what's being gained by not having the 64-bit symlinks.
Q
--
http://linuxfromscratch.org/mailman/listinfo/lfs-dev
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page
