Table of Contents
Advertisement
5 Determine that the libraries are stored in the lib subdirectory:
--libdir=/usr/lib
6 Determine that the 32-bit X libraries are used:
--x-libraries=/usr/X11R6/lib/
Not all of these variables are needed for every program. Adapt them to the respective
program.
An example configure call to compile a native 32-bit application on x86_64, ppc64,
or s390x could appear as follows:
CC="gcc -m32"
LDFLAGS="-L/usr/lib;"
.configure
--prefix=/usr
--libdir=/usr/lib
make
make install
19.4 Kernel Specifications
The 64-bit kernels for x86_64, ppc64, and s390x offer both a 64-bit and a 32-bit kernel
ABI (application binary interface). The latter is identical with the ABI for the corre-
sponding 32-bit kernel. This means that the 32-bit application can communicate with
the 64-bit kernel in the same way as with the 32-bit kernel.
The 32-bit emulation of system calls for a 64-bit kernel does not support all the APIs
used by system programs. This depends on the platform. For this reason, a small number
of applications, like lspci, must be compiled on non-ppc64 platforms as 64-bit pro-
grams to function properly. On IBM System z, not all ioctls are available in the 32-bit
kernel ABI.
A 64-bit kernel can only load 64-bit kernel modules that have been specially compiled
for this kernel. It is not possible to use 32-bit kernel modules.
\
\
\
\
32-Bit and 64-Bit Applications in a 64-Bit System Environment
383
Advertisement
Table of Contents
Troubleshooting
