It appears that -nostdinc also excludes GCC internal header directory (for e.g. stdarg.h), which I didn't expect.
Does someone know a clean way to resolve this? A quick check at GCC command-line options didn't reveal a way to explicitly include that directory afterwards without knowing its path. I.e. something similar to `gcc -print-file-name=libgcc.a` On Thu, Oct 29, 2009 at 12:16:23AM +0100, Robert Millan wrote: > > Committed then. > > On Mon, Oct 26, 2009 at 05:16:38PM +0100, Robert Millan wrote: > > > > It should be pretty obvious that we don't want to use system headers when > > building target, but we've been for so long without this flag that I want > > to make sure. > > > > Does anyone see a problem with it? > > > > -- > > Robert Millan > > > > The DRM opt-in fallacy: "Your data belongs to us. We will decide when (and > > how) you may access your data; but nobody's threatening your freedom: we > > still allow you to remove your data and not access it at all." > > > > > $ bzr diff -r 1768..1769 > > bzr+ssh://bzr.savannah.gnu.org/grub/people/robertmh/lib-linux/Makefile.in > > > > 2009-10-26 Robert Millan <rmh.g...@aybabtu.com> > > > > * Makefile.in (TARGET_CPPFLAGS): Add `-nostdinc'. > > > > === modified file 'Makefile.in' > > --- Makefile.in 2009-10-06 00:04:32 +0000 > > +++ Makefile.in 2009-10-23 13:31:15 +0000 > > @@ -75,7 +75,7 @@ > > TARGET_MODULE_FORMAT = @TARGET_MODULE_FORMAT@ > > TARGET_APPLE_CC = @TARGET_APPLE_CC@ > > OBJCONV = @OBJCONV@ > > -TARGET_CPPFLAGS = @TARGET_CPPFLAGS@ -I$(builddir) -I$(builddir)/include > > -I$(srcdir)/include \ > > +TARGET_CPPFLAGS = @TARGET_CPPFLAGS@ -nostdinc -I$(builddir) > > -I$(builddir)/include -I$(srcdir)/include \ > > -Wall -W > > TARGET_LDFLAGS = @TARGET_LDFLAGS@ > > TARGET_IMG_LDSCRIPT = @TARGET_IMG_LDSCRIPT@ > > > > > _______________________________________________ > > Grub-devel mailing list > > Grub-devel@gnu.org > > http://lists.gnu.org/mailman/listinfo/grub-devel > > > -- > Robert Millan > > The DRM opt-in fallacy: "Your data belongs to us. We will decide when (and > how) you may access your data; but nobody's threatening your freedom: we > still allow you to remove your data and not access it at all." -- Robert Millan The DRM opt-in fallacy: "Your data belongs to us. We will decide when (and how) you may access your data; but nobody's threatening your freedom: we still allow you to remove your data and not access it at all." _______________________________________________ Grub-devel mailing list Grub-devel@gnu.org http://lists.gnu.org/mailman/listinfo/grub-devel
