mmz@alexandria.cc (May) wrote in news:cfcc3917.0311231944.13209842
@posting.google.com:

> I have a problem with these files.
>
> #include
>
> #include
> #include
> #include
> #include
>
> Could someone please tell me where to find these files?

unistd.h should come with your UNIX distribution. The others are all
included in the standard X distribution. Note that they will all include more
files, so you really need a whole distribution.

Ken Lee, http://www.rahul.net/kenton/

Are you having a problem compiling? Make sure to specify the library
directory.

cc MyCode.c -o MyCode -L/usr/X11R6/lib -lX11

If that doesn't work, try changing X11R6 to X11, but I think for Xfree86
it should always be X11R6.

Good luck,
Tom

On 23 Nov 2003 19:44:21 -0800, May wrote:

> I have a problem with these files.
>
> #include
>
> #include
> #include
> #include
> #include
>
> Could someone please tell me where to find these files?
>
> Thanks in advance for any help that you can give me!!
>
>
> Yours Sincerely,
> May



--
Using M2, Opera's revolutionary e-mail client: http://www.opera.com/m2/

Wouldn't the original poster need to add -I/usr/X11R6/include?

Tom Junior wrote:

> Are you having a problem compiling? Make sure to specify the library
> directory.
>
> cc MyCode.c -o MyCode -L/usr/X11R6/lib -lX11
>

In comp.windows.x, May

wrote
on 23 Nov 2003 19:44:21 -0800
:
> I have a problem with these files.
>
> #include
>
> #include
> #include
> #include
> #include
>
> Could someone please tell me where to find these files?
>
> Thanks in advance for any help that you can give me!!
>
>
> Yours Sincerely,
> May

Linux puts them in /usr/X11R6/include/X11/Intrinsic.h etc.
Another poster has already specified how to properly include
them in your command line for compilation; the following should
work reasonably well on most Linux systems.

cc -I/usr/X11R6/include -L/usr/X11R6/lib x_something.c -o x_something -lX11

I'd have to look regarding Solaris as a few extra things may be
required in there; note also that Solaris likes to put things in
/usr/openwin/include for various reasons.

I am also not entirely sure whether a space between the
#include and the < is needed, or not.

--
#191, ewill3@earthlink.net
It's still legal to go .sigless.