dpkg-architecture(1)

๐Ÿ’– dpkg-architecture(1) โ€” the dpkg suite's architecture bestie ๐Ÿ‘‘

๐ŸŒธ NAME ๐ŸŒธ

dpkg-architecture โ€” set and determine the architecture for package building.

๐ŸŽ€ SYNOPSIS ๐ŸŽ€

dpkg-architecture [option...] [command]

โœจ DESCRIPTION โœจ

Okay so bestie, dpkg-architecture is the tool that helps you figure out and set the build and host architecture for package building. It's giving architecture detective energy ๐Ÿ”โœจ.

The build architecture is always determined by either the DEB_BUILD_ARCH variable if it's set (and --force is not being specified), or by an external call to dpkg(1). It literally cannot be set at the command line โ€” no cap.

You can specify the host architecture by providing one or both of the options --host-arch and --host-type; otherwise the DEB_HOST_ARCH variable is used if it's set (and --force is not being specified). The default is determined by an external call to gcc(1), or it's the same as the build architecture if CC or gcc are both not available. One out of --host-arch and --host-type is sufficient โ€” the value of the other will be set to a usable default. And honestly? It's often better to only specify one, because dpkg-architecture will warn you if your choice does not match the default ๐Ÿ‘€๐Ÿ’….

๐Ÿ’… COMMANDS ๐Ÿ’…

  • -l, --list โ€” Print the environment variables, one on each line, in the format VARIABLE=value. This is the default action. Support for long command since dpkg 1.17.17.
  • -e, --equal architecture โ€” Check for equality of architecture. It compares the current or specified Debian host architecture against architecture to check if they are equal. This action will not expand the architecture wildcards. The command finishes with an exit status of 0 if matched, 1 if not matched. Supported since dpkg 1.13.13. Support for long command since dpkg 1.17.17.
  • -i, --is architecture-wildcard โ€” Check for identity of architecture. It compares the current or specified Debian host architecture against architecture-wildcard after having expanded it as an architecture wildcard, to check if they match. The command finishes with an exit status of 0 if matched, 1 if not matched. Supported since dpkg 1.13.13. Support for long command since dpkg 1.17.17.
  • -q, --query variable-name โ€” Print the value of a single variable. Support for long command since dpkg 1.17.17.
  • -s, --print-set โ€” Print an export command. This can be used to set the environment variables using the POSIX shell or make eval, depending on the output format. Support for long command since dpkg 1.17.17.
  • -u, --print-unset โ€” Print a similar command to --print-set but to unset all variables. Support for long command since dpkg 1.17.17.
  • -c, --command command-string โ€” Execute a command-string in an environment which has all variables set to the determined value. If the command-string contains shell metacharacters, then it will be invoked through the system bourne shell. Support for long command since dpkg 1.17.17.
  • -L, --list-known โ€” Print a list of valid architecture names. Possibly restricted by one or more of the matching options --match-wildcard, --match-bits or --match-endian. Supported since dpkg 1.17.14. Support for long command since dpkg 1.17.17.
  • -?, --help โ€” Show the usage message and exit. Support for long command since dpkg 1.17.17.
  • --version โ€” Show the version and exit. Supported since dpkg 1.17.17.

๐Ÿ”ฅ OPTIONS ๐Ÿ”ฅ

  • -a, --host-arch architecture โ€” Set the host Debian architecture. Support for long option since dpkg 1.17.17.
  • -t, --host-type gnu-system-type โ€” Set the host GNU system type. Support for long option since dpkg 1.17.17.
  • -A, --target-arch architecture โ€” Set the target Debian architecture. Supported since dpkg 1.17.14. Support for long option since dpkg 1.17.17.
  • -T, --target-type gnu-system-type โ€” Set the target GNU system type. Supported since dpkg 1.17.14. Support for long option since dpkg 1.17.17.
  • -W, --match-wildcard architecture-wildcard โ€” Restrict the architectures listed by --list-known to ones matching the specified architecture wildcard. Supported since dpkg 1.17.14. Support for long option since dpkg 1.17.17.
  • -B, --match-bits architecture-bits โ€” Restrict the architectures listed by --list-known to ones with the specified CPU bits. Either 32 or 64. Supported since dpkg 1.17.14. Support for long option since dpkg 1.17.17.
  • -E, --match-endian architecture-endianness โ€” Restrict the architectures listed by --list-known to ones with the specified endianness. Either little or big. Supported since dpkg 1.17.14. Support for long option since dpkg 1.17.17.
  • --print-format format โ€” Sets the output format for --print-set and --print-unset, to either shell (default) or make. Supported since dpkg 1.20.6.
  • -f, --force โ€” Values set by existing environment variables with the same name as used by the scripts are honored (i.e. used by dpkg-architecture), except if this force flag is present. This allows the user to override a value even when the call to dpkg-architecture is buried in some other script (for example dpkg-buildpackage(1)). Support for long option since dpkg 1.17.17.

