Shlib brain damage?

[Bill Mayhew]

Hi compatriots,

Being mostly an engineer, rather than a software guru, I apologize
if this is a dumb question.

Recently, I grabbed the "phone" talk program from comp.sources and
compiled it.  No big deal, other than adding a flag variable so
that it didn't try to close a stream it hadn't open when the other
party wasn't logged it (it dumped core in that case, as posted).

What bothered me was that the stripped executable was still 72,454
bytes.  I figured this was a ripe target for the application of the
shared library.  Following the advice in the little "Unix PC
Interface Speicification" (or whatever it's called) paperback book,
I switched over to using tam calls from curses.  I also followd the
form of /usr/include/Makepre.h for setting up my make file.

When /bin/ld tried to link the shared library, a lot of stuff that
the paperback book said was supposed to be in tam was claimed to be
undefined.  I tried adding -lcurses, but as you guessed, that was a
disaster too.

Is it me, the phase of the moon, or is a lot of stuff just not in
the shared library?  Is there any way to use what is in shlib, and
also put the missing stuff in my executable?

Thanks,
Bill

Not sure what path to me works these days, try these:

....!spl1!neoucom!wtm
....!mandrill!neoucom!wtm
....!pitt!neoucom!wtm
....!allegra!neoucom!wtm
....!cbosgd!neoucom!wtm  (doubtful)
....!allegra!blair!impulse!neoucom!wtm (small chance)

forget domain, the map is way out of date.