Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!ucbvax!hplabs!hplabsz!mayer
From: mayer@hplabsz.HPL.HP.COM (Niels Mayer)
Newsgroups: comp.sys.hp
Subject: Re: HP X11 include file problem
Message-ID: <2971@hplabsz.HPL.HP.COM>
Date: 24 Feb 89 06:56:18 GMT
References: <508@mmlai.UUCP>
Reply-To: mayer@hplabs.hp.com (Niels Mayer)
Organization: Hewlett-Packard Labs, Software Technology Lab, Palo Alto, CA.
Lines: 28
Summary:
Expires:
Sender:
Followup-To:

In article <508@mmlai.UUCP> burzio@mmlai.UUCP (Tony Burzio) writes:
>Several of my programs are bombing in compile because the
>include file /usr/include/X11/Xos.h is looking for the
>file <strings.h> and it can't find it.  Hmmm..  This sounds
>like a BSD dependancy.  Anyone from HP know about this?

/usr/include/X11/Xos.h has a bunch of stuff like
> #ifdef SYSV
> #include <string.h>
> #define index strchr
> #define rindex strrchr
> #else /* SYSV */
> #include <strings.h>
> #endif /* SYSV */.

These ifdefs hopefully take care of the superficial differences between
SYSV-based systems (like HPUX) and BSD-based systems (like SunOS).

So the proper way to compile a file name.c containing X11/Xt/Xw calls
should be:
	"cc -c -O -DSYSV +Nd4000 +Ns4000 name.c" for an HP9000s3xx system, and
	"cc -c -O -DSYSV name.c" for an HP9000x8xx system.

The MIT X11 sources force -DSYSV through imake's machine-specific
configuration files. Including <X11/Xos.h> in your X11 client source allows
for some degree of program portability across unix variants.

-- Niels.