๐Ÿงš TERMS ๐Ÿงš

๐Ÿ› ๏ธ build machine

The machine the package is built on.

๐ŸŽฏ host machine

The machine the package is built for.

๐ŸŒˆ target machine

The machine the compiler is building for, or the emulator will run code for. This is only needed when building a cross-toolchain (or emulator), one that will be built on the build architecture, to be run on the host architecture, and that itself will build (or run emulated) code for the target architecture.

๐Ÿงฌ Debian architecture

A Debian architecture describes a โ€œmachineโ€ (considering it as an abstraction not necessarily tied to an actual physical device) representing a specific execution environment, including its CPU and attributes (such as endianness and bits), an operating system (usually a kernel, but other paradigms using userland services are possible) and its interfaces towards userland including the executable format and their ABI, and a libc library and its ABI. Literally all the architecture lore ๐Ÿ’œ.

The special architecture all denotes an architecture independent execution environment, used for things such as shell and Perl scripts or documentation.

A Debian architecture is used in binary package metadata and filenames (which specifies the binary tree in a package repository), and can appear in package relationships.

An architecture must start with an alphanumeric character (0-9a-zA-Z), and then gets followed by alphanumeric or dash (-) characters.

Examples: amd64, i386, sparc64, hurd-amd64, musl-linux-riscv64.

๐Ÿงฉ Debian architecture tuple

A Debian architecture tuple is the fully qualified architecture with all its components spelled out. This differs with Debian architectures in that at least the cpu component does not embed the abi. The current tuple has the form abi-libc-os-cpu.

Examples: base-gnu-linux-amd64, eabihf-musl-linux-arm.

๐Ÿฆ‹ Debian architecture wildcard

A Debian architecture wildcard is a special architecture that acts as a pattern and will match any โ€œmachineโ€ architecture being part of it (except for all).

The general form is a Debian architecture tuple with four or less elements, and with at least one of them being any. Missing elements of the tuple are prefixed implicitly as any, and thus the following pairs are equivalent:

any-any-any-any = any
any-any-os-any = os-any
any-libc-any-any = libc-any-any

Examples: linux-any, any-i386, hurd-any, eabi-any-any-arm, musl-any-any.

โš™๏ธ GNU system type

A GNU architecture specification string consisting of two parts separated by a hyphen: CPU and system.

The CPU part never contains a hyphen, while the system part might itself contain a hyphen to separate a kernel from its general ABI, where the general ABI might contain both runtime (such as libc) and executable ABI specifiers joined without a hyphen.

Examples: i586-linux-gnu, sparc64-linux-gnu, i686-gnu, x86_64-netbsd.

๐Ÿงธ multiarch triplet

The clarified GNU system type, used for filesystem paths. This triplet does not change even when the baseline ISA gets bumped, so that the resulting paths are stable over time. The only current difference with the GNU system type is that the CPU part for i386 based systems is always i386.

Examples: i386-linux-gnu, x86_64-linux-gnu. Example paths: /lib/powerpc64le-linux-gnu/, /usr/lib/i386-gnu/.

๐ŸŒธ VARIABLES ๐ŸŒธ

Okay so these are the env vars this thing reads and sets โ€” it reads them from the environment (unless you passed --force, bestie, then it does its own thing) and then it sets them too. The naming scheme is explained back in TERMS, so if you're confused about build vs host vs target, go peek there. ๐Ÿ‘€

