Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!uwm.edu!zaphod.mps.ohio-state.edu!tut.cis.ohio-state.edu!ucbvax!hplabs!hp-sdd!ncr-sd!sagpd1!jharkins
From: jharkins@sagpd1.UUCP (Jim Harkins)
Newsgroups: comp.lang.c
Subject: Re: help with UNIX include files
Message-ID: <602@sagpd1.UUCP>
Date: 18 Jan 90 20:45:12 GMT
References: <1990Jan16.202640.357@csusac.csus.edu> <4092@helios.TAMU.EDU>
Reply-To: jharkins@sagpd1.UUCP (Jim Harkins)
Distribution: usa
Organization: Scientific Atlanta, Government Products Div, San Diego, CA
Lines: 13

In article <4092@helios.TAMU.EDU>, john@stat.tamu.edu (John S. Price) writes:
> If the include
> files aren't there, you must use #include "/path.../foo.h", or if it
> is in the directory you are compiling from, use #include "foo.h".

Close, but this ain't horseshoes.  If you use #include "foo.h" the compiler
looks for foo.h in the directory the source file is in, not neccesarily
the directory you are compiling from.  For example, if you are in the directory
fred and issue the command 'cc ../src/foo.c', foo.h will only be found if
it lives ../src, not if it lives in fred.

jim
"only dead fish go with the flow."