All of lore.kernel.org
 help / color / mirror / Atom feed
From: Lance <lancethepants@gmail.com>
To: git@vger.kernel.org
Subject: Issue with compiling git 1.8.4 under uclibc with gcc 4.6.3
Date: Mon, 26 Aug 2013 14:10:43 -0600	[thread overview]
Message-ID: <521BB643.304@gmail.com> (raw)

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

             reply	other threads:[~2013-08-26 20:10 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-26 20:10 Lance [this message]
2013-08-26 20:18 ` Issue with compiling git 1.8.4 under uclibc with gcc 4.6.3 Lukas Fleischer
2013-08-26 20:29   ` Lance
2013-08-26 20:31     ` Lukas Fleischer
2013-08-26 20:59       ` Jeff King
2013-08-26 21:57         ` [PATCH] config: do not use C function names as struct members Jeff King
2013-08-27  0:56           ` Lukas Fleischer
2013-08-27  4:38           ` Junio C Hamano
2013-08-26 21:07       ` Issue with compiling git 1.8.4 under uclibc with gcc 4.6.3 Andreas Schwab

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=521BB643.304@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.