Path: utzoo!attcan!uunet!snorkelwacker!tut.cis.ohio-state.edu!rutgers!deimos.cis.ksu.edu!maverick.ksu.ksu.edu!eecea!khc From: khc@eecea.eece.ksu.edu (Ken Carpenter) Newsgroups: comp.sys.mips Subject: Re: BSD43 libraries Message-ID: <1990Jun1.132149.29655@maverick.ksu.ksu.edu> Date: 1 Jun 90 13:21:49 GMT References: <1990May17.201954.13301@maverick.ksu.ksu.edu> Sender: news@maverick.ksu.ksu.edu (The News Guru) Organization: Kansas State University Lines: 34 khc@eecea.eece.ksu.edu (Ken Carpenter) writes: >In trying to compile a large piece of code that was originally >written for bsd4.3, I finally got the compiling done without error >by using -I/usr/include/bsd43 on the cc command line. >Now when linking I have -lbsd specified, but still get an error >message about three unfound symbols: setsigmask, sigvec, and ftime. >Does anyone know what library these are found in? Thanks for the replies to the above. The two suggested solutions were to use the switch "-systype bsd43" with the sysV cc, and to use the /bsd43/bin/cc as the compiler. Here is what happened in my case: 1. makefiles contained CC = /bin/cc originally - thus the fact that /bsd43/bin was first in my path did not matter. 2. When the BSD code was made with CC = /bin/cc and "-systype bsd43" was added to CFLAGS the make was without error. However, the executable dumped core on invocation. 3. When the BSD code was made with CC = /bsd43/bin/cc and no addition to CFLAGS, the make was without error, and the code ran almost the same as on a Sun 4/60. (The difference may be a machine dependent bug, not something in the compiling or linking.) Conclusion: porting BSD4.3 code, use /bsd43/bin/cc explicitly when compiling and linking, and make no other changes. Kenneth H. Carpenter | 913-532-5600 | khc@eecea.eece.ksu.edu Electrical & Computer Engineering Department | KHC@ksuvm.bitnet Kansas State University - Durland Hall | rutgers!ksuvax1!eecea!khc Manhattan, KS 66506 | {pyramid,ucsd}!ncr-sd!ncrwic!ksuvax1!eecea!khc