General Issues

Known programming issues and workarounds, if any, for SAP Open Client products.

Programming Issues
CR#	Description
	Upgrading to a new version Workaround: For statically and dynamically linked SAP Open Client applications (dblib, ctlib, and esql)(dblib and ctlib), SAP recommends the following: Rebuild all statically linked SAP Open Client applications (dblib, ctlib, and esql) (dblib and ctlib) using the new version of software. Recompile and relink the applications using the new header files and libraries. For dynamically linked SAP Open Client applications, recompile and relink with the SDK libraries that now include “syb” in the library names. Note: If you have made any changes to the application files, you must recompile. Ensure that the runtime libraries are for the same major release as the version used to build the application.
	Compiling sample programs Workaround: When linking an application with the static Open Client libraries, add this parameter to your link line: -lnsl -lsocket
682932	Generic 64-bit x86 Workaround: On Solaris x86-64 (64-bit), the libraries are built using generic 64-bit x86 instructions.
575063	Linking static libraries Workaround: When statically linking the Open Client and Open Server libraries, you must link your application to librt, the Realtime Extensions library. Static linking requires that you add `-lrt` to your makefile.
	Programming with thread-safe libraries Workaround: To use the Sybase thread-safe libraries, you must compile and link your code with thread safety options. You must use the `-mt -D_REENTRANT` option on the cc command.