libelf

The libelf APIs are used to create the ELF descriptor. The descriptor is then used by other APIs to read from, and write to, the ELF object file.

libelf is packaged as part of a dynamic link library (DLL). The XPLINK versions are packaged as part of CEE.SCEERUN2. The NOXPLINK version is packaged as part of CEE.SCEERUN.

For 64–bit applications, libelf is shipped in the CDAEQED DLL as part of CEE.SCEERUN2.
For 31–bit XPLINK applications, libelf is shipped in the CDAEED DLL as part of CEE.SCEERUN2.
For 31–bit NOXPLINK applications, libelf is shipped in the CDAEEDE DLL as part of CEE.SCEERUN.

When compiling an application that uses the libelf library, you must include libelf.h which is located in the /usr/lpp/cbclib/include/libelf directory.

Optionally, you can bind the module with an appropriate side deck:

For 64–bit applications:
- Bind with CEE.SCEELIB(CDAEQED) if you are using an IBM® MVS™ file system
- Bind with /usr/lpp/cbclib/lib/libelfdwarf64.x if you are using a hierarchical file system
For 31–bit applications on an MVS file system:
- Bind with CEE.SCEELIB(CDAEED) if you are using XPLINK version of DLL.
- Bind with CEE.SCEELIB(CDAEEDE) if you are using NOXPLINK version of DLL.
For 31–bit applications on a z/OS UNIX file system:
- Bind with /usr/lpp/cbclib/lib/libelfdwarf32.x if you are using XPLINK version of DLL.
- Bind with /usr/lpp/cbclib/lib/libelfdwarf32e.x if you are using NOXPLINK version of DLL.

Note: IBM has extended the libelf library to support C/C++ on the z/OS® operating system. These extensions enable the libelf library to be used in various environments without additional extensions. The generic interfaces provided by libelf are defined as part of the UNIX System V Release 4 ABI. For descriptions of the interfaces supported by libelf, refer to the following documents:

System V Application Binary Interface Standard
DWARF/ELF Extensions Library Reference