Path: utzoo!utgpu!news-server.csri.toronto.edu!mailrus!cs.utexas.edu!oakhill!dover!digital!digital.sps.mot.com!chen From: chen@digital.sps.mot.com (Jinfu Chen) Newsgroups: comp.sys.apollo Subject: Re: Skeleton include files Message-ID: <4c7dbdb4.12c9a@digital.sps.mot.com> Date: 29 Aug 90 15:43:33 GMT References: <1990Aug28.204058.17366@unx.sas.com> <4c7aae64.20b6d@apollo.HP.COM> Sender: news@digital.sps.mot.com Distribution: usa Organization: Motorola, LICD, SPS, Mesa, AZ Lines: 44 In article <4c7aae64.20b6d@apollo.HP.COM> ced@apollo.HP.COM (Carl Davidson) writes: >aspect, not only of code, but of user skills. In the last three years (since we >began running SR10 and its descendents here in Chelmsford) I've ported several >programs "right off the net" without any trouble at all: Mush (versions 5.7, >6.0, 6.1, 7.0, and now 7.1), VN, GWM, mkmf, arc 5.21, cpr, and rolo, just to >name a few. In general, the sources compiled, linked, and run with no >modification. Occasionally I've had the odd problem with the fact that our >C compiler is pickier than most about not abusing pointers and such, but I >don't recall ever having a problem with include files. I tend to agree with Carl for pulling programs off net and compiling without too much problem in SR10.x. However, every once a while I'd encounter a program using some include files that I can't find. For examlpe, nntp is one. Most of time I could get one from a Sun system and hack around some equivalent code but that's still extra efforts. Although the latest release has some #ifdef apollo lines to get around the missing file which apparantly is available in, according to cpp symbols, sun, hpux, pyr, hp300, and NeXT, it's still annoying to see Apollo sits out off the majority. Since I am not a BSD expert but an avid BSD user, I don't know how compatible Domain/OS BSD4.3 to the "real" BSD4.3. If there is a BSD 4.3 comformance test suite, like the SYS V3 test suite, I hope Apollo could pass it. >Programs that want to access /dev/kmem aside, I've never had a serious problem >porting user-space code that runs on any other 4.3bsd-based system. That's not >to say that we're perfect, because, of course Domain/OS isn't perfect. What >might be interesting would be to ask other readers of comp.sys.apollo to >give us the benefit of their accumulated wisdom regarding porting code gleaned >from comp.sources.unix and alt.sources to Domain/OS. I'm sure there are folks >out there with a significant bag of tricks that we could all benefit from. >How about it, folks? Perhaps another way is to have some HP/Apollo people who are BSD fans, such as Carl, to push from inside. User community will benifit from it. Of course, we could all wait for OSF/1 :-) -- Jinfu Chen (602)898-5338 Motorola, Inc. SPS Mesa, AZ ...uunet!motsps!digital!chen chen@digital.sps.mot.com CMS: RXFR30 at MESAVM ----------