{"thread":{"id":"20873","subject":"[PATCH] Add more instructions about how to install git.","startedAt":"2009-09-08T05:11:26Z","lastAt":"2009-09-08T19:41:21Z","messageCount":11,"participants":["Thiago Farina","Alex Riesen","Matthieu Moy","Michael J Gruber","Erik Faye-Lund","Johannes Sixt","Mikael Magnusson","Brian Gernhardt"],"isPatch":true,"patchVersion":1,"patchTotal":null},"messages":[{"id":"122663","messageId":"1252386686-15689-1-git-send-email-tfransosi@gmail.com","threadId":"20873","inReplyTo":null,"subject":"[PATCH] Add more instructions about how to install git.","fromName":"Thiago Farina","fromEmail":"tfransosi@gmail.com","sentAt":"2009-09-08T05:11:26Z","receivedAt":"2009-09-08T05:11:26Z","isPatch":true,"sender":{"key":"tfransosi@gmail.com","avatar":"https://avatars.githubusercontent.com/u/970071?v=4"},"body":"Signed-off-by: Thiago Farina <tfransosi@gmail.com>\n---\n INSTALL |    9 +++++++++\n 1 files changed, 9 insertions(+), 0 deletions(-)\n\ndiff --git a/INSTALL b/INSTALL\nindex ae7f750..67abfc7 100644\n--- a/INSTALL\n+++ b/INSTALL\n@@ -1,6 +1,15 @@\n \n \t\tGit installation\n \n+To install git follow these 4 steps inside your git directory:\n+$ autoconf      # Generates the configure file from configure.ac\n+$ ./configure   # Configures everything needed to build git\n+$ make all      # Compiles git based in the Makefile\n+$ make install  # Installs git in your own ~/bin directory\n+\n+If you don't have autoconf installed, you can do this by:\n+$ sudo apt-get install autoconf\n+\n Normally you can just do \"make\" followed by \"make install\", and that\n will install the git programs in your own ~/bin/ directory.  If you want\n to do a global install, you can do\n-- \n1.6.0.4\n"},{"id":"122664","messageId":"81b0412b0909072244k21a4ddf6vdc38d9f713a4a084@mail.gmail.com","threadId":"20873","inReplyTo":"1252386686-15689-1-git-send-email-tfransosi@gmail.com","subject":"Re: [PATCH] Add more instructions about how to install git.","fromName":"Alex Riesen","fromEmail":"raa.lkml@gmail.com","sentAt":"2009-09-08T05:44:51Z","receivedAt":"2009-09-08T05:44:51Z","isPatch":true,"sender":{"key":"raa.lkml@gmail.com","avatar":"https://avatars.githubusercontent.com/u/324101?v=4"},"body":"On Tue, Sep 8, 2009 at 07:11, Thiago Farina<tfransosi@gmail.com> wrote:\n> Signed-off-by: Thiago Farina <tfransosi@gmail.com>\n> ---\n>  INSTALL |    9 +++++++++\n>  1 files changed, 9 insertions(+), 0 deletions(-)\n>\n> diff --git a/INSTALL b/INSTALL\n> index ae7f750..67abfc7 100644\n> --- a/INSTALL\n> +++ b/INSTALL\n> @@ -1,6 +1,15 @@\n>\n>                Git installation\n>\n> +To install git follow these 4 steps inside your git directory:\n> +$ autoconf      # Generates the configure file from configure.ac\n> +$ ./configure   # Configures everything needed to build git\n> +$ make all      # Compiles git based in the Makefile\n> +$ make install  # Installs git in your own ~/bin directory\n> +\n> +If you don't have autoconf installed, you can do this by:\n> +$ sudo apt-get install autoconf\n\n... if you're on a Debian-derived system. The other half of the\nworld, which is RedHat-derived, uses RPM. And there are\nother package management tools. Maybe that was a reason\nwhy the instructions weren't included before.\n"},{"id":"122665","messageId":"vpqhbvekldk.fsf@bauges.imag.fr","threadId":"20873","inReplyTo":"81b0412b0909072244k21a4ddf6vdc38d9f713a4a084@mail.gmail.com","subject":"Re: [PATCH] Add more instructions about how to install git.","fromName":"Matthieu Moy","fromEmail":"matthieu.moy@grenoble-inp.fr","sentAt":"2009-09-08T06:20:55Z","receivedAt":"2009-09-08T06:20:55Z","isPatch":true,"sender":{"key":"matthieu.moy@grenoble-inp.fr","avatar":"https://gravatar.com/avatar/72c8a2705971a25dfaff23cece15130d405685845d911aedd5667ace277f3fc5?d=mp&s=160"},"body":"Alex Riesen <raa.lkml@gmail.com> writes:\n\n> On Tue, Sep 8, 2009 at 07:11, Thiago Farina<tfransosi@gmail.com> wrote:\n>> Signed-off-by: Thiago Farina <tfransosi@gmail.com>\n>> ---\n>>  INSTALL |    9 +++++++++\n>>  1 files changed, 9 insertions(+), 0 deletions(-)\n>>\n>> diff --git a/INSTALL b/INSTALL\n>> index ae7f750..67abfc7 100644\n>> --- a/INSTALL\n>> +++ b/INSTALL\n>> @@ -1,6 +1,15 @@\n>>\n>>                Git installation\n>>\n>> +To install git follow these 4 steps inside your git directory:\n>> +$ autoconf      # Generates the configure file from configure.ac\n>> +$ ./configure   # Configures everything needed to build git\n>> +$ make all      # Compiles git based in the Makefile\n>> +$ make install  # Installs git in your own ~/bin directory\n\nYour commit message doesn't say what's wrong with\n\n| Alternatively you can use autoconf generated ./configure script to\n| set up install paths (via config.mak.autogen), so you can write\n| instead\n| \n|         $ make configure ;# as yourself\n|         $ ./configure --prefix=/usr ;# as yourself\n|         $ make all doc ;# as yourself\n|         # make install install-doc install-html;# as root\n\nwhich is already in INSTALL a few lines after what your patch adds.\n\n>> +If you don't have autoconf installed, you can do this by:\n>> +$ sudo apt-get install autoconf\n>\n> ... if you're on a Debian-derived system. \n\nand if you have sudo configured.\n\nBTW, apt-get is anyway somehow deprecaded, you should\ns/apt-get/aptitude/.\n\n-- \nMatthieu Moy\nhttp://www-verimag.imag.fr/~moy/\n"},{"id":"122683","messageId":"4AA60E41.5050702@drmicha.warpmail.net","threadId":"20873","inReplyTo":"vpqhbvekldk.fsf@bauges.imag.fr","subject":"Re: [PATCH] Add more instructions about how to install git.","fromName":"Michael J Gruber","fromEmail":"git@drmicha.warpmail.net","sentAt":"2009-09-08T07:56:49Z","receivedAt":"2009-09-08T07:56:49Z","isPatch":true,"sender":{"key":"git@grubix.eu","avatar":"https://avatars.githubusercontent.com/u/233215?v=4"},"body":"Matthieu Moy venit, vidit, dixit 08.09.2009 08:20:\n> Alex Riesen <raa.lkml@gmail.com> writes:\n> \n>> On Tue, Sep 8, 2009 at 07:11, Thiago Farina<tfransosi@gmail.com> wrote:\n>>> Signed-off-by: Thiago Farina <tfransosi@gmail.com>\n>>> ---\n>>>  INSTALL |    9 +++++++++\n>>>  1 files changed, 9 insertions(+), 0 deletions(-)\n>>>\n>>> diff --git a/INSTALL b/INSTALL\n>>> index ae7f750..67abfc7 100644\n>>> --- a/INSTALL\n>>> +++ b/INSTALL\n>>> @@ -1,6 +1,15 @@\n>>>\n>>>                Git installation\n>>>\n>>> +To install git follow these 4 steps inside your git directory:\n>>> +$ autoconf      # Generates the configure file from configure.ac\n>>> +$ ./configure   # Configures everything needed to build git\n>>> +$ make all      # Compiles git based in the Makefile\n>>> +$ make install  # Installs git in your own ~/bin directory\n> \n> Your commit message doesn't say what's wrong with\n> \n> | Alternatively you can use autoconf generated ./configure script to\n> | set up install paths (via config.mak.autogen), so you can write\n> | instead\n> | \n> |         $ make configure ;# as yourself\n> |         $ ./configure --prefix=/usr ;# as yourself\n> |         $ make all doc ;# as yourself\n> |         # make install install-doc install-html;# as root\n> \n> which is already in INSTALL a few lines after what your patch adds.\n\n... especially since that really is a second class alternative these\ndays, with using the shipped Makefile being the preferred way - just as\nthe current documentation states.\n\n> \n>>> +If you don't have autoconf installed, you can do this by:\n>>> +$ sudo apt-get install autoconf\n>>\n>> ... if you're on a Debian-derived system. \n> \n> and if you have sudo configured.\n> \n> BTW, apt-get is anyway somehow deprecaded, you should\n> s/apt-get/aptitude/.\n> \n"},{"id":"122703","messageId":"a4c8a6d00909080724q1c792f6bs641ea9d000d08b5a@mail.gmail.com","threadId":"20873","inReplyTo":"vpqhbvekldk.fsf@bauges.imag.fr","subject":"Re: [PATCH] Add more instructions about how to install git.","fromName":"Thiago Farina","fromEmail":"tfransosi@gmail.com","sentAt":"2009-09-08T14:24:37Z","receivedAt":"2009-09-08T14:24:37Z","isPatch":true,"sender":{"key":"tfransosi@gmail.com","avatar":"https://avatars.githubusercontent.com/u/970071?v=4"},"body":"On Tue, Sep 8, 2009 at 3:20 AM, Matthieu\nMoy<Matthieu.Moy@grenoble-inp.fr> wrote:\n> Your commit message doesn't say what's wrong with\n>\n> | Alternatively you can use autoconf generated ./configure script to\n> | set up install paths (via config.mak.autogen), so you can write\n> | instead\n> |\n> |         $ make configure ;# as yourself\n> |         $ ./configure --prefix=/usr ;# as yourself\n> |         $ make all doc ;# as yourself\n> |         # make install install-doc install-html;# as root\n>\n> which is already in INSTALL a few lines after what your patch adds.\n\nI tried to being more explicit about what the new users has to do. The\nfirst instruction that the text says is: \"Normaly you can just do\n\"make\"\".\nBut the new user, cloning git won't have a configure file, so he can't\njust do \"make\".\n\nAnd then, the text says: \"so you can write instead\". This brings me to\none alternative (not what I really should do), when in fact it should\nbe (I guess) the first instructions that new users need to follow.\n"},{"id":"122704","messageId":"40aa078e0909080737x701eb708t766edb024dc30c37@mail.gmail.com","threadId":"20873","inReplyTo":"a4c8a6d00909080724q1c792f6bs641ea9d000d08b5a@mail.gmail.com","subject":"Re: [PATCH] Add more instructions about how to install git.","fromName":"Erik Faye-Lund","fromEmail":"kusmabite@googlemail.com","sentAt":"2009-09-08T14:37:28Z","receivedAt":"2009-09-08T14:37:28Z","isPatch":true,"sender":{"key":"kusmabite@gmail.com","avatar":"https://avatars.githubusercontent.com/u/47073?v=4"},"body":"On Tue, Sep 8, 2009 at 4:24 PM, Thiago Farina<tfransosi@gmail.com> wrote:\n> I tried to being more explicit about what the new users has to do. The\n> first instruction that the text says is: \"Normaly you can just do\n> \"make\"\".\n> But the new user, cloning git won't have a configure file, so he can't\n> just do \"make\".\n\nI think you are confused. There's a default Makefile there, so a\nnormal user CAN just call \"make\". What a new user can't do, is to call\n\"./configure\" without generating the configure-script first. There are\nalready instructions on how to do this.\n\n-- \nErik \"kusma\" Faye-Lund\nkusmabite@gmail.com\n(+47) 986 59 656\n"},{"id":"122705","messageId":"4AA66C54.4060101@viscovery.net","threadId":"20873","inReplyTo":"a4c8a6d00909080724q1c792f6bs641ea9d000d08b5a@mail.gmail.com","subject":"Re: [PATCH] Add more instructions about how to install git.","fromName":"Johannes Sixt","fromEmail":"j.sixt@viscovery.net","sentAt":"2009-09-08T14:38:12Z","receivedAt":"2009-09-08T14:38:12Z","isPatch":true,"sender":{"key":"j6t@kdbg.org","avatar":"https://avatars.githubusercontent.com/u/14810926?v=4"},"body":"Thiago Farina schrieb:\n> I tried to being more explicit about what the new users has to do. The\n> first instruction that the text says is: \"Normaly you can just do\n> \"make\"\".\n> But the new user, cloning git won't have a configure file, so he can't\n> just do \"make\".\n> \n> And then, the text says: \"so you can write instead\". This brings me to\n> one alternative (not what I really should do), when in fact it should\n> be (I guess) the first instructions that new users need to follow.\n\nThen guessed wrong. You really only have to say \"make\". The use of\nautoconf and ./configure is purely optional and not necessary.\n\n-- Hannes\n"},{"id":"122706","messageId":"a4c8a6d00909080752p5b663fc8r8bf1c60023ef39b4@mail.gmail.com","threadId":"20873","inReplyTo":"4AA66C54.4060101@viscovery.net","subject":"Re: [PATCH] Add more instructions about how to install git.","fromName":"Thiago Farina","fromEmail":"tfransosi@gmail.com","sentAt":"2009-09-08T14:52:46Z","receivedAt":"2009-09-08T14:52:46Z","isPatch":true,"sender":{"key":"tfransosi@gmail.com","avatar":"https://avatars.githubusercontent.com/u/970071?v=4"},"body":"On Tue, Sep 8, 2009 at 10:38 AM, Johannes Sixt<j.sixt@viscovery.net> wrote:\n> Thiago Farina schrieb:\n>> I tried to being more explicit about what the new users has to do. The\n>> first instruction that the text says is: \"Normaly you can just do\n>> \"make\"\".\n>> But the new user, cloning git won't have a configure file, so he can't\n>> just do \"make\".\n>>\n>> And then, the text says: \"so you can write instead\". This brings me to\n>> one alternative (not what I really should do), when in fact it should\n>> be (I guess) the first instructions that new users need to follow.\n>\n> Then guessed wrong. You really only have to say \"make\". The use of\n> autoconf and ./configure is purely optional and not necessary.\nI don't think so.\nRunning only \"make\".\n$ make\nGIT_VERSION = 1.6.5.rc0\n    * new build flags or prefix\n    CC fast-import.o\nIn file included from builtin.h:4,\n                 from fast-import.c:143:\ngit-compat-util.h:129:25: error: openssl/ssl.h: No such file or directory\ngit-compat-util.h:130:25: error: openssl/err.h: No such file or directory\nIn file included from builtin.h:6,\n                 from fast-import.c:143:\ncache.h:8:21: error: openssl/sha.h: No such file or directory\nIn file included from fast-import.c:152:\ncsum-file.h:10: error: expected specifier-qualifier-list before ‘SHA_CTX’\nfast-import.c: In function ‘create_index’:\nfast-import.c:850: error: ‘SHA_CTX’ undeclared (first use in this function)\nfast-import.c:850: error: (Each undeclared identifier is reported only once\nfast-import.c:850: error: for each function it appears in.)\nfast-import.c:850: error: expected ‘;’ before ‘ctx’\nfast-import.c:886: warning: implicit declaration of function ‘SHA1_Init’\nfast-import.c:886: error: ‘ctx’ undeclared (first use in this function)\nfast-import.c:891: warning: implicit declaration of function ‘SHA1_Update’\nfast-import.c:896: warning: implicit declaration of function ‘SHA1_Final’\nfast-import.c: In function ‘store_object’:\nfast-import.c:1035: error: ‘SHA_CTX’ undeclared (first use in this function)\nfast-import.c:1035: error: expected ‘;’ before ‘c’\nfast-import.c:1040: error: ‘c’ undeclared (first use in this function)\nfast-import.c: In function ‘validate_raw_date’:\nfast-import.c:1750: warning: ignoring return value of ‘strtoul’,\ndeclared with attribute warn_unused_result\nfast-import.c:1758: warning: ignoring return value of ‘strtoul’,\ndeclared with attribute warn_unused_result\nmake: *** [fast-import.o] Error 1\n\nRunning configure and then make\n$ make configure\nGIT_VERSION = 1.6.5.rc0.dirty\n    GEN configure\n$ make\n    CC fast-import.o\nIn file included from builtin.h:4,\n                 from fast-import.c:143:\ngit-compat-util.h:129:25: error: openssl/ssl.h: No such file or directory\ngit-compat-util.h:130:25: error: openssl/err.h: No such file or directory\nIn file included from builtin.h:6,\n                 from fast-import.c:143:\ncache.h:8:21: error: openssl/sha.h: No such file or directory\nIn file included from fast-import.c:152:\ncsum-file.h:10: error: expected specifier-qualifier-list before ‘SHA_CTX’\nfast-import.c: In function ‘create_index’:\nfast-import.c:850: error: ‘SHA_CTX’ undeclared (first use in this function)\nfast-import.c:850: error: (Each undeclared identifier is reported only once\nfast-import.c:850: error: for each function it appears in.)\nfast-import.c:850: error: expected ‘;’ before ‘ctx’\nfast-import.c:886: warning: implicit declaration of function ‘SHA1_Init’\nfast-import.c:886: error: ‘ctx’ undeclared (first use in this function)\nfast-import.c:891: warning: implicit declaration of function ‘SHA1_Update’\nfast-import.c:896: warning: implicit declaration of function ‘SHA1_Final’\nfast-import.c: In function ‘store_object’:\nfast-import.c:1035: error: ‘SHA_CTX’ undeclared (first use in this function)\nfast-import.c:1035: error: expected ‘;’ before ‘c’\nfast-import.c:1040: error: ‘c’ undeclared (first use in this function)\nfast-import.c: In function ‘validate_raw_date’:\nfast-import.c:1750: warning: ignoring return value of ‘strtoul’,\ndeclared with attribute warn_unused_result\nfast-import.c:1758: warning: ignoring return value of ‘strtoul’,\ndeclared with attribute warn_unused_result\nmake: *** [fast-import.o] Error 1\n\nNow autconf, ./configure, make.\n$ autoconf\n$ ./configure\nconfigure: Setting lib to 'lib' (the default)\nconfigure: Will try -pthread then -lpthread to enable POSIX Threads.\nconfigure: CHECKS for site configuration\nconfigure: CHECKS for programs\nchecking for cc... cc\nchecking for C compiler default output file name... a.out\nchecking whether the C compiler works... yes\nchecking whether we are cross compiling... no\nchecking for suffix of executables...\nchecking for suffix of object files... o\nchecking whether we are using the GNU C compiler... yes\nchecking whether cc accepts -g... yes\nchecking for cc option to accept ISO C89... none needed\nchecking if linker supports -R... no\nchecking if linker supports -Wl,-rpath,... yes\nchecking for gar... no\nchecking for ar... ar\nchecking for gtar... no\nchecking for tar... tar\nchecking for asciidoc... asciidoc\nchecking for asciidoc version... asciidoc 8.2.7 > 7\nconfigure: CHECKS for libraries\nchecking for SHA1_Init in -lcrypto... no\nchecking for SHA1_Init in -lssl... no\nchecking for curl_global_init in -lcurl... yes\nchecking for XML_ParserCreate in -lexpat... yes\nchecking for iconv in -lc... yes\nchecking for deflateBound in -lz... yes\nchecking for socket in -lc... yes\nchecking for hstrerror in -lc... yes\nchecking for basename in -lc... yes\nconfigure: CHECKS for header files\nchecking how to run the C preprocessor... cc -E\nchecking for grep that handles long lines and -e... /bin/grep\nchecking for egrep... /bin/grep -E\nchecking for ANSI C header files... yes\nchecking for sys/types.h... yes\nchecking for sys/stat.h... yes\nchecking for stdlib.h... yes\nchecking for string.h... yes\nchecking for memory.h... yes\nchecking for strings.h... yes\nchecking for inttypes.h... yes\nchecking for stdint.h... yes\nchecking for unistd.h... yes\nchecking sys/select.h usability... yes\nchecking sys/select.h presence... yes\nchecking for sys/select.h... yes\nchecking for old iconv()... no\nconfigure: CHECKS for typedefs, structures, and compiler characteristics\nchecking for struct dirent.d_ino... yes\nchecking for struct dirent.d_type... yes\nchecking for struct sockaddr_storage... yes\nchecking for struct addrinfo... yes\nchecking for getaddrinfo... yes\nchecking for library containing getaddrinfo... none required\nchecking whether formatted IO functions support C99 size specifiers... yes\nchecking whether system succeeds to read fopen'ed directory... no\nchecking whether snprintf() and/or vsnprintf() return bogus value... no\nconfigure: CHECKS for library functions\nchecking libgen.h usability... yes\nchecking libgen.h presence... yes\nchecking for libgen.h... yes\nchecking for strcasestr... yes\nchecking for library containing strcasestr... none required\nchecking for memmem... yes\nchecking for library containing memmem... none required\nchecking for strlcpy... no\nchecking for uintmax_t... yes\nchecking for strtoumax... yes\nchecking for library containing strtoumax... none required\nchecking for setenv... yes\nchecking for library containing setenv... none required\nchecking for unsetenv... yes\nchecking for library containing unsetenv... none required\nchecking for mkdtemp... yes\nchecking for library containing mkdtemp... none required\nchecking for mkstemps... no\nchecking Checking for POSIX Threads with '-pthread'... yes\nconfigure: creating ./config.status\nconfig.status: error: cannot find input file: config.mak.in\n$ make\n\nNow it compiles everything.\n"},{"id":"122707","messageId":"237967ef0909080756g579f5359te7da19fded27596f@mail.gmail.com","threadId":"20873","inReplyTo":"a4c8a6d00909080752p5b663fc8r8bf1c60023ef39b4@mail.gmail.com","subject":"Re: [PATCH] Add more instructions about how to install git.","fromName":"Mikael Magnusson","fromEmail":"mikachu@gmail.com","sentAt":"2009-09-08T14:56:03Z","receivedAt":"2009-09-08T14:56:03Z","isPatch":true,"sender":{"key":"mikachu@gmail.com","avatar":null},"body":"2009/9/8 Thiago Farina <tfransosi@gmail.com>:\n> On Tue, Sep 8, 2009 at 10:38 AM, Johannes Sixt<j.sixt@viscovery.net> wrote:\n>> Thiago Farina schrieb:\n>>> I tried to being more explicit about what the new users has to do. The\n>>> first instruction that the text says is: \"Normaly you can just do\n>>> \"make\"\".\n>>> But the new user, cloning git won't have a configure file, so he can't\n>>> just do \"make\".\n>>>\n>>> And then, the text says: \"so you can write instead\". This brings me to\n>>> one alternative (not what I really should do), when in fact it should\n>>> be (I guess) the first instructions that new users need to follow.\n>>\n>> Then guessed wrong. You really only have to say \"make\". The use of\n>> autoconf and ./configure is purely optional and not necessary.\n> I don't think so.\n> Running only \"make\".\n> $ make\n> GIT_VERSION = 1.6.5.rc0\n>    * new build flags or prefix\n>    CC fast-import.o\n> In file included from builtin.h:4,\n>                 from fast-import.c:143:\n> git-compat-util.h:129:25: error: openssl/ssl.h: No such file or directory\n> git-compat-util.h:130:25: error: openssl/err.h: No such file or directory\n[snip]\n\nYou need to edit the Makefile if your system needs tweaks, there are tons\nof comments.\n\n> Running configure and then make\n> $ make configure\n> GIT_VERSION = 1.6.5.rc0.dirty\n>    GEN configure\n> $ make\n>    CC fast-import.o\n> In file included from builtin.h:4,\n>                 from fast-import.c:143:\n> git-compat-util.h:129:25: error: openssl/ssl.h: No such file or directory\n> git-compat-util.h:130:25: error: openssl/err.h: No such file or directory\n\nYou forgot to run configure.\n\n> Now autconf, ./configure, make.\n> $ autoconf\n> $ ./configure\n> configure: Setting lib to 'lib' (the default)\n> configure: Will try -pthread then -lpthread to enable POSIX Threads.\n> configure: CHECKS for site configuration\n> configure: CHECKS for programs\n[...]\n> checking for mkstemps... no\n> checking Checking for POSIX Threads with '-pthread'... yes\n> configure: creating ./config.status\n> config.status: error: cannot find input file: config.mak.in\n> $ make\n>\n> Now it compiles everything.\n\n-- \nMikael Magnusson\n"},{"id":"122708","messageId":"D79F79B1-A4F4-4AEA-9E3B-F0CF59019B88@gernhardtsoftware.com","threadId":"20873","inReplyTo":"a4c8a6d00909080752p5b663fc8r8bf1c60023ef39b4@mail.gmail.com","subject":"Re: [PATCH] Add more instructions about how to install git.","fromName":"Brian Gernhardt","fromEmail":"brian@gernhardtsoftware.com","sentAt":"2009-09-08T15:19:59Z","receivedAt":"2009-09-08T15:19:59Z","isPatch":true,"sender":{"key":"brian@gernhardtsoftware.com","avatar":"https://avatars.githubusercontent.com/u/133455?v=4"},"body":"\nOn Sep 8, 2009, at 10:52 AM, Thiago Farina wrote:\n\n> On Tue, Sep 8, 2009 at 10:38 AM, Johannes Sixt<j.sixt@viscovery.net>  \n> wrote:\n>> Then guessed wrong. You really only have to say \"make\". The use of\n>> autoconf and ./configure is purely optional and not necessary.\n> I don't think so.\n> Running only \"make\".\n> $ make\n> GIT_VERSION = 1.6.5.rc0\n>    * new build flags or prefix\n>    CC fast-import.o\n> In file included from builtin.h:4,\n>                 from fast-import.c:143:\n> git-compat-util.h:129:25: error: openssl/ssl.h: No such file or  \n> directory\n> git-compat-util.h:130:25: error: openssl/err.h: No such file or  \n> directory\n\nYou don't have OpenSSL, a perquisite mentioned in the INSTALL file at  \nline 55.  You can do the following:\n\nmake NO_OPENSSL=Yes\n\nor save the option so you don't have to retype it each time:\n\necho \"NO_OPENSSL=Yes\" > config.mak\nmake\n\nOr install OpenSSL or run the autoconf.\n\nThe Makefile tries it's best to be as smart as possible without being  \na configure script of it's own (see ll. 656-925), and it's highly  \ncommented at the beginning so that only a minimal knowledge of make is  \nrequired (ll. 4-198).  I suppose we could  note that the defines  \nshould be put in a config.mak file.\n\n> Running configure and then make\n> $ make configure\n> GIT_VERSION = 1.6.5.rc0.dirty\n>    GEN configure\n\n  $ ./configure\n[lots of output]\n> $ make\n>    CC fast-import.o\n\nAs pointed out before, you forgot to run the generated configure  \nscript (as already documented at Makefile:20).\n\nHowever, it's generally considered preferable to hand-create a  \nconfig.mak for the few options you need on a regular basis and let the  \nMakefile do it's work.  The autoconf files occasionally lag behind the  \nrest of development as they're not widely used by git developers  \n(AFAICT).\n\nI'd personally argue that we should point out in INSTALL that git can  \nbe configured via a hand-written config.mak using the defines  \ndescribed at the top of the Makefile before we talk about using  \nautoconf.  (Perhaps with quick notes about the most commonly used  \ndefines.)\n\nFor example, my config.mak contains:\n\nprefix=/usr/local\nASCIIDOC8=Yes\nMAN_BOLD_LITERAL=Yes\nBLK_SHA1=Yes\n\nThe rest of the configuration for my OS (OS X/Darwin, specifically)  \nare handled by the Makefile.\n\n~~ Brian\n"},{"id":"122722","messageId":"vpqzl95z0ke.fsf@bauges.imag.fr","threadId":"20873","inReplyTo":"a4c8a6d00909080752p5b663fc8r8bf1c60023ef39b4@mail.gmail.com","subject":"Re: [PATCH] Add more instructions about how to install git.","fromName":"Matthieu Moy","fromEmail":"matthieu.moy@grenoble-inp.fr","sentAt":"2009-09-08T19:41:21Z","receivedAt":"2009-09-08T19:41:21Z","isPatch":true,"sender":{"key":"matthieu.moy@grenoble-inp.fr","avatar":"https://gravatar.com/avatar/72c8a2705971a25dfaff23cece15130d405685845d911aedd5667ace277f3fc5?d=mp&s=160"},"body":"Thiago Farina <tfransosi@gmail.com> writes:\n\n> Running only \"make\".\n> $ make\n\n[...]\n\n> Running configure and then make\n> $ make configure\n> GIT_VERSION = 1.6.5.rc0.dirty\n>     GEN configure\n> $ make\n\n[...]\n\nWhat about trying to do what the INSTALL file suggests, then?\n\n| Alternatively you can use autoconf generated ./configure script to\n| set up install paths (via config.mak.autogen), so you can write\n| instead\n| \n|         $ make configure ;# as yourself\n|         $ ./configure --prefix=/usr ;# as yourself\n|         $ make all doc ;# as yourself\n|         # make install install-doc install-html;# as root\n\nYou did the first line, but the three next one give you instructions\nthat you didn't follow. These instructions start line 16 of the\nINSTALL file, that is, in the first screen when viewing the file with\na reasonable window size.\n\nI tend to disagree with the mainainer that the configure should be the\n\"alternate\" and plain make the recommanded way, but the configure\nscript is there, it works, it's documented early enough in the INSTALL\nfile, so what's the problem?\n\n-- \nMatthieu Moy\nhttp://www-verimag.imag.fr/~moy/\n"}]}