From: Jonathan Nieder <jrnieder@gmail.com>
To: git@vger.kernel.org
Cc: 白い熊 <ShiroiKuma@ShiroiKuma.org>, "Duy Nguyen" <pclouds@gmail.com>,
"Rene Scharfe" <rene.scharfe@lsrfire.ath.cx>
Subject: Re: tar-tree.c dereferencing pointer to incomplete type
Date: Sat, 19 Jan 2013 13:28:51 -0800 [thread overview]
Message-ID: <20130119212851.GA4009@elie.Belkin> (raw)
In-Reply-To: <CAPy7p-5vZKzznSny97BZMWHxHPJupO3in7tvjyFOTxBYzw5D4Q@mail.gmail.com>
白い熊 wrote:
> On Sat, Jan 19, 2013 at 6:26 PM, 白い熊 <ShiroiKuma@shiroikuma.org> 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
prev parent reply other threads:[~2013-01-19 21:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-19 13:31 tar-tree.c dereferencing pointer to incomplete type 白い熊
2013-01-19 13:37 ` Duy Nguyen
2013-01-19 14:26 ` 白い熊
2013-01-19 14:37 ` 白い熊
2013-01-19 21:28 ` Jonathan Nieder [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20130119212851.GA4009@elie.Belkin \
--to=jrnieder@gmail.com \
--cc=ShiroiKuma@ShiroiKuma.org \
--cc=git@vger.kernel.org \
--cc=pclouds@gmail.com \
--cc=rene.scharfe@lsrfire.ath.cx \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).