{"thread":{"id":"38473","subject":"bug report: build issue with git 2.2.2 using uclibc toolchain","startedAt":"2015-01-30T15:55:20Z","lastAt":"2015-01-30T16:33:32Z","messageCount":3,"participants":["Lance Fredrickson","Jeff King"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"255436","messageId":"54CBA968.2040807@gmail.com","threadId":"38473","inReplyTo":null,"subject":"bug report: build issue with git 2.2.2 using uclibc toolchain","fromName":"Lance Fredrickson","fromEmail":"lancethepants@gmail.com","sentAt":"2015-01-30T15:55:20Z","receivedAt":"2015-01-30T15:55:20Z","isPatch":false,"sender":{"key":"lancethepants@gmail.com","avatar":"https://gravatar.com/avatar/88dd92f9e4060d50dc978b7ace37c6b24daa5dcd3d2b744ef0aa670c75813a5c?d=mp&s=160"},"body":"I've been keeping up-to-date versions of git built for an embedded \nmipsel architecture device running on uclibc.\n2.2.1 and previous versions build fine, but 2.2.2 stops with an error.\n\nThe toolchain is an OpenWRT variant (entware) using gcc 4.6.4 and uclibc \n0.9.32, available at the following.\nhttp://entware.wl500g.info/sources/\n\nHere is the output of the build error.\n\nCC builtin/grep.o\nbuiltin/get-tar-commit-id.c: In function 'cmd_get_tar_commit_id':\nbuiltin/get-tar-commit-id.c:31:12: error: dereferencing pointer to \nincomplete type\n"},{"id":"255437","messageId":"54CBB1A3.9000805@gmail.com","threadId":"38473","inReplyTo":"54CBA968.2040807@gmail.com","subject":"Re: bug report: build issue with git 2.2.2 using uclibc toolchain","fromName":"Lance Fredrickson","fromEmail":"lancethepants@gmail.com","sentAt":"2015-01-30T16:30:27Z","receivedAt":"2015-01-30T16:30:27Z","isPatch":false,"sender":{"key":"lancethepants@gmail.com","avatar":"https://gravatar.com/avatar/88dd92f9e4060d50dc978b7ace37c6b24daa5dcd3d2b744ef0aa670c75813a5c?d=mp&s=160"},"body":"Sorry, file this one away under user error. I had an issue with my build \nenvironment.\ncheers!\n\nOn 1/30/2015 8:55 AM, Lance Fredrickson wrote:\n> I've been keeping up-to-date versions of git built for an embedded \n> mipsel architecture device running on uclibc.\n> 2.2.1 and previous versions build fine, but 2.2.2 stops with an error.\n>\n> The toolchain is an OpenWRT variant (entware) using gcc 4.6.4 and \n> uclibc 0.9.32, available at the following.\n> http://entware.wl500g.info/sources/\n>\n> Here is the output of the build error.\n>\n> CC builtin/grep.o\n> builtin/get-tar-commit-id.c: In function 'cmd_get_tar_commit_id':\n> builtin/get-tar-commit-id.c:31:12: error: dereferencing pointer to \n> incomplete type\n"},{"id":"255438","messageId":"20150130163331.GA5239@peff.net","threadId":"38473","inReplyTo":"54CBA968.2040807@gmail.com","subject":"Re: bug report: build issue with git 2.2.2 using uclibc toolchain","fromName":"Jeff King","fromEmail":"peff@peff.net","sentAt":"2015-01-30T16:33:32Z","receivedAt":"2015-01-30T16:33:32Z","isPatch":false,"sender":{"key":"peff@peff.net","avatar":"https://avatars.githubusercontent.com/u/45925?v=4"},"body":"On Fri, Jan 30, 2015 at 08:55:20AM -0700, Lance Fredrickson wrote:\n\n> I've been keeping up-to-date versions of git built for an embedded mipsel\n> architecture device running on uclibc.\n> 2.2.1 and previous versions build fine, but 2.2.2 stops with an error.\n> \n> The toolchain is an OpenWRT variant (entware) using gcc 4.6.4 and uclibc\n> 0.9.32, available at the following.\n> http://entware.wl500g.info/sources/\n> \n> Here is the output of the build error.\n> \n> CC builtin/grep.o\n> builtin/get-tar-commit-id.c: In function 'cmd_get_tar_commit_id':\n> builtin/get-tar-commit-id.c:31:12: error: dereferencing pointer to\n> incomplete type\n\nThat seems odd. The line in question is:\n\n  if (header->typeflag[0] != 'g')\n\nthe \"header\" variable is defined above as:\n\n  struct ustar_header *header = (struct ustar_header *)buffer;\n\nand \"struct ustar_header\" is defined in \"tar.h\", which is included\nabove.\n\nuclibc ships its own tar.h. Ours should take precedence (because we use\n\"\"), but perhaps there is something funny going on in the build\nsettings. I can't find any interesting changes in v2.2.1..v2.2.2,\nthough.\n\nCan you double-check that v2.2.1 still builds, and if so try to use \"git\nbisect start v2.2.2 v2.2.1\" to find the responsible commit?\n\n-Peff\n"}]}