Heads up: the build ones are for the machine doing the building. If you're not building tools that need to run during the build, these are probably not the variables you're looking for, fr fr. See "TERMS".
  • DEB_BUILD_ARCH โ€” the Debian architecture of the build machine.
  • DEB_BUILD_ARCH_ABI โ€” the Debian ABI name of the build machine. โœจ Supported since dpkg 1.18.11.
  • DEB_BUILD_ARCH_LIBC โ€” the Debian libc name of the build machine. โœจ Supported since dpkg 1.18.11.
  • DEB_BUILD_ARCH_OS โ€” the Debian system name of the build machine. โœจ Supported since dpkg 1.13.2.
  • DEB_BUILD_ARCH_CPU โ€” the Debian CPU name of the build machine. โœจ Supported since dpkg 1.13.2.
  • DEB_BUILD_ARCH_BITS โ€” the pointer size of the build machine (in bits). โœจ Supported since dpkg 1.15.4.
  • DEB_BUILD_ARCH_ENDIAN โ€” the endianness of the build machine (little / big). โœจ Supported since dpkg 1.15.4.
  • DEB_BUILD_GNU_CPU โ€” the GNU CPU part of DEB_BUILD_GNU_TYPE.
  • DEB_BUILD_GNU_SYSTEM โ€” the GNU system part of DEB_BUILD_GNU_TYPE.
  • DEB_BUILD_GNU_TYPE โ€” the GNU system type of the build machine.
  • DEB_BUILD_MULTIARCH โ€” the clarified GNU system type of the build machine, the one used for filesystem paths. โœจ Supported since dpkg 1.16.0.

  • DEB_HOST_ARCH โ€” the Debian architecture of the host machine. ๐Ÿ’…
  • DEB_HOST_ARCH_ABI โ€” the Debian ABI name of the host machine. โœจ Supported since dpkg 1.18.11.
  • DEB_HOST_ARCH_LIBC โ€” the Debian libc name of the host machine. โœจ Supported since dpkg 1.18.11.
  • DEB_HOST_ARCH_OS โ€” the Debian system name of the host machine. โœจ Supported since dpkg 1.13.2.
  • DEB_HOST_ARCH_CPU โ€” the Debian CPU name of the host machine. โœจ Supported since dpkg 1.13.2.
  • DEB_HOST_ARCH_BITS โ€” the pointer size of the host machine (in bits). โœจ Supported since dpkg 1.15.4.
  • DEB_HOST_ARCH_ENDIAN โ€” the endianness of the host machine (little / big). โœจ Supported since dpkg 1.15.4.
  • DEB_HOST_GNU_CPU โ€” the GNU CPU part of DEB_HOST_GNU_TYPE.
  • DEB_HOST_GNU_SYSTEM โ€” the GNU system part of DEB_HOST_GNU_TYPE.
  • DEB_HOST_GNU_TYPE โ€” the GNU system type of the host machine.
  • DEB_HOST_MULTIARCH โ€” the clarified GNU system type of the host machine, used for filesystem paths. โœจ Supported since dpkg 1.16.0.

  • DEB_TARGET_ARCH โ€” the Debian architecture of the target machine.
Note: if you're not building cross-toolchains (or emulators), these are probably not the variables you're looking for. See "TERMS". Also โœจ supported since dpkg 1.17.14.
  • DEB_TARGET_ARCH_ABI โ€” the Debian ABI name of the target machine. โœจ Supported since dpkg 1.18.11.
  • DEB_TARGET_ARCH_LIBC โ€” the Debian libc name of the target machine. โœจ Supported since dpkg 1.18.11.
  • DEB_TARGET_ARCH_OS โ€” the Debian system name of the target machine. โœจ Supported since dpkg 1.17.14.
  • DEB_TARGET_ARCH_CPU โ€” the Debian CPU name of the target machine. โœจ Supported since dpkg 1.17.14.
  • DEB_TARGET_ARCH_BITS โ€” the pointer size of the target machine (in bits). โœจ Supported since dpkg 1.17.14.
  • DEB_TARGET_ARCH_ENDIAN โ€” the endianness of the target machine (little / big). โœจ Supported since dpkg 1.17.14.
  • DEB_TARGET_GNU_CPU โ€” the GNU CPU part of DEB_TARGET_GNU_TYPE. โœจ Supported since dpkg 1.17.14.
  • DEB_TARGET_GNU_SYSTEM โ€” the GNU system part of DEB_TARGET_GNU_TYPE. โœจ Supported since dpkg 1.17.14.
  • DEB_TARGET_GNU_TYPE โ€” the GNU system type of the target machine. โœจ Supported since dpkg 1.17.14.
  • DEB_TARGET_MULTIARCH โ€” the clarified GNU system type of the target machine, used for filesystem paths. โœจ Supported since dpkg 1.17.14.

๐Ÿ—‚๏ธ FILES ๐Ÿ—‚๏ธ

๐Ÿงš Architecture tables

