home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.sys.next.sysadmin
- Path: sparky!uunet!charon.amdahl.com!pacbell.com!ames!sun-barr!cs.utexas.edu!wupost!csus.edu!news
- From: eps@futon.SFSU.EDU (Eric P. Scott)
- Subject: Re: Where is std C lib?
- Message-ID: <1992Nov14.030325.14705@csus.edu>
- Sender: news@csus.edu
- Reply-To: eps@cs.sfsu.edu
- Organization: San Francisco State University
- References: <9586@blue.cis.pitt.edu.UUCP>
- Date: Sat, 14 Nov 1992 03:03:25 GMT
- Lines: 27
-
- In article <9586@blue.cis.pitt.edu.UUCP> rcc@next1.math.pitt.edu
- (robert cyphers) writes:
- >Where does the standard C library live on the NeXT? I don't have
- >a /usr/lib/libc.a and yet my programs compile. Some configuration
- >scripts get confused when they can't find this file.
-
- /lib/libsys_s.a
-
- Some configuration scripts get *very* confused on NeXTs for a
- number of reasons. Reading #include files without preprocessing
- them first loses because the __STRICT_BSD__/__STRICT_ANSI__
- conditionals aren't respected. Things are worse in 3.0 with
- the "improved" (NOT!) reorganization. Looking for .o files
- rather than specific procedures loses, since some entry points
- are in different modules from most BSD systems (something that
- programs don't care about). Then there are the problems with
- traditional vs. ANSI preprocessing. Configure is a great idea,
- but there are quite a few truly dreadful Configure scripts out
- there. I'm much happier with the approach nn takes, with its
- matrix of architecture and OS dependencies.
-
- >Also, does the std c lib include the RPC library functions (librpc.a)
- >as I believe is the case on a SUN?
-
- Yes.
-
- -=EPS=-
-