Date: Mon, 19 May 2008 14:01:48 -1000 From: Clifton Royston <cliftonr@lava.net> To: Dave Uhring <duhring@charter.net> Cc: freebsd-stable@freebsd.org Subject: Re: Buildworld Fails RELENG_7 Message-ID: <20080520000147.GA2824@lava.net> In-Reply-To: <20080519201408.GD79130@charter.net> References: <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> <20080519201408.GD79130@charter.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, May 19, 2008 at 03:14:08PM -0500, Dave Uhring wrote:
> 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.
This starts to narrow down the problem you're having a bit, I think.
Given that this is different from the expected behavior and the
behavior others are seeing, this sounds to me like either 1) the wrong
compiler or version of the compiler is being found and used in place of
the desired gcc instance, or 2) something in your shell or environment
is somehow getting into the buildworld environment and causing make or
the inner shell to misparse the commandline to gcc.
-- Clifton
--
Clifton Royston -- cliftonr@iandicomputing.com / cliftonr@lava.net
President - I and I Computing * http://www.iandicomputing.com/
Custom programming, network design, systems and network consulting services
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20080520000147.GA2824>