Path: utzoo!mnetor!uunet!lll-winken!lll-lcc!ames!pasteur!ucbvax!hplabs!hpcea!hpfcdc!rml
From: rml@hpfcdc.HP.COM (Bob Lenk)
Newsgroups: comp.sys.hp
Subject: Re: Where are the netinet files?
Message-ID: <5570033@hpfcdc.HP.COM>
Date: 20 Apr 88 00:01:59 GMT
References: <12104@sri-spam.istc.sri.com>
Organization: HP Ft. Collins, Co.
Lines: 24

>                  The biggest problem I've encountered thus far is finding
>    a lot of the .h system files on the HP that are on the Sun.

SunOS is a BSD-based system.  HP-UX is a System V compatible system.
The headers you mention are from BSD.  Although we do provide many
BSD features (and headers) we don't provide them all.  As such, porting
BSD code is not always painless (or even easy).

>                               I finally got it to work by including the
>    full pathname of /usr/lib/libBSD.a to be compiled with the other object
>    files.  The "-lBSD" argument to cc didn't work, even though my reading
>    of the cc man page indicates that it should.

Where on the cc command line did you place the -lBSD option?  This
option is simply a shorthand for /usr/lib/libBSD.a, which would show
up at the same point in the command line.  Thus the option usually must
go at the end of the command line (unlike normal option syntax), since
the linker only extracts from a library .o files that resolve unresolved
references from files preceding it on the command line.  This is
common to all implementations I know of, but probably not explained
well in the manual.

		Bob Lenk
		{ihnp4, hplabs}!hpfcla!rml
		rml%hpfcla@hplabs.hp.com