From: Fabio Aiuto <polinice83@libero.it>
To: git@vger.kernel.org
Subject: Semantic errors
Date: Thu, 21 Mar 2019 20:06:11 +0100 [thread overview]
Message-ID: <1553195171.1436.1.camel@libero.it> (raw)
Hello to all,
I'm browsins git code with Eclipse. I'm on a local branch called
"studio" based on master (last public commit e902e9b by Junio C Hamano
on Monday March 11 2019). I've built everything by changing:
CFLAGS = -g -Wall (removing -O2 to have smooth trace in debugging).
But the environment detects the following semantic errors (I made no
edits!!!):
Description Resource Path Location Type
Symbol 'GIT_HTML_PATH' could not be resolved git.c /git
line 154 Semantic Error
Symbol 'GIT_MAN_PATH' could not be resolved git.c /git
line 158 Semantic Error
Symbol 'GIT_INFO_PATH' could not be resolved git.c /git
line 162 Semantic Error
Symbol 'active_cache' could not be resolved commit.c /git
/builtin line 899 Semantic Error
Field 'ce_intent_to_add(active_cache[i])' could not be resolved
commit.c /git/builtin line 899 Semantic Error
Symbol 'active_nr' could not be resolved commit.c /git/bu
iltin line 889 Semantic Error
Symbol 'active_nr' could not be resolved commit.c /git/bu
iltin line 898 Semantic Error
Field 'oid' could not be resolved commit.c /git/builtin
line 1654 Semantic Error
Symbol 'active_nr' could not be resolved commit.c /git/bu
iltin line 901 Semantic Error
Symbol 'active_cache_tree' could not be resolved commit.c
/git/builtin line 1654 Semantic Error
Symbol 'active_cache_changed' could not be resolved commit.c
/git/builtin line 418 Semantic Error
Symbol 'active_cache_tree' could not be resolved commit.c
/git/builtin line 419 Semantic Error
Symbol 'active_nr' could not be resolved commit.c /git/bu
iltin line 254 Semantic Error
Symbol 'active_cache' could not be resolved commit.c /git
/builtin line 255 Semantic Error
I can debug without problems, but what if I should trece through one of
those errors?
How can I fix them?
Thanks in advance!!!
Fabio.
next reply other threads:[~2019-03-21 19:06 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-21 19:06 Fabio Aiuto [this message]
2019-03-21 19:16 ` Semantic errors Randall S. Becker
2019-03-21 19:32 ` Fabio Aiuto
2019-03-21 21:03 ` Randall S. Becker
2019-03-22 20:24 ` Fabio Aiuto
2019-03-22 21:15 ` Randall S. Becker
2019-03-22 21:25 ` Fabio Aiuto
2019-03-22 21:39 ` Randall S. Becker
2019-03-22 21:41 ` Fabio Aiuto
2019-03-22 22:43 ` Randall S. Becker
2019-03-23 12:14 ` Fabio Aiuto
2019-03-23 13:00 ` Fabio Aiuto
2019-03-23 19:34 ` Randall S. Becker
2019-03-25 19:21 ` Fabio Aiuto
2019-03-25 19:35 ` Randall S. Becker
2019-03-25 19:37 ` Fabio Aiuto
2019-03-22 21:39 ` Fabio Aiuto
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=1553195171.1436.1.camel@libero.it \
--to=polinice83@libero.it \
--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.