Kbase 13938: Undefined symbols, PROBUILD PROGRESS client, for Dataservers
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
5/10/1998 |
|
Undefined symbols, PROBUILD PROGRESS client, for Dataservers
Undefined Symbols, PROBUILD PROGRESS client for Dataservers.
The following Undefined symbols result when running the
link script (default: ldpro) for PROGRESS local client
for Dataserver without choosing TCP/IP from the
Configurable Elements screen of PROBUILD.
(Sybase requires picking TCP/IP for its networking to work, even if
you're building a LOCAL client.)
The following or similar messages will appear when you
run the link script (default: ldpro).
Undefined first referenced
symbol in file
socket ./4gl/wvsys.o
accept ./4gl/wvsys.o
bind ./4gl/wvsys.o
listen ./4gl/wvsys.o
To correctly build a PROGRESS executable for a client
select the following within PROBUILD:
(This is an example for Sybase, but it applies to
all dataservers)
Product List: PROGRESS CLIENT
Link Script Executable Names:
these can be changed or the default names can be kept.
The default name for the PROGRESS executable should be
changed to avoid confusion with the supplied generic
_progres executable.
For SYBASE 10:
Configurable Elements: TCP-IP NETWORK PROTOCOL
Dataserver Library
SYBASE10 DATASERVER
For SYBASE4:
Configurable Elements: TCP-IP NETWORK PROTOCOL
SYBASE4 DATASERVER
If your license does not show TCP-IP NETWORK PROTOCOL as a
Configurable Element, make sure BUILDENV is run before
PROBUILDing the link script. Buildenv will set the SOCKLIB
environment variable. Then edit the the link script (default: ldpro)
to include the SOCKLIB environment variable.
$SYBLIB $SOCKLIB \ <-- Add this to the end of the link script
(default: ldpro)
$CC_OBJ
Progress Software Technical Support Note # 13938