Datasheet

“main” (Installation and Administration) — 2004/6/25 — 13:29 — page 201 — #227

32-Bit and 64-Bit Applications in a 64-Bit System Environment

2. Instruct the linker to process 64-bit objects:

LD="ld -m elf64ppc"

3. Set the assembler to generate 64-bit objects:

AS="gcc -c -m64"

4. Determine that the libraries for libtool and so on come from /usr/

lib64/:

LDFLAGS="-L/usr/lib64"

5. Determine that the libraries are stored in the lib64 subdirectory:

--libdir=/usr/lib64

6. Determine that the 64-bit X libraries are used:

--x-libraries=/usr/X11R6/lib64/

Not all of these variables are needed for every program. Adapt them to the

respective program.

An example configure call could appear as follows:

CC="gcc -m64" \

LDFLAGS="-L/usr/lib64;" \

.configure \

--prefix=/usr \

--libdir=/usr/lib64

make

make install

7.4 Kernel Speciﬁcations

The 64-bit kernels for ppc64, s390x, amd64, and em64t offer both a 64-bit

and a 32-bit kernel ABI (application binary interface). The latter is identical

with the ABI for the corresponding 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 a

number of APIs used by system programs. This depends on the platform.

201SUSE LINUX Enterprise Server