From: Jeff King <peff@peff.net>
To: Lance Fredrickson <lancethepants@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: bug report: build issue with git 2.2.2 using uclibc toolchain
Date: Fri, 30 Jan 2015 11:33:32 -0500 [thread overview]
Message-ID: <20150130163331.GA5239@peff.net> (raw)
In-Reply-To: <54CBA968.2040807@gmail.com>
On Fri, Jan 30, 2015 at 08:55:20AM -0700, Lance Fredrickson wrote:
> I've been keeping up-to-date versions of git built for an embedded mipsel
> architecture device running on uclibc.
> 2.2.1 and previous versions build fine, but 2.2.2 stops with an error.
>
> The toolchain is an OpenWRT variant (entware) using gcc 4.6.4 and uclibc
> 0.9.32, available at the following.
> http://entware.wl500g.info/sources/
>
> Here is the output of the build error.
>
> CC builtin/grep.o
> builtin/get-tar-commit-id.c: In function 'cmd_get_tar_commit_id':
> builtin/get-tar-commit-id.c:31:12: error: dereferencing pointer to
> incomplete type
That seems odd. The line in question is:
if (header->typeflag[0] != 'g')
the "header" variable is defined above as:
struct ustar_header *header = (struct ustar_header *)buffer;
and "struct ustar_header" is defined in "tar.h", which is included
above.
uclibc ships its own tar.h. Ours should take precedence (because we use
""), but perhaps there is something funny going on in the build
settings. I can't find any interesting changes in v2.2.1..v2.2.2,
though.
Can you double-check that v2.2.1 still builds, and if so try to use "git
bisect start v2.2.2 v2.2.1" to find the responsible commit?
-Peff
prev parent reply other threads:[~2015-01-30 16:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-30 15:55 bug report: build issue with git 2.2.2 using uclibc toolchain Lance Fredrickson
2015-01-30 16:30 ` Lance Fredrickson
2015-01-30 16:33 ` Jeff King [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=20150130163331.GA5239@peff.net \
--to=peff@peff.net \
--cc=git@vger.kernel.org \
--cc=lancethepants@gmail.com \
/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).