Il giorno sab, 23/03/2019 alle 15.34 -0400, Randall S. Becker ha
scritto:

On March 23, 2019 9:00, Fabio Aiuto wrote:

quoted

To: Randall S. Becker <redacted>; git@vger.kernel.org
Subject: Re: Semantic errors

Il giorno ven, 22/03/2019 alle 18.43 -0400, Randall S. Becker ha
scritto:

quoted

quoted

-----Original Message-----
From: Fabio Aiuto <redacted>
Sent: March 22, 2019 17:41
To: Randall S. Becker <redacted>; git@vger.kernel
.org
Subject: Re: Semantic errors

Il giorno ven, 22/03/2019 alle 17.39 -0400, Randall S. Becker
ha
scritto:

quoted

On March 22, 2019 17:25, Fabio Aiuto

quoted

Il giorno gio, 21/03/2019 alle 17.03 -0400, Randall S.
Becker ha
scritto:

quoted

quoted

Of On March 21, 2019 15:32, Fabio Aiuto wrote:
Il giorno gio, 21/03/2019 alle 15.16 -0400, Randall S.
Becker ha
scritto:

quoted

On March 21, 2019 15:06, Fabio Aiuto wrote:

quoted

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	Loca
tion
Type
Symbol 'GIT_HTML_PATH' could not be resolved	
git
.c
/g
it
line 154	Semantic Error
Symbol 'GIT_MAN_PATH' could not be resolved	
git.
c
/gi
t
line 158	Semantic Error
Symbol 'GIT_INFO_PATH' could not be resolved	
git
.c
/g
it
line 162	Semantic Error
Symbol 'active_cache' could not be resolved	
comm
it.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	
Sem
anti
c
Error
Symbol 'active_nr' could not be resolved	com
mit.
c
/gi
t/bu
iltin	line 889	Semantic Error
Symbol 'active_nr' could not be resolved	com
mit.
c
/gi
t/bu
iltin	line 898	Semantic Error
Field 'oid' could not be resolved	commit.c
/g
it/b
uilt
in
line 1654	Semantic Error
Symbol 'active_nr' could not be resolved	com
mit.
c
/gi
t/bu
iltin	line 901	Semantic Error
Symbol 'active_cache_tree' could not be resolved
com
mit.
c
/git/builtin	line 1654	Semantic Error
Symbol 'active_cache_changed' could not be resolved
comm
it.c
/git/builtin	line 418	Semantic Error
Symbol 'active_cache_tree' could not be resolved
com
mit.
c
/git/builtin	line 419	Semantic Error
Symbol 'active_nr' could not be resolved	com
mit.
c
/gi
t/bu
iltin	line 254	Semantic Error
Symbol 'active_cache' could not be resolved	
comm
it.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?

This situation occurs in many projects in ECLIPSE,
not
only git.
The
errors are likely coming from one of the error
parsers
that you have enabled in your workspace. Look in the
Project Properties or Workspace Preferences under
C/C++
Build/Settings in the Error Parsers tab for your
build
configuration.
You may
have to turn off some of those.
There is also the C/C++ General/Code Analysis
Preferences
setting where you might have to turn off the
problematic
errors. I have found that this is a common situation
for
code that is imported into ECLIPSE from other
platforms,
where the GNU error and analysis tools are overly
aggressive by default.

Good luck.
Randall

-- Brief whoami:
 NonStop developer since approximately
211288444200000000
 UNIX developer since approximately 421664400
-- In my real life, I talk too much.

Thank you I tried to disable all of them, but they all
remain.
For
example the variable 'active_nr' is actually never
declared.
That's
so strange.
Hope to
solve this all soon. I'm freezed...

It is very likely in ECLIPSE either in workstation or
project
settings relating to error parsers (turn everything off).
It
still may be an error parser issue. One key thing... do
not
use -Wall.
There are also settings about what to do in some error
conditions configured in ECLIPSE. -Wall could be probably
triggering a response from one of the error parsers. But
the
Semantic Error type is not normally from the compiler;
rather,
it is from ECLIPSE CDT pre- scanning the code. Anyway,
check
out other -W settings to disable all warnings as a start.
If
you are building in Cygwin or Mingw, you probably can
ignore
the ECLIPSE errors, especially if git actually built. If
you
are trying to mix a managed build and a non-managed build
in
the same project, you are going to be out of luck.

