Translation(s): English : Português Brasileiro : Français
Contents
Что такое Multiarch?
Multiarch позволяет вам устанавливать пакеты, предназначенные для различных архитектур на одну и ту же машину. Это полезно для различных задач, но наиболее общая задача - установка 64 и 32-битных программ на одной машине с автоматическим разрешением зависимостей. В общем, вы можете иметь библиотеки более чем одной архитектуры установленные вместе и приложения для той или иной архитектуры, установленные как альтернативы. Заметьте что при этом не обязательно версии приложений под различные архитектуры должны быть установлены вместе.
Концепция
Чтобы узнать текущую архитектуру, набираем dpkg --print-architecture. (Обратите внимание, что архитектура на самом деле относится к "ABI" (Application Binary Interface), а не набор инструкций (ISA). Так, например, armel и armhf различные архитектуры потому, что они имеют различные вызовы библиотек ABIs, хотя используют одинаковый набор инструкций.
Пакеты можно указывать как 'package:architecture', например libc:i386 и libc:amd64, обратите внимание что семантика в dpkg и apt немного отличается, поэтому вы можете получить различные результаты, но они всегда будут безопасны и не двусмысленны. Имя пакета 'package', всегда будет соответствовать текущей архитектуре apt.
Доступные архитектуры можно посмотреть dpkg --print-foreign-architectures.dpkg будет управлять пакетами для этих архитектур, а также архитектуры машины.
Заголовок 'Multi-Arch' в пакете соответствует всем multiarch-aware пакетам.
Existing packages work fine in a multiarch environment, just as before, but to gain the benefits of co-installation or cross-architecture dependencies, many packages need to be made 'multiarch-aware'.
- For an unchanged package you can choose which arch version of a package to install (e.g. 'amd64' or 'i386').
- If a package is marked 'Multi-Arch: foreign', then it can satisfy dependencies of a package of a different architecture (e.g 'make:amd64' will satisfy a dependency on make for any-architecture package).
- To enable more than one architecture version of a package to be installed at the same time (generally libraries and dev- packages) files need to be moved so they don't clash. These packages are marked 'Multi-Arch: same'.
Packages marked 'Multi-Arch : allowed also exist which can be treated as either :same or :foreign depending on how they are depended-on.
Packagers are currently working through the distro, starting with the most useful packages for making multi-arch aware. See the multiarch spec and implementation howto for details of how it all actually works, and how to update packages to take advantage of the functionality.
Availability
You need a multiarch-aware dpkg and apt.
In Debian dpkg this is present since 1.16.2. In Ubuntu this is present since natty (v1.15.8.10ubuntu1). Check by seeing if dpkg --print-foreign-architectures is understood.
Apt is multiarch-aware if it supports -o APT::Architectures. This is available from version 0.8.13 onwards. However there are many multiarch-related improvements and bug-fixes in later apt versions (some required by Debian dpkg 1.16.2 to properly enable multiarch), such as apt-get build-dep -a cross-dependency support, so the later the better in general up to at least 0.9.4.
Prior to apt 0.9 in Debian, dpkg can get stuck (but only if multiarch is enabled) during upgrades when it is not told which arch package it should be configuring by apt. (dpkg: error: --configure needs a valid package name but 'gcc-4.7-base' is not: ambiguous package name 'gcc-4.7-base' with more than one installed instance) dpkg --configure -a will unbung this.
Использование
Конфигурация архитектур
Чтобы добавить дополнитульную архитектуру (в Debian для dpkg 1.16.2 и выше):
dpkg --add-architecture <arch>
пример
dpkg --add-architecture armhf
Обратите внимание: ничего не изменится, пока не обновите список пакетов.
apt-get update
Для удаления архитектуры
dpkg --remove-architecture <arch>
dpkg архитектуры хранятся в /var/lib/dpkg/arch.
Setting up apt sources
Apt defaults to using the set of architectures reported by dpkg, and any unqualified architecture deb lines in /etc/apt/sources.list, which is usually what you wanted. This can be overridden using APT::Architecture=<arch> to set the default architecture or APT::Architectures="<arch> <arch>".
apt-sources can be architecture qualified with this syntax. This is very useful on Ubuntu's split archive. It is not normally necessary on Debian unless your normal archive does not mirror the extra architectures you are interested in.
deb [arch=amd64,i386] http://uk.archive.ubuntu.com/ubuntu/ quantal main universe deb [arch=armel,armhf] http://ports.ubuntu.com/ubuntu-ports quantal main universe
Arch-qualifying deb-src lines doesn't make any sense.
Note: There is a bug in apt versions >=0.9.7 and <0.9.7.2 which means that putting 'arch=armel,armhf' on one line didn't work - you needed two separate entries.
Don't forget to
apt-get update
after adding new architectures.
Установка/удаление пакетов
Для установки пакета из архитектуры не по-умолчанию, нужно ввести в командной строке:
apt-get install package:architecture
Зависимости пакета будут установлены автоматически, для корректной архитектуры пример:
apt-get install links:i386
dpkg -i package_version_architecture.deb dpkg -r package:architecture
Installing cross-dependencies
To install build-dependencies of a package before cross-building:
apt-get build-dep -a <arch> <package>
This only works when all the 'tools' packages depended-on are marked Multi-Arch: foreign, any depended-on libraries which are also needed on the BUILD machine, and -dev packages which are needed for both HOST and BUILD architectures are made co-installable ('Multi-Arch: same' with arch-qualified paths), and any exceptions to the default rules are marked package:any or package:native in the package source. This process is ongoing.
When it doesn't work you can often get the dependencies installed with a manual apt-get line: e.g instead of
apt-get build-dep -a armhf acl
, do
apt-get install autoconf automake debhelper gettext libtool libattr1-dev:armhf
Details of how this resolves are on MultiarchCross.
Installing Android SDK compat libraries
Some users using the Android SDK might encounter problems when trying to run build-tools or platform-tools on amd64 bit platform. As replacement for ia32-libs, users should be fine just installing the following libraries:
dpkg --add-architecture i386 aptitude update aptitude install libstdc++6:i386 libgcc1:i386 zlib1g:i386 libncurses5:i386