白い熊 wrote: > On Sat, Jan 19, 2013 at 6:26 PM, 白い熊 <ShiroiKuma@xxxxxxxxxxxxxx> wrote: >> Moved it and compiles fine. In fact I moved it back now, so it should >> be finding it again and it still builds fine, no trace of the prior >> error. I'm dumbfounded! But at least it compiles... > > OK, figured it out. It was indeed the wrong tar.h, the one that was > making it bomb was the kernel headers tar.h from the Android source. > That explains it quite well. Hm. Is there anything to do to make our headers specified with -I take precedence over unrelated system headers when processing '#include "foo.h"' directives? Thanks, Jonathan -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html