Date: Mon, 19 May 2008 15:14:08 -0500 From: Dave Uhring <duhring@charter.net> To: Lowell Gilbert <freebsd-stable-local@be-well.ilk.org> Cc: freebsd-stable@freebsd.org Subject: Re: Buildworld Fails RELENG_7 Message-ID: <20080519201408.GD79130@charter.net> In-Reply-To: <448wy6yviw.fsf@be-well.ilk.org> References: <20080519151739.GA50653@charter.net> <4AB77C7C-55F7-4CC3-B842-E684F6C899E3@rabson.org> <20080519163825.GA32372@charter.net> <DB8B754A-5994-4358-9F8C-93218AAEF9F4@rabson.org> <20080519165421.GA62264@charter.net> <20080519170223.GH7468@bunrab.catwhisker.org> <20080519175358.GB55020@charter.net> <20080519180201.GI7468@bunrab.catwhisker.org> <20080519183614.GB55295@charter.net> <448wy6yviw.fsf@be-well.ilk.org>
index | next in thread | previous in thread | raw e-mail
On Mon, May 19, 2008 at 02:54:31PM -0400, Lowell Gilbert wrote: > Dave Uhring <duhring@charter.net> writes: > > > > If a -I/some/directory is used as a CFLAG then the *include directive must read > > > > #include <driver.h>, *not* #include "driver.h". The latter demands that the > > header file be in the same directory as the source file. > > Not that it necessarily affects what you're going through, but that > last statement is incorrect. The double quotes are (according to the > C standard) implementation defined, and gcc (like many other > compilers) will prefer the local directory for the double quotes, but > will search the entire search path if it doesn't find the file there. The problem is that gcc is *not* finding the file in the directory referenced by the -I cflag. If I copy the header files to the directory where the error occurs the header file is found and used to compile the source file.home | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20080519201408.GD79130>