[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: multiarch/bi-arch status (ETA) question

Adam Stiles <adam@priceengines.co.uk> writes:

> On Tuesday 05 July 2005 15:44, Goswin von Brederlow wrote:
>> All current linux distributions are pure64. They only differ slightly
>> in the amount of 32bit libs preinstalled (what debian has as
>> ia32-libs). Multiarch is something that goes way beyond what other
>> amd64 distributions have.
>> Multiarch standardizes and greatly simplifies installing random 32bit
>> packages on amd64 by making the packaging system aware of the fact. It
>> does not change the ability to run 32bit apps on amd64 at all, you
> Most current "64 bit" Linux distributions are not pure 64-bit but
> contain both 32 and 64 bit libraries.  In other words, they are
> multi-arch.

No. They have ia32-libs preinstalled.

Multi-arch means the packaging system knows about the various archs
the system can run. Afaik no linux distribution can install the i386
packages on amd64. They all have special 32bit amd64 packages for
stuff that needs it.

> This does not change the fact that it is a bodge.
> I am running a pure 64 bit Debian system.  The kernel, libraries and
> userland are all compiled as 64-bit software, and that's the way it
> should be.  Legacy 32-bit software is *always* going to hold you
> back.  Whatever you want to get working, just re-compile it in
> 64-bit mode -- it's as simple as make clean, ./configure, make, su,
> make install.

You compiled your own kernel without 32bit syscall emulation? Then
neither lilo nor grub will work anymore nor will syslinux or debian-cd
and several other things.

gcc probably doesn't even compile out of the box without that
emulation layer.


Reply to: