Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!usc!cs.utexas.edu!uwm.edu!bionet!agate!dog.ee.lbl.gov!nosc!uhccux!munnari.oz.au!mundamutti.cs.mu.OZ.AU!kre From: kre@cs.mu.OZ.AU (Robert Elz) Newsgroups: comp.sys.pyramid,aus.pyramid Subject: Re: Makeing "Gated" Keywords: Gated Message-ID: Date: 12 Apr 91 02:44:02 GMT References: <1991Apr8.073344.2646@cheops.qld.tne.oz.au> <671136511.AA15442@flaccid> Sender: news@cs.mu.oz.au Lines: 30 keyvan@pyra.co.uk (Keyvan Shirnia Pre Sales) writes: >Well memory.h is only defined in ATT. (That is the definition) Some other >operating systems might have memory.h in their UCB environment, but that >is not true UCB! That's an obsolete notion of what BSD is ... memory.h appeared in BSD in 4.3 (years ago). There's not supposed to be any noticeable difference between the BSD mem*() functions (which is what memory.h is all about) so you should be able to simply copy (or link) the ATT universe memory.h into the UCB universe on a pyramid. Unfortunately, I suspect that this may be just pushing the problem back one layer, as if memory.h isn't in pyramid's UCB universe, then its almost certain that the mem*() functions aren't in the libc in its UCB universe either. You may be able to get around that by linking with the ATT universe libc *after* the UCB universe libc - which means that you'll need to explicitly name that on the cc (or ld) command line, not just default to it. The BSD mem*() functions are supposed to be exact functional duplicates of the Sys V versions - though the true BSD versions don't make any pretence to be effecient - they were just added to make it easier to move Sys V progs to BSD, and in general improve compatability between the two). kre ps: I'm pretty sure of all of this, except what might work on the Pyramid, as I put all this stuff in BSD just before 4.3 was released.