z/TPF Program Management - IBM

|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
export TPF_X_LIBS=/ztpf/tpfcross/build/tpf-06r1-13/H-s390x-linux-gnu/lib/gcc/s390x-ibm-tpf/4.1.2
export TPF_INFO=/ztpf/tpfcross/build/tpf-06r1-13/share/info
export INFOPATH=$TPF_INFO:$INFOPATH
For example, enter the following commands if you are using the GCC 4.6.3
ELF-compatible compiler:
export PATH=/ztpf/tpfcross/build/tpf-11r1-8/H-s390x-linux-gnu/bin:${PATH}
export TPF_X_GCC=/ztpf/tpfcross/build/tpf-11r1-8/include/c++/4.6.3
export TPF_X_LIBS=/ztpf/tpfcross/build/tpf-11r1-8/H-s390x-linux-gnu/lib/gcc/s390x-ibm-tpf/4.6.3
export TPF_INFO=/ztpf/tpfcross/build/tpf-11r1-8/share/info
export INFOPATH=$TPF_INFO:$INFOPATH
b. Optional: To offer a choice of GCC compiler versions to application
programmers, customize the tpftools/include_ztpf/
maketpf_rules_cfg_REDHAT file to set four environment variables to define
the installation location for each of the supported levels of the compiler:
1) Uncomment the export directives by removing the leading number sign
(#).
2) Change the TPF_* variables to identify the directories where the versions
are installed. For example, change
#export TPF_X_LIBS:=
to
export TPF_X_LIBS:=/opt/gcc/current/libs
3) Prefix the PATH setting with the directory where the version is installed.
For example:
export PATH:=/opt/gcc/current/bin:$(PATH)
A set of environment variables for GCC V4.1 and GCC V4.6 might look
like this example:
ifeq ($(TPFGCC_VERSION),41)
export TPF_X_GCC:=/opt/gcc/current/tpf_x_gcc
export TPF_X_LIBS:=/opt/gcc/current/libs
export TPF_INFO:=/opt/gcc/current/info
export PATH:=/opt/gcc/current/bin:$(PATH)
endif
ifeq ($(TPFGCC_VERSION),46)
export TPF_X_GCC:=/cteam/jones/tpf-gcc-4.6.3-8/s390x-ibm-tpf/include/c++/4.6.3
export TPF_X_LIBS:=/cteam/jones/tpf-gcc-4.6.3-8/lib/gcc/s390x-ibm-tpf/4.6.3
export TPF_INFO:=/cteam/jones/tpf-gcc-4.6.3-8/share/info
export PATH:=/cteam/jones/tpf-gcc-4.6.3-8/bin:$(PATH)
endif
c. Verify that the compiler was built successfully. Start a new Linux session and
enter the following command:
tpf-gcc -v
If the compiler was unpacked successfully and the directories that are
shown in the examples were used, the following information is displayed if
you are using the GCC 4.1.2 compiler:
Using built-in specs.
Target: s390x-ibm-tpf
Configured with: /ztpf/tpfcross/build/tpf-06r1-13/sources/tools/cross/configure --host=s390x-linux-gnu --target=s390x-ibm-tpf
--build=s390x-linux-gnu --prefix=/ztpf/tpfcross/build/tpf-06r1-13 --exec-prefix=/ztpf/tpfcross/build/tpf-06r1-13/H-s390x-linux-gnu
--enable-languages=c,c++ --program-prefix=tpf- --without-newlib --with-sysroot
Thread model: tpf
TARGET_SYSTEM_ROOT:
/ztpf/tpfcross/build/tpf-cross-tools-4.1-tpf-06r1-13/H-s390x-linux-gnu/bin/../s390x-ibm-tpf/sys-root
gcc version 4.1.2 20060724 (GNUPro 06r1-13) for z/TPF PUT05
50 z/TPF Program Management
If you are using the GCC 4.6 compiler, the following example shows the
output from the tpf-gcc -v command: