OFF TOPIC: Problems with user compiling C program

MARK SAYER (MSAYER@cuscal.com.au)
Tue, 03 Feb 1998 13:33:00 +1100

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

--Boundary_(ID_bp+Sl7cPU34ECsryfg4NjQ)
Content-type: text/plain; CHARSET=US-ASCII

Greetings -

I think this might be a tad off-topic - but it is an administrative
issue for me I feel. I have a program which uses the sockets
library...and when I compile I get the following:

# cc ptytcp.c
Undefined first referenced
symbol in file
socket ptytcp.o
accept ptytcp.o
bind ptytcp.o
getservbyname ptytcp.o
listen ptytcp.o
ld: fatal: Symbol referencing errors. No output written to a.out

I also have a user on my system trying to compile another program using
libraries provided by IBM for their MQ Series product...when they
compile they get the following:

# cc amqsput0.c
Undefined first referenced
symbol in file
MQDISC amqsput0.o
MQOPEN amqsput0.o
MQCONN amqsput0.o
MQPUT amqsput0.o
MQCLOSE amqsput0.o
ld: fatal: Symbol referencing errors. No output written to a.out

When I looked at the man docs for the sockets library calls - it said
something about having to dynamically link the binaries...but didn't go
into a lot of detail...Is there pissobly a problem with ld not knowing
where these library files are living or am I completely off the track
(Wouldn't be the first time :-)

Running Solaris 2.5.1

Compiler versions:

cc: SC4.0 18 Oct 1995 C 4.0
acomp: SC4.0 18 Oct 1995 C 4.0
ld: Software Generation Utilities (SGU) SunOS/ELF (LK-2.0 (S/I) -
versioning)

Any ideas????

Mark.

--Boundary_(ID_bp+Sl7cPU34ECsryfg4NjQ)
Content-type: text/html
Content-transfer-encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">

Greetings -

I think this might be a tad off-topic - but it is an = administrative issue for me I feel. I have a program which uses the = sockets library...and when I compile I get the following:


# cc ptytcp.c
Undefined         =             =   first referenced
 symbol        &nb= sp;           &nb= sp;        in file
socket         &nb= sp;           &nb= sp;        ptytcp.o
accept         &nb= sp;           &nb= sp;        ptytcp.o
bind          = ;            = ;          ptytcp.o =
getservbyname        &n= bsp;           &n= bsp;  ptytcp.o
listen         &nb= sp;           &nb= sp;        ptytcp.o
ld: fatal: Symbol referencing errors. No output = written to a.out

I also have a user on my system trying to compile = another program using libraries provided by IBM for their MQ Series = product...when they compile they get the following:


# cc amqsput0.c
Undefined         =             =   first referenced
 symbol        &nb= sp;           &nb= sp;        in file
MQDISC         &nb= sp;           &nb= sp;        amqsput0.o
MQOPEN         &nb= sp;           &nb= sp;        amqsput0.o
MQCONN         &nb= sp;           &nb= sp;        amqsput0.o
MQPUT         &nbs= p;           &nbs= p;         amqsput0.o
MQCLOSE         &n= bsp;           &n= bsp;       amqsput0.o
ld: fatal: Symbol referencing errors. No output = written to a.out

When I looked at the man docs for the sockets = library calls - it said something about having to dynamically link the = binaries...but didn't go into a lot of detail...Is there pissobly a = problem with ld not knowing where these library files are living or am = I completely off the track (Wouldn't be the first time :-)


Running Solaris 2.5.1

Compiler versions:

cc: SC4.0 18 Oct 1995 C 4.0
acomp: SC4.0 18 Oct 1995 C 4.0
ld: Software Generation Utilities (SGU) SunOS/ELF = (LK-2.0 (S/I) - versioning)

Any ideas????

Mark.

--Boundary_(ID_bp+Sl7cPU34ECsryfg4NjQ)--