git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Issue with compiling git 1.8.4 under uclibc with gcc 4.6.3

From
Lance <lancethepants@gmail.com>
Date
Aug 26, 2013, 20:10 UTC
Message-ID
<521BB643.304@gmail.com>

Up until the latest release, I've been able to compile git for a uclibc based embedded linux. The toolchain I use is from "entware", which is based off of the openwrt toolchain. https://code.google.com/p/wl500g-repo/

Somewhere between git 1.8.3.4 & 1.8.4 there seems to be some changes that breaks compilation for my particular situation. When cross compiling I receive the following error. I also receive the same error when compiling natively on the uclibc based device itself. Not sure if being uclibc based has anything to do with it, but is noteworthy. I am not a c programmer. Both the cross compiler, and embedded device's version off gcc is 4.6.3. Previous versions compile fine

     CC config.o
config.c: In function 'get_next_char':
config.c:220:14: error: expected identifier before '(' token
config.c:220:14: error: expected statement before ')' token
config.c:220:14: error: expected statement before ')' token
config.c:224:11: error: expected identifier before '(' token
Lance
Next: Lukas Fleischer
Message 1 of 9 in “Issue with compiling git 1.8.4 under uclibc with gcc 4.6.3”
  1. LanceAug 26, 2013
  2. Lukas FleischerAug 26, 2013
  3. LanceAug 26, 2013
  4. Lukas FleischerAug 26, 2013
  5. Jeff KingAug 26, 2013
  6. config: do not use C function names as struct membersJeff King, Aug 26, 2013
  7. Lukas FleischerAug 27, 2013
  8. Junio C HamanoAug 27, 2013
  9. Andreas SchwabAug 26, 2013

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.