threads / discuss / 23519

Compilation pb of git-1.7.0.5

Subject: Compilation pb of git-1.7.0.5

## tl;dr

5 messages between Apr 19, 2010 and Apr 19, 2010.

replies: 4people: 3as markdown or json

Yves Caniou· Apr 19, 2010, 05:59 UTC · lore
Dear all,

I tried to install git on a Quad-Core AMD Opteron(tm) Processor 8356, with the version 4.1.2 of gcc (Red Hat 4.1.2-14).

After the ./configure --prefix=$HOME/git, the make all gives me
- some warnings like
"fast-import.c: 2622: Warning: 2570, Value assigned to enumeration 
object "type" is different type."
- some errors like
"archive.c: 223: Serious: 4470, Initialization value must be address constant 
expression."
This error appears also on lines 309, 311, etc.
Thank you for any help.
.Yves.
Sverre Rabbelier· Apr 19, 2010, 06:26 UTC · re: Yves Caniou · lore

Re: Compilation pb of git-1.7.0.5

Heya,
On Mon, Apr 19, 2010 at 07:59, Yves Caniou <yves.caniou@ens-lyon.fr> wrote:
> After the ./configure --prefix=$HOME/git, the make all gives me

Which revision are you trying to compile? Also, it's probably more helpful to just post the result of 'make all' verbatim, rather than snippets.

-- 
Cheers,

Sverre Rabbelier
Yves Caniou· Apr 19, 2010, 07:32 UTC · re: Sverre Rabbelier · lore

Re: Compilation pb of git-1.7.0.5

Le Monday 19 April 2010 08:26:59 Sverre Rabbelier, vous avez écrit :
Show 6 quoted lines
> Heya,
>
> On Mon, Apr 19, 2010 at 07:59, Yves Caniou <yves.caniou@ens-lyon.fr> wrote:
> > After the ./configure --prefix=$HOME/git, the make all gives me
>
> Which revision are you trying to compile?
I should have recall this in the mail, instead of just let it in the subject: 1.7.0.5
> Also, it's probably more 
> helpful to just post the result of 'make all' verbatim, rather than
> snippets.

Ok. Thanks to wereHamster on IRC, it appears that the compiler that was used for compilation is the Hitachi Cc version 6.2 and not gcc, because ./configure detects cc and uses cc instead of gcc.

Here is the output of the make all, made after the ./configure [...]
--------
$>make all
    * new build flags or prefix
    CC fast-import.o
cc: Warning: 100, Unknown option, "-g" option is ignored.
fast-import.c: 2622: Warning: 2570, Value assigned to enumeration object "type" is different type.
fast-import.c: 1776: Warning: 2570, Value assigned to enumeration object "type" is different type.
fast-import.c: 2213: Warning: 2570, Value assigned to enumeration object "type" is different type.
fast-import.c: 2346: Warning: 2570, Value assigned to enumeration object "type" is different type.
    CC abspath.o
cc: Warning: 100, Unknown option, "-g" option is ignored.
    CC advice.o
cc: Warning: 100, Unknown option, "-g" option is ignored.
    CC alias.o
cc: Warning: 100, Unknown option, "-g" option is ignored.
    CC alloc.o
cc: Warning: 100, Unknown option, "-g" option is ignored.
    CC archive.o
cc: Warning: 100, Unknown option, "-g" option is ignored.
archive.c: 223: Serious: 4470, Initialization value must be address constant expression.
archive.c: 309: Serious: 4470, Initialization value must be address constant expression.
archive.c: 311: Serious: 4470, Initialization value must be address constant expression.
archive.c: 313: Serious: 4470, Initialization value must be address constant expression.
archive.c: 315: Serious: 4470, Initialization value must be address constant expression.
archive.c: 316: Serious: 4470, Initialization value must be address constant expression.
archive.c: 317: Serious: 4470, Initialization value must be address constant expression.
archive.c: 318: Serious: 4470, Initialization value must be address constant expression.
archive.c: 319: Serious: 4470, Initialization value must be address constant expression.
archive.c: 320: Serious: 4470, Initialization value must be address constant expression.
archive.c: 321: Serious: 4470, Initialization value must be address constant expression.
archive.c: 322: Serious: 4470, Initialization value must be address constant expression.
archive.c: 323: Serious: 4470, Initialization value must be address constant expression.
archive.c: 324: Serious: 4470, Initialization value must be address constant expression.
archive.c: 325: Serious: 4470, Initialization value must be address constant expression.
archive.c: 326: Serious: 4470, Initialization value must be address constant expression.
archive.c: 329: Serious: 4470, Initialization value must be address constant expression.
archive.c: 332: Serious: 4470, Initialization value must be address constant expression.
archive.c: 334: Serious: 4470, Initialization value must be address constant expression.
make: *** [archive.o] Error 1
------------

Note that the direct compilation with the following command calls gcc, worked and the installation was successful. $>make prefix=$HOME/git install

Thank you.
.Yves.
Michael J Gruber· Apr 19, 2010, 08:37 UTC · re: Sverre Rabbelier · lore

Re: Compilation pb of git-1.7.0.5

Sverre Rabbelier venit, vidit, dixit 19.04.2010 08:26:
Show 8 quoted lines
> Heya,
> 
> On Mon, Apr 19, 2010 at 07:59, Yves Caniou <yves.caniou@ens-lyon.fr> wrote:
>> After the ./configure --prefix=$HOME/git, the make all gives me
> 
> Which revision are you trying to compile? Also, it's probably more
> helpful to just post the result of 'make all' verbatim, rather than
> snippets.

...and try to use make directly rather than configure, which isn't maintained that well.

I wonder whether we should hide configure somehow. If you see a Makefile and configure and don't know the project, the natural impulse is to use configure before make.

Michael
Yves Caniou· Apr 19, 2010, 08:50 UTC · re: Michael J Gruber · lore

Re: Compilation pb of git-1.7.0.5

Le Monday 19 April 2010 10:37:18 Michael J Gruber, vous avez écrit :
> Sverre Rabbelier venit, vidit, dixit 19.04.2010 08:26:
> > Heya,
> >
> > On Mon, Apr 19, 2010 at 07:59, Yves Caniou <yves.caniou@ens-lyon.fr> 
wrote:
Show 8 quoted lines
> >> After the ./configure --prefix=$HOME/git, the make all gives me
> >
> > Which revision are you trying to compile? Also, it's probably more
> > helpful to just post the result of 'make all' verbatim, rather than
> > snippets.
>
> ...and try to use make directly rather than configure, which isn't
> maintained that well.

That's what I did, but maybe you didn't saw my mail. It works fine, because Cc doesn't overide gcc. So I can install. I don't know if you want to look at the errors or not, but if not, maybe adding some info in known issues?

Show 5 quoted lines
> I wonder whether we should hide configure somehow. If you see a Makefile
> and configure and don't know the project, the natural impulse is to use
> configure before make.
>
> Michael

Indeed, the natural reflex is to make a ./configure --help to have the options, and use ./configure. I saw the first lines in the INSTALL file, describing "make prefix=" but just made like I'm used to.

Thx.
.Yves.

← back to recent threads