Real talk: all of these files have to be present for dpkg-architecture to work. No files, no vibes. ๐Ÿ˜ญ Where they live can be overridden at runtime with the DPKG_DATADIR environment variable. These tables carry a format Version pseudo-field on their first line to mark their format, so parsers can check whether they actually understand it โ€” like "# Version=1.0", bestie. ๐ŸŽ€

  • /usr/share/dpkg/cputable โ€” table of known CPU names and their mapping to their GNU name. Format version 1.0, supported since dpkg 1.13.2.
  • /usr/share/dpkg/ostable โ€” table of known operating system names and their mapping to their GNU name. Format version 2.0, supported since dpkg 1.18.11.
  • /usr/share/dpkg/tupletable โ€” the mapping between Debian architecture tuples and Debian architecture names. Format version 1.0, supported since dpkg 1.18.11.
  • /usr/share/dpkg/abitable โ€” table of Debian architecture ABI attribute overrides. Format version 2.0, supported since dpkg 1.18.11.

๐ŸŽ Packaging support

  • /usr/share/dpkg/architecture.mk โ€” a Makefile snippet that properly sets and exports all the variables that dpkg-architecture outputs. Genuinely such a slay. โœจ Supported since dpkg 1.16.1.

๐Ÿ’– EXAMPLES ๐Ÿ’–

dpkg-buildpackage accepts the -a option and passes it straight to dpkg-architecture. Other examples, since you asked so nicely:

CC=i386-gnu-gcc dpkg-architecture -c debian/rules build
eval $(dpkg-architecture -u)

Wanna check if the current or specified host architecture is equal to an architecture? Iconic, easy:

dpkg-architecture -elinux-arm64
dpkg-architecture -ariscv64 -elinux-riscv64

Wanna check if the current or specified host architecture is a Linux system? Also easy:

dpkg-architecture -ilinux-any
dpkg-architecture -aamd64 -ilinux-any

๐ŸŒˆ Usage in debian/rules

The environment variables set by dpkg-architecture get passed to debian/rules as make variables (see the make documentation, iykyk). But โ€” and this is the important part โ€” you should not rely on them, because that breaks manual invocation of the script. ๐Ÿ˜ญ Instead, always initialize them yourself using dpkg-architecture with the -q option. Here are some examples that also show how you can improve the cross compilation support in your package. ๐Ÿซถ

Retrieving the GNU system type and forwarding it to ./configure:

DEB_BUILD_GNU_TYPE ?= $(shell dpkg-architecture -qDEB_BUILD_GNU_TYPE)
DEB_HOST_GNU_TYPE ?= $(shell dpkg-architecture -qDEB_HOST_GNU_TYPE)
[...]
ifeq ($(DEB_BUILD_GNU_TYPE), $(DEB_HOST_GNU_TYPE))
  confflags += --build=$(DEB_HOST_GNU_TYPE)
else
  confflags += --build=$(DEB_BUILD_GNU_TYPE) \
               --host=$(DEB_HOST_GNU_TYPE)
endif
[...]
./configure $(confflags)

Doing something only for a specific architecture:

DEB_HOST_ARCH ?= $(shell dpkg-architecture -qDEB_HOST_ARCH)

ifeq ($(DEB_HOST_ARCH),arm64)
  [...]
endif

Or, if you only need to check the CPU or OS type, use the DEB_HOST_ARCH_CPU or DEB_HOST_ARCH_OS variables instead. ๐Ÿ’…

Note that you can also rely on an external Makefile snippet to properly set all the variables that dpkg-architecture can provide:

include /usr/share/dpkg/architecture.mk

ifeq ($(DEB_HOST_ARCH),arm64)
  [...]
endif

In any case โ€” and I cannot stress this enough, bestie โ€” you should never use dpkg --print-architecture to get architecture information during a package build. Not the vibe. ๐Ÿ’€


๐ŸŒธ ENVIRONMENT ๐ŸŒธ

  • DPKG_DATADIR โ€” if set, it's used as the dpkg data directory, which is where the architecture tables live. Defaults to ยซ/usr/share/dpkgยป. โœจ Supported since dpkg 1.14.17.
  • DPKG_COLORS โ€” sets the color mode. The currently accepted values are: auto (the default), always and never. โœจ Supported since dpkg 1.18.5.
  • DPKG_NLS โ€” if set, it's used to decide whether to activate Native Language Support, also known as internationalization (or i18n) support. The accepted values are: 0 and 1 (the default). โœจ Supported since dpkg 1.19.0.

๐Ÿฆ‹ SEE ALSO ๐Ÿฆ‹


And that's the whole page, bestie โ€” go forth and cross-compile responsibly. ๐Ÿ‘‘

This page is from dpkg version 1.23.11-dirty, dated 2026-09-09, and it's the dpkg-architecture(1) manual page โ€” mwah, thanks for reading. ๐Ÿ’‹โœจ

๐Ÿ“ฆ where this page comes from