# tar-tree.c dereferencing pointer to incomplete type 5 messages from 2013-01-19 to 2013-01-19. Participants: 白い熊, Duy Nguyen, Jonathan Nieder. Thread: https://gitlist.dev/t/32671 ## 白い熊, 2013-01-19 13:31 Subject: tar-tree.c dereferencing pointer to incomplete type Message-ID: URL: https://gitlist.dev/e/CAPy7p-45-E-vWcjBTXSLpjoQLic54JdAoKqB3jz4RA6GzAkw8w%40mail.gmail.com ``` Hello: I'm building v 1.8.1.1 on Android. The build chokes on the builtins phase on tar-tree.c with: CC builtin/tar-tree.o builtin/tar-tree.c: In function 'cmd_get_tar_commit_id': builtin/tar-tree.c:93:12: error: dereferencing pointer to incomplete type make: *** [builtin/tar-tree.o] Error 1 The line that's causing this in tar-tree.c is: if (header->typeflag[0] != 'g') from int cmd_get_tar_commit_id(int argc, const char **argv, const char *prefix) { char buffer[HEADERSIZE]; struct ustar_header *header = (struct ustar_header *)buffer; char *content = buffer + RECORDSIZE; ssize_t n; if (argc != 1) usage(builtin_get_tar_commit_id_usage); n = read_in_full(0, buffer, HEADERSIZE); if (n < HEADERSIZE) die("git get-tar-commit-id: read error"); if (header->typeflag[0] != 'g') return 1; if (memcmp(content, "52 comment=", 11)) return 1; n = write_in_full(1, content + 11, 41); if (n < 41) die_errno("git get-tar-commit-id: write error"); return 0; } But why? What's messed up with my setup. I can compile no probs on other machines. I'm trying to get my head round this, but don't see the problem? -- 白い熊 ``` ## Duy Nguyen, 2013-01-19 13:37 Subject: Re: tar-tree.c dereferencing pointer to incomplete type Message-ID: URL: https://gitlist.dev/e/CACsJy8DfOYRmF6FqTLCAYgXGpECX-VhpXGK5CfcmVvKXQ%2BDpuA%40mail.gmail.com In-Reply-To: ``` On Sat, Jan 19, 2013 at 8:31 PM, 白い熊 wrote: > Hello: > > I'm building v 1.8.1.1 on Android. The build chokes on the builtins > phase on tar-tree.c with: > > CC builtin/tar-tree.o > builtin/tar-tree.c: In function 'cmd_get_tar_commit_id': > builtin/tar-tree.c:93:12: error: dereferencing pointer to incomplete type > make: *** [builtin/tar-tree.o] Error 1 > > The line that's causing this in tar-tree.c is: > > if (header->typeflag[0] != 'g') There is another tar.h somewhere in your system? Stopping the compilation after proprocessing should show if it includes the correct tar.h. -- Duy ``` ## 白い熊, 2013-01-19 14:26 Subject: Re: tar-tree.c dereferencing pointer to incomplete type Message-ID: URL: https://gitlist.dev/e/CAPy7p-7V6y4hfLrYYi_3zGkzGTw2BeF5wh3zPYzumrp%2BPbqr%2BQ%40mail.gmail.com In-Reply-To: ``` On Sat, Jan 19, 2013 at 5:37 PM, Duy Nguyen wrote: > There is another tar.h somewhere in your system? Stopping the > compilation after proprocessing should show if it includes the correct > tar.h. Thank you, this must've been it, as it was finding tar.h from glibc. 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... -- 白い熊 ``` ## 白い熊, 2013-01-19 14:37 Subject: Re: tar-tree.c dereferencing pointer to incomplete type Message-ID: URL: https://gitlist.dev/e/CAPy7p-5vZKzznSny97BZMWHxHPJupO3in7tvjyFOTxBYzw5D4Q%40mail.gmail.com In-Reply-To: ``` On Sat, Jan 19, 2013 at 6:26 PM, 白い熊 wrote: > Thank you, this must've been it, as it was finding tar.h from glibc. > > 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. All's good now. Thank you :@) -- 白い熊 ``` ## Jonathan Nieder, 2013-01-19 21:28 Subject: Re: tar-tree.c dereferencing pointer to incomplete type Message-ID: <20130119212851.GA4009@elie.Belkin> URL: https://gitlist.dev/e/20130119212851.GA4009%40elie.Belkin In-Reply-To: ``` 白い熊 wrote: > On Sat, Jan 19, 2013 at 6:26 PM, 白い熊 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 ```