Re: Upcoming Debian multiarch support (amd64, sparc64, s390x, mips64) [affects sarge slightly]
On Tue, Jan 13, 2004 at 03:20:00PM +0100, Claus Färber wrote:
> Goswin von Brederlow <firstname.lastname@example.org> schrieb/wrote:
> > And the biggest job is changing every library package to build the
> > amd64 flavour and put its libraries into /lib64/. But that can be done
> > step by step as needed to compile binaries for amd64
> The method of putting libraries into /lib/ and /lib64/ does not work if
> you want to have i386 and ppc, for example, on the same system. While
> this is not possible at the moment, it will be once someone writes a
> good CPU emulator... (or with CLI).
It has been possible, at least in the past, on Alpha. Even today, when
you compile an Alpha kernel, you have the ability to enable i386 binary
support. em86 has not been updated in years, though, so I don't know if
it is actually any good any more. I suspect not. Even not so drastic,
a Linux kernel on Alpha can still run OSF/1 and Tru64 binaries.
However, even on i386 this situation could arise. For instance, Debian
GNU/KFreeBSD could support both FreeBSD and Linux binaries on a single
box. (The FreeBSD kernel already has that ability.)
In other words, you hypothesis is a lot closer than you may think :-)
> IMO multiarch support could be designed in a way that allows such
> future cases to work, too:
> . .so files are put into /lib-<arch> or /usr/lib-<arch>.
> . /lib/ and /usr/lib are populated with symbolic links to the libraries
> for the native architecture by ldconfig;
> on amd64 /lib64/ and /usr/lib64/ are used instead and /lib/ and /usr/
> lib/ are used for links to leagacy 32 bit libs.
> . non-.so-library files (which usually provide the same interface for
> calling programs) are kept in /lib/ and /usr/lib/ as usual.
> Connollystraße 8, D-80809 München, Tel. +49 700 CFAERBER, Fax +49 89 35709492
> Mitterfeldstraße 20, D-83043 Bad Aibling - ICQ: 15468108 - www.faerber.muc.de
> OpenPGP: DSS 1024/639680F0 E7A8 AADB 6C8A 2450 67EA AF68 48A5 0E63 6396 80F0
> To UNSUBSCRIBE, email to email@example.com
> with a subject of "unsubscribe". Trouble? Contact firstname.lastname@example.org