Reference
- About this guide
- I Advanced administration
- II System
- 8 32-bit and 64-bit applications in a 64-bit system environment
- 9 Introduction to the boot process
- 10 The
systemddaemon - 11
journalctl: query thesystemdjournal - 12 The boot loader GRUB 2
- 13 Basic networking
- 14 UEFI (Unified Extensible Firmware Interface)
- 15 Special system features
- 16 Dynamic kernel device management with
udev
- III Services
- IV Mobile computers
- A An example network
- B GNU licenses
8 32-bit and 64-bit applications in a 64-bit system environment #Edit source
openSUSE® Leap is available for 64-bit platforms. The developers have not ported all 32-bit applications to 64-bit systems. This chapter offers a brief overview of 32-bit support implementation on 64-bit openSUSE Leap platforms.
openSUSE Leap for the 64-bit platforms AMD64 and Intel 64 is designed so that existing 32-bit applications run in the 64-bit environment “out-of-the-box.” This support means that you can continue to use your preferred 32-bit applications without waiting for a corresponding 64-bit port to become available.
Note: No support for building 32-bit applications
openSUSE Leap does not support compilation of 32-bit applications. It only offers runtime support for 32-bit binaries.
8.1 Runtime support #Edit source
Important: Conflicts between application versions
If an application is available for both 32-bit and 64-bit environments, installing both versions may cause problems. In such cases, decide on one version to install to avoid potential runtime errors.
An exception to this rule is PAM (pluggable authentication modules). openSUSE Leap uses PAM in the authentication process as a layer that mediates between user and application. Always install both PAM versions on 64-bit operating systems that also run 32-bit applications.
For correct execution, every application requires a range of libraries. Because the names are identical for the 32-bit and 64-bit versions of these libraries, they must be differentiated from each other in another way.
To retain compatibility with 32-bit versions, 64-bit and
32-bit libraries are stored in the same location. The 32-bit
version of libc.so.6 is located under
/lib/libc.so.6 in both 32-bit and 64-bit
environments.
All 64-bit libraries and object files are located in directories called
lib64. The 64-bit object files normally
found under /lib and
/usr/lib are now found under
/lib64 and /usr/lib64. This means
that space is available for 32-bit libraries under /lib
and /usr/lib, so the file name for both versions can
remain unchanged.
If the data content of 32-bit subdirectories under /lib does not
depend on word size, they are not moved. This scheme conforms to LSB (Linux Standards Base)
and FHS (Filesystem Hierarchy Standard).
8.2 Kernel specifications #Edit source
The 64-bit kernels for AMD64/Intel 64 offer both a 64-bit and a 32-bit kernel ABI (application binary interface). The latter is identical to the ABI for the corresponding 32-bit kernel. This means that communication between both 32-bit and 64-bit applications with 64-bit kernels are identical.
The 32-bit system call emulation for 64-bit kernels does not support
all the APIs used by system programs. This depends on the platform. For this
reason, few applications, like lspci, must be
compiled.
A 64-bit kernel can only load 64-bit kernel modules. You must compile 64-bit modules specifically for 64-bit kernels. It is not possible to use 32-bit kernel modules with 64-bit kernels.
Tip: Kernel-loadable modules
Certain applications require separate kernel-loadable modules. If you intend to use a 32-bit application in a 64-bit system environment, contact the provider of the application and SUSE. Make sure that the 64-bit version of the kernel-loadable module and the 32-bit compiled version of the kernel API are available for this module.