Datasheet

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

All header ﬁles must be written in an architecture-independent form. The

installed 32-bit and 64-bit libraries must have an API (application program-

ming interface) that matches the installed header ﬁles. The normal SUSE

environment is designed according to this principle. In the case of manu-

ally updated libraries, resolve these issues yourself.

7.3 Software Compilation on Biarch

Platforms

To develop binaries for the other architecture on a biarch architecture, the

respective libraries for the second architecture must additionally be in-

stalled. These packages are called rpmname-32bit if the second architec-

ture is a 32-bit architecture or rpmname-64bit if the second architecture is

a 64-bit architecture.

You also need the respective headers and libraries from the

rpmname-devel packages and the development libraries for the second

architecture from rpmname-devel-32bit or rpmname-devel-64bit.

For example, to compile a program that uses libaio on a system whose

second architecture is a 64-bit architecture, you need the following RPMs:

libaio 32-bit runtime package

libaio-devel Headers and libraries for the 32-bit development

libaio-64bit 64-bit runtime package

libaio-devel-64bit 64-bit development libraries

Most Open Source programs use an autoconf-based program conﬁgura-

tion. To use autoconf for conﬁguring a program for the second architec-

ture, overwrite the normal compiler and linker settings of autoconf by

running the conﬁgure script with additional environment variables.

The following example refers to a ppc system with ppc64 as the second ar-

chitecture:

1. Set autoconf to use the 64-bit compiler:

CC="gcc -m64"

200 7.3. Software Compilation on Biarch Platforms