Date: Mon, 19 May 2008 20:38:25 -0500 From: Dave Uhring <duhring@charter.net> To: Clifton Royston <cliftonr@lava.net> Cc: freebsd-stable@freebsd.org Subject: Re: Buildworld Fails RELENG_7 Message-ID: <20080520013825.GB1310@charter.net> In-Reply-To: <20080520000147.GA2824@lava.net> References: <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> <20080520000147.GA2824@lava.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, May 19, 2008 at 02:01:48PM -1000, Clifton Royston wrote: > On Mon, May 19, 2008 at 03:14:08PM -0500, Dave Uhring wrote: > > > > 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. The c compiler is the one shipped with 7.0 RELEASE. Except for the 3 new header files that I placed from cvsupped sources into /usr/include/sys the entire system is 7.0 RELEASE. Prior to beginning the build I deliberately set # export CFLAGS="" Nothing else in my environment would have affected the compiler.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20080520013825.GB1310>