HP3000-L Archives

September 1999, Week 4

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
"BIXBY,MARK (HP-Cupertino,ex1)" <[log in to unmask]>
Reply To:
BIXBY,MARK (HP-Cupertino,ex1)
Date:
Wed, 22 Sep 1999 18:26:14 -0600
Content-Type:
text/plain
Parts/Attachments:
text/plain (36 lines)
> -----Original Message-----
> From: Troy Dodsworth [mailto:[log in to unmask]]
> Sent: Wednesday, September 22, 1999 2:42 PM
> To: [log in to unmask]
> Subject: linking with dcexl.hpdce.sys
>
>
> I am trying to link dcexl.hpdce.sys in order to make use of
> some of its
> functionality like gethostname(), but the program I am
> linking also contains
> a couple of fopens which the dcexl library has its own
> versions of.  When I
> link the executable I specify xl=dcexl.hpdce.sys, which then
> gets used ahead
> of any functions in xl.pub.sys which has the fopen I want to
> call rather
> than the dce version.  The problem is the executable will run
> with a posix
> shell but it will not function properly from the ci.  I have
> debugged the
> issue and is always returns a null file pointer when ever the fopen is
> called when the program is run from the ci rather than a
> posix shell.  Is
> there a solution to this some type of linkedit option?  or
> will executables
> linked with the dcexl library only function correctly from a
> posix shell?

FWIW, gethostname() exists in -lsocket (aka /usr/lib/libsocket.a and .sl).

I've never had to link anything with dcexl, and so I have no idea about your
fopen problem....

- Mark B.

ATOM RSS1 RSS2