From: Lance Fredrickson <lancethepants@gmail.com>
To: git@vger.kernel.org
Subject: Re: bug report: build issue with git 2.2.2 using uclibc toolchain
Date: Fri, 30 Jan 2015 09:30:27 -0700 [thread overview]
Message-ID: <54CBB1A3.9000805@gmail.com> (raw)
In-Reply-To: <54CBA968.2040807@gmail.com>
Sorry, file this one away under user error. I had an issue with my build
environment.
cheers!
On 1/30/2015 8:55 AM, 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
next prev parent reply other threads:[~2015-01-30 16:30 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 [this message]
2015-01-30 16:33 ` Jeff King
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=54CBB1A3.9000805@gmail.com \
--to=lancethepants@gmail.com \
--cc=git@vger.kernel.org \
/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).