home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!sun-barr!olivea!spool.mu.edu!yale.edu!ira.uka.de!smurf.sub.org!easix!umunk!udo
- From: udo@umunk.GUN.de (Udo Munk)
- Newsgroups: comp.os.coherent
- Subject: Re: Data CMP modems, fcntl.h et.al.
- Message-ID: <920914921@umunk.GUN.de>
- Date: 14 Sep 92 00:10:34 GMT
- References: <79582@ut-emx.uucp>
- Organization: U. Munk's private BBS
- Lines: 33
- X-Newsreader: Tin 1.1 PL4
-
- vax@ccwf.cc.utexas.edu (Vax) writes:
- [...]
- : Will MWC make an official announcement (on the net) about fcntl.h? As I see
- : it, we have three alternatives:
- : o Move fcntl.h to the /usr/include/sys directory as per the dox.
-
- Really a poor idea! If you port software to your modified Coherent and
- give this to a unexperienced user, who hasn't moved his fcntl.h,
- she/he would say: s..., why does this ported program doesn't compile????
-
- : o Make a link from the sys directory into /usr/include, thus
- : effectively having 'two' copies of fcntl.h
-
- Same as above, privat modifications aren't the right way.
-
- : o Leave fcntl.h in the /usr/include directory and modify incoming
- : source to look for it there.
-
- Yes, please do so, until this problem is solved by MWC!
-
- I've take a look at various System V's, the real fcntl.h lives in
- /usr/include/sys, and /usr/include/fcntl.h only contains one line:
- #include <sys/fcntl.h>
- Of cause also a link would work.
-
- PS: I'll mail a copy of this article to MWC, just to be sure that
- someone there get informed about this problem.
- --
- Udo Munk | voice: +49 2131 275348 | uucp: +49 2131 278869
- Oberstr. 21 | mail : udo@umunk.GUN.de | 2400/1200/300 8N1
- 4040 Neuss 1 | ...!{mcshh,smurf,unido}!easix!umunk!udo | MYNAME=bbsuser
- Fed. Rep. of | CompuServe: 100021,2515 | login: uucp
- Germany | first get /usr/spool/uucppublic/info | pwd: public
-