forrie@morwyn.UUCP (Forrie Aldrich) (05/17/91)
I had posted a message a short time ago about having problems with
my compiler, etc.
Well, what I did is re-install my entire c library. It still complained.
I installed my Development set all over again, reinstalled the Crypt
stuff, and still no luck.
Then, a friend of mine gave me a copy of his fresh uncorrupted C library,
and still no luck.
What's happening is this: the loader isn't finding common symbols from
the c library such as '_doprnt' 'setvbuf' etc... And I CAN'T for the
life of me figure out WHY this is happening. I have never had any
problems like this before, and can't figure out where to look for the
problem(s).
Could someone out there help, or offer some advice? Thanks in advance!
Forrie
--
--------------------=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=--------------------
Forrest Aldrich, Jr.| (a reliable path here someday) |forrie@morwyn.UUCP
| <email paths> |
CREATIVE CONNECTIONS| uunet!virgin!unhtel!morwyn!forrie |Graphic Illustration
------------------\-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=/------------------
\___ PO Box 1541 - Dover, NH 03820 ___/ floyd@ims.alaska.edu (Floyd Davidson) (05/17/91)
In article <102@morwyn.UUCP> forrie@morwyn.UUCP (Forrie Aldrich) writes: >I had posted a message a short time ago about having problems with >my compiler, etc. [...] >What's happening is this: the loader isn't finding common symbols from >the c library such as '_doprnt' 'setvbuf' etc... If you are using the shared lib, they aren't there. If you are not using the shared lib, post the exact command line you are invoking the compiler with, and someone will surely see where the problem is. Floyd -- Floyd L. Davidson | Alascom, Inc. pays me, |UA Fairbanks Institute of Marine floyd@ims.alaska.edu| but not for opinions. |Science suffers me as a guest.
bruce@balilly (Bruce Lilly) (05/18/91)
In article <1991May17.033818.13599@ims.alaska.edu> floyd@ims.alaska.edu (Floyd Davidson) writes: >In article <102@morwyn.UUCP> forrie@morwyn.UUCP (Forrie Aldrich) writes: >>I had posted a message a short time ago about having problems with >>my compiler, etc. >[...] >>What's happening is this: the loader isn't finding common symbols from >>the c library such as '_doprnt' 'setvbuf' etc... > >If you are using the shared lib, they aren't there. To use the shared library with such a program, modify the makefile to use doprnt.o, setvbuf.o, etc. on the ld line, then add doprnt.o setvbuf.o: /lib/libc.a ar x $? $@ to the makefile, and you should be all set. -- Bruce Lilly blilly!balilly!bruce@sonyd1.Broadcast.Sony.COM
floyd@ims.alaska.edu (Floyd Davidson) (05/18/91)
In article <1991May17.224422.15038@blilly.UUCP> bruce@balilly (Bruce Lilly) writes: >In article <1991May17.033818.13599@ims.alaska.edu> floyd@ims.alaska.edu (Floyd Davidson) writes: >>In article <102@morwyn.UUCP> forrie@morwyn.UUCP (Forrie Aldrich) writes: >>>I had posted a message a short time ago about having problems with >>>my compiler, etc. >>[...] >>>What's happening is this: the loader isn't finding common symbols from >>>the c library such as '_doprnt' 'setvbuf' etc... >> >>If you are using the shared lib, they aren't there. > >To use the shared library with such a program, modify the makefile to use >doprnt.o, setvbuf.o, etc. on the ld line, then add > >doprnt.o setvbuf.o: /lib/libc.a > ar x $? $@ > >to the makefile, and you should be all set. > I put them into a local library and use the -l option. To me it seems a little cleaner... Floyd -- Floyd L. Davidson | Alascom, Inc. pays me, |UA Fairbanks Institute of Marine floyd@ims.alaska.edu| but not for opinions. |Science suffers me as a guest.