If I run a make inside the git working directory, this will
just
create binaries in the working directory. But in my
home/{myname}/bin/ I have found the following files:

git git-cvsserver gitk git-receive-pack git-shell git-
upload-
archive git-upload- pack

Maybe they are deployed by a make install I run
accidentally (I
think that's possible). How could I clean the effect of
this
accidental install?
If I don't
clean this install could I have problems in the future?

I haven't done a Windows build so I really can't help here.
Anyone
else able to chime in?

I'm on debian stretch.

Unless /home/{yourname}/bin is on your PATH, the make install
should
not cause a problem and cleaning up from it probably is fine. I'm
surprised there is no /home/{yourname}/share also because make
install
will move man pages into it - although you might not have all of
the
man pages installed (that is another topic and make target - my
platform does not have a port of the Asciidoctor tool, so I can't
build git man pages, so I use quick-install-man, which depends on
having a clone of the man page repository that the really awesome
git
team creates). It might be helpful to specify some of the option
defines described in the Makefile so that the install goes to the
proper place (like /usr/local). Run 'uname -s' to figure out
which
system type config.mak.uname is going to use, and go from there.

Good luck.

Randall

-- Brief whoami:
 NonStop developer since approximately 211288444200000000
 UNIX developer since approximately 421664400
-- In my real life, I talk too much.

I found in the Makefile:

...

prefix = $(HOME)
bindir = $(prefix)/bin <--- delete the whole home/fabio/bin mandir
=
$(prefix)/share/man  <--- delete infodir = $(prefix)/share/info <

--- delete

gitexecdir = libexec/git-core <---- delete mergetoolsdir =
$(gitexecdir)/mergetools <---not present sharedir = $(prefix)/share
<---
delete gitwebdir = $(sharedir)/gitweb <--- delete perllibdir =
$(sharedir)/perl5
<--- delete localedir = $(sharedir)/locale <--- delete template_dir
= share/git-
core/templates <--- delete htmldir = $(prefix)/share/doc/git-doc <-
-- not
present
ETC_GITCONFIG = $(sysconfdir)/gitconfig   <--- in my /etc there's
no
gitconfig
ETC_GITATTRIBUTES = $(sysconfdir)/gitattributes <--- in my /etc
there's no
gitattributes lib = lib # DESTDIR = pathsep = :

bindir_relative = $(patsubst $(prefix)/%,%,$(bindir))
mandir_relative =
$(patsubst $(prefix)/%,%,$(mandir)) infodir_relative = $(patsubst
$(prefix)/%,%,$(infodir)) gitexecdir_relative = $(patsubst
$(prefix)/%,%,$(gitexecdir)) localedir_relative = $(patsubst
$(prefix)/%,%,$(localedir)) htmldir_relative = $(patsubst
$(prefix)/%,%,$(htmldir)) perllibdir_relative = $(patsubst
$(prefix)/%,%,$(perllibdir))

...

so by deleting all this stuff should be everything good, shouldn't
it?
Please let me know if there should be anything else to know.

Your path, being
PATH=~/bin:/home/{myname}/bin:/usr/local/bin:/usr/bin:/bin:/usr/local
/g
ames:/usr/games:/usr/sbin:/sbin
puts your own bin in front of where the system-defined git would be
located. So yes, the new install will interfere. As long as you
remove the git install from ~/bin and /home/{myname}/bin (are these
not the same?), you should go back to using the system's git.

Thank you Randall, I wonder if it's due to that install that I have
these first wo entries in my PATH environment variable. If I create a
new user I don't have any entries pointing at home/{username}. Maybe
it's impossible to know (I've found nothing related in the Makefile).
Does install command set the environment variables with the specified
install paths?
Thank you.
Fabio.