Kbase 33540: 'no SCO ELF identifying .note' when probuilding
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
10/05/1998 |
|
Solution ID: P3540
FACT(s) (Environment):
SCO OpenServer 5.0.5
Progress 9.1x
SYMPTOM(s):
Linking _progres with the DataServer Library using probuild
probuild fails with the messages:
warning: no SCO ELF identifying .note
fatal error: Symbol referencing errors
CAUSE:
The Executable and Linking Format (ELF) is a standard for executables and object files which replaced the COFF standard with the introduction of System V Release 4 (SVR4). Common Object File Format (COFF) is a standard for object files and executables in pre-System V, Release 4 (SVR4) based systems. The warnings during the probuild suggests a compiler incompatibility issue -- for example, the compiler that is being used is an older one that doesn't recognize the ELF format.
FIX:
1) Use displaypkg to check what software packages are installed on the system.
2) Ensure that the correct C packages are installed. According to the Progress Client Deployment Guide (where probuild is documented), the required software components include C run-time libraries and communications libraries from the operating system vendor.
3) Ensure that the cc compiler is installed. By default it should be in /udk/usr/ccs/bin/cc. This is the compiler that probuild uses by default.
4) Ensure the correct environment variables are set. For example:
PROLOAD=$DLC/probuild; export PROLOAD
CC="/udk/usr/ccs/bin/cc"; export CC
LDOPT="-L /udk/usr/lib -L /udk/usr/ccs/lib"; export LDOPT
SOCKLIB="-lsocket -lnsl -lresolv"; export SOCKLIB
CFLAGS="-xt -Kframe"; export CFLAGS