{"thread":{"id":"23519","subject":"Compilation pb of git-1.7.0.5","startedAt":"2010-04-19T05:59:14Z","lastAt":"2010-04-19T08:50:33Z","messageCount":5,"participants":["Yves Caniou","Sverre Rabbelier","Michael J Gruber"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"139864","messageId":"201004190759.15032.yves.caniou@ens-lyon.fr","threadId":"23519","inReplyTo":null,"subject":"Compilation pb of git-1.7.0.5","fromName":"Yves Caniou","fromEmail":"yves.caniou@ens-lyon.fr","sentAt":"2010-04-19T05:59:14Z","receivedAt":"2010-04-19T05:59:14Z","isPatch":false,"sender":{"key":"yves.caniou@ens-lyon.fr","avatar":null},"body":"Dear all,\n\nI tried to install git on a Quad-Core AMD Opteron(tm) Processor 8356, with the \nversion 4.1.2 of gcc (Red Hat 4.1.2-14).\n\nAfter the ./configure --prefix=$HOME/git, the make all gives me\n\n- some warnings like\n\"fast-import.c: 2622: Warning: 2570, Value assigned to enumeration \nobject \"type\" is different type.\"\n\n- some errors like\n\"archive.c: 223: Serious: 4470, Initialization value must be address constant \nexpression.\"\nThis error appears also on lines 309, 311, etc.\n\nThank you for any help.\n\n.Yves.\n"},{"id":"139865","messageId":"i2kfabb9a1e1004182326w32b1ce9ak2ada640ce30cc945@mail.gmail.com","threadId":"23519","inReplyTo":"201004190759.15032.yves.caniou@ens-lyon.fr","subject":"Re: Compilation pb of git-1.7.0.5","fromName":"Sverre Rabbelier","fromEmail":"srabbelier@gmail.com","sentAt":"2010-04-19T06:26:59Z","receivedAt":"2010-04-19T06:26:59Z","isPatch":false,"sender":{"key":"srabbelier@gmail.com","avatar":"https://avatars.githubusercontent.com/u/3098?v=4"},"body":"Heya,\n\nOn Mon, Apr 19, 2010 at 07:59, Yves Caniou wrote:\n> After the ./configure --prefix=$HOME/git, the make all gives me\n\nWhich revision are you trying to compile? Also, it's probably more\nhelpful to just post the result of 'make all' verbatim, rather than\nsnippets.\n\n-- \nCheers,\n\nSverre Rabbelier\n"},{"id":"139871","messageId":"201004190932.26445.yves.caniou@ens-lyon.fr","threadId":"23519","inReplyTo":"i2kfabb9a1e1004182326w32b1ce9ak2ada640ce30cc945@mail.gmail.com","subject":"Re: Compilation pb of git-1.7.0.5","fromName":"Yves Caniou","fromEmail":"yves.caniou@ens-lyon.fr","sentAt":"2010-04-19T07:32:26Z","receivedAt":"2010-04-19T07:32:26Z","isPatch":false,"sender":{"key":"yves.caniou@ens-lyon.fr","avatar":null},"body":"Le Monday 19 April 2010 08:26:59 Sverre Rabbelier, vous avez écrit :\n> Heya,\n>\n> On Mon, Apr 19, 2010 at 07:59, Yves Caniou wrote:\n> > After the ./configure --prefix=$HOME/git, the make all gives me\n>\n> Which revision are you trying to compile?\n\nI should have recall this in the mail, instead of just let it in the subject: 1.7.0.5\n\n> Also, it's probably more \n> helpful to just post the result of 'make all' verbatim, rather than\n> snippets.\n\nOk. 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, \nbecause ./configure detects cc and uses cc instead of gcc.\n\nHere is the output of the make all, made after the ./configure [...]\n\n--------\n$>make all\n * new build flags or prefix\n CC fast-import.o\ncc: Warning: 100, Unknown option, \"-g\" option is ignored.\nfast-import.c: 2622: Warning: 2570, Value assigned to enumeration object \"type\" is different type.\nfast-import.c: 1776: Warning: 2570, Value assigned to enumeration object \"type\" is different type.\nfast-import.c: 2213: Warning: 2570, Value assigned to enumeration object \"type\" is different type.\nfast-import.c: 2346: Warning: 2570, Value assigned to enumeration object \"type\" is different type.\n CC abspath.o\ncc: Warning: 100, Unknown option, \"-g\" option is ignored.\n CC advice.o\ncc: Warning: 100, Unknown option, \"-g\" option is ignored.\n CC alias.o\ncc: Warning: 100, Unknown option, \"-g\" option is ignored.\n CC alloc.o\ncc: Warning: 100, Unknown option, \"-g\" option is ignored.\n CC archive.o\ncc: Warning: 100, Unknown option, \"-g\" option is ignored.\narchive.c: 223: Serious: 4470, Initialization value must be address constant expression.\narchive.c: 309: Serious: 4470, Initialization value must be address constant expression.\narchive.c: 311: Serious: 4470, Initialization value must be address constant expression.\narchive.c: 313: Serious: 4470, Initialization value must be address constant expression.\narchive.c: 315: Serious: 4470, Initialization value must be address constant expression.\narchive.c: 316: Serious: 4470, Initialization value must be address constant expression.\narchive.c: 317: Serious: 4470, Initialization value must be address constant expression.\narchive.c: 318: Serious: 4470, Initialization value must be address constant expression.\narchive.c: 319: Serious: 4470, Initialization value must be address constant expression.\narchive.c: 320: Serious: 4470, Initialization value must be address constant expression.\narchive.c: 321: Serious: 4470, Initialization value must be address constant expression.\narchive.c: 322: Serious: 4470, Initialization value must be address constant expression.\narchive.c: 323: Serious: 4470, Initialization value must be address constant expression.\narchive.c: 324: Serious: 4470, Initialization value must be address constant expression.\narchive.c: 325: Serious: 4470, Initialization value must be address constant expression.\narchive.c: 326: Serious: 4470, Initialization value must be address constant expression.\narchive.c: 329: Serious: 4470, Initialization value must be address constant expression.\narchive.c: 332: Serious: 4470, Initialization value must be address constant expression.\narchive.c: 334: Serious: 4470, Initialization value must be address constant expression.\nmake: *** [archive.o] Error 1\n------------\n\nNote that the direct compilation with the following command calls gcc, worked and the installation was successful.\n$>make prefix=$HOME/git install\n\nThank you.\n\n.Yves.\n"},{"id":"139880","messageId":"4BCC163E.3050808@drmicha.warpmail.net","threadId":"23519","inReplyTo":"i2kfabb9a1e1004182326w32b1ce9ak2ada640ce30cc945@mail.gmail.com","subject":"Re: Compilation pb of git-1.7.0.5","fromName":"Michael J Gruber","fromEmail":"git@drmicha.warpmail.net","sentAt":"2010-04-19T08:37:18Z","receivedAt":"2010-04-19T08:37:18Z","isPatch":false,"sender":{"key":"git@grubix.eu","avatar":"https://avatars.githubusercontent.com/u/233215?v=4"},"body":"Sverre Rabbelier venit, vidit, dixit 19.04.2010 08:26:\n> Heya,\n> \n> On Mon, Apr 19, 2010 at 07:59, Yves Caniou wrote:\n>> After the ./configure --prefix=$HOME/git, the make all gives me\n> \n> Which revision are you trying to compile? Also, it's probably more\n> helpful to just post the result of 'make all' verbatim, rather than\n> snippets.\n\n...and try to use make directly rather than configure, which isn't\nmaintained that well.\n\nI wonder whether we should hide configure somehow. If you see a Makefile\nand configure and don't know the project, the natural impulse is to use\nconfigure before make.\n\nMichael\n"},{"id":"139884","messageId":"201004191050.33790.yves.caniou@ens-lyon.fr","threadId":"23519","inReplyTo":"4BCC163E.3050808@drmicha.warpmail.net","subject":"Re: Compilation pb of git-1.7.0.5","fromName":"Yves Caniou","fromEmail":"yves.caniou@ens-lyon.fr","sentAt":"2010-04-19T08:50:33Z","receivedAt":"2010-04-19T08:50:33Z","isPatch":false,"sender":{"key":"yves.caniou@ens-lyon.fr","avatar":null},"body":"Le Monday 19 April 2010 10:37:18 Michael J Gruber, vous avez écrit :\n> Sverre Rabbelier venit, vidit, dixit 19.04.2010 08:26:\n> > Heya,\n> >\n> > On Mon, Apr 19, 2010 at 07:59, Yves Caniou \nwrote:\n> >> After the ./configure --prefix=$HOME/git, the make all gives me\n> >\n> > Which revision are you trying to compile? Also, it's probably more\n> > helpful to just post the result of 'make all' verbatim, rather than\n> > snippets.\n>\n> ...and try to use make directly rather than configure, which isn't\n> maintained that well.\n\nThat's what I did, but maybe you didn't saw my mail. It works fine, because Cc \ndoesn't overide gcc. So I can install. I don't know if you want to look at \nthe errors or not, but if not, maybe adding some info in known issues?\n\n> I wonder whether we should hide configure somehow. If you see a Makefile\n> and configure and don't know the project, the natural impulse is to use\n> configure before make.\n>\n> Michael\n\nIndeed, the natural reflex is to make a ./configure --help to have the \noptions, and use ./configure. I saw the first lines in the INSTALL file, \ndescribing \"make prefix=\" but just made like I'm used to.\n\nThx.\n\n.Yves.\n"}]}