Makeing "Gated"

[Root Boy Jim]

In article <kre.671424242 at mundamutti.cs.mu.OZ.AU> kre at cs.mu.OZ.AU (Robert Elz) writes:
>keyvan at 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).

I don't believe that it was in the original 4.3. At least it's not
documented in the manual sets that you get from Usenix (or us).
It may have been hidden away in some System V compatibility
library directory in the source tree, however. In any case,
it's certainly been available for quite some time. The Tahoe
version has a copyright date of 85/08/05, which predates 4.3.

It appears that vendors who chase dual universes can't keep up
with either one. Sequent does just as bad of a job.

>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.

Perhaps I wasn't explicit enuf. Sequent lets you mix and match.
Pyramid, on the other hand, puts a reference to either
__ucblibc_Id_ or __attlibc_Id in every object in the library,
except for version.o, which defines same.

So yes, you can use both librarys. I just ran the following program
main(){printf("memcmp(\"foo\",\"bar\") = %x\n",memcmp("foo","bar"));}
with the command line: cc -o qaz qaz.c -lc /.attlib/libc.a
The answer, btw, is 4.

I suppose I can pull out both version.o and add them to each
library along with anything else I want to cross-pollenate.
-- 
		[rbj at uunet 1] stty sane
		unknown mode: sane