On Sun, Nov 15, 2009 at 12:50:39PM +0100, Felix Zielcke wrote:
> > > $ srcdir=$PWD builddir=$PWD gcc -isystem=$srcdir/include 
> > > -I$srcdir/include -I$builddir -I$builddir/include test.c -o test && ls 
> > > test
> > > test
> > > $ srcdir=$PWD builddir=$PWD gcc -nostdinc -isystem $(gcc 
> > > -print-file-name=include) -I$srcdir/include -I$builddir 
> > > -I$builddir/include test.c 
> > > test.c:2:20: error: stdint.h: No such file or directory
> > 
> > We used -isystem as a way of excluding system headers but not gcc headers.
> > With the -print-file-name trick this seems to be no longer necessary, right?
> > 
> > So why not "-nostdinc -I$(gcc -print-file-name=include)" instead?
> 
> I think we should use -isystem for the gcc internal header files not -I,
> but I just tested experimental branch with -I instead of -isystem and
> also compiles cleanly (except the usual grub.texi warnings)

Seems fine.  Thanks for investigating this.

-- 
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

Reply via email to