{"thread":{"id":"7152","subject":"Re: Git building is borked","startedAt":"2007-03-08T10:21:07Z","lastAt":"2007-03-08T15:19:14Z","messageCount":7,"participants":["Anton Altaparmakov","Shawn O. Pearce"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"36616","messageId":"4BBB354C-B000-4EF7-B3FF-7B2A4D6DE538@cam.ac.uk","threadId":"7152","inReplyTo":null,"subject":"Git building is borked","fromName":"Anton Altaparmakov","fromEmail":"aia21@cam.ac.uk","sentAt":"2007-03-08T10:21:07Z","receivedAt":"2007-03-08T10:21:07Z","isPatch":false,"sender":{"key":"aia21@cam.ac.uk","avatar":null},"body":"Hi,\n\nI am trying to build git on my Mac Book Pro running OSX Tiger 10.4.8  \nand I have run into a problem...\n\n[snip lots of successful output]\nmake -C git-gui all\nGITGUI_VERSION = 0.6.GITGUI\n     GEN CREDITS-FILE\nerror: Cannot locate authorship information.\nmake[1]: *** [CREDITS-FILE] Error 1\nmake: *** [all] Error 2\n\nLooking at the CREDITS-GEN script it runs git for all sorts of evil  \npurposes thus it appears that in order to build and install git one  \nhas to already got installed git!\n\nThat seems terminally flawed/broken to me...\n\nSo how do I get git installed in the first place on my OSX box?!?\n\nBest regards,\n\n\tAnton\n-- \nAnton Altaparmakov <aia21 at cam.ac.uk> (replace at with @)\nUnix Support, Computing Service, University of Cambridge, CB2 3QH, UK\nLinux NTFS maintainer, http://www.linux-ntfs.org/\n"},{"id":"36615","messageId":"F0177878-0A2B-43B0-9838-E032FB3A0A58@cam.ac.uk","threadId":"7152","inReplyTo":"4BBB354C-B000-4EF7-B3FF-7B2A4D6DE538@cam.ac.uk","subject":"Re: Git building is borked","fromName":"Anton Altaparmakov","fromEmail":"aia21@cam.ac.uk","sentAt":"2007-03-08T10:29:25Z","receivedAt":"2007-03-08T10:29:25Z","isPatch":false,"sender":{"key":"aia21@cam.ac.uk","avatar":null},"body":"It is even worse...\n\nHaving commented out all mentions of \"git-gui\" from the main git  \nMakefile, I was able to run make and \"sudo make install\" succesfully  \nand now I appear to have a working git.  (-:\n\nBut now I put the git-gui mentions back into the Makefile and tried  \nagain it still fails.  Looking at it closer it actually requires me  \nto compile within a checked out git tree, i.e. including the .git  \ndirectory and all its contents!  That seems even weirder than  \nrequiring git to be installed in the first place...\n\nBest regards,\n\n\tAnton\n\nOn 8 Mar 2007, at 10:21, Anton Altaparmakov wrote:\n\n> Hi,\n>\n> I am trying to build git on my Mac Book Pro running OSX Tiger  \n> 10.4.8 and I have run into a problem...\n>\n> [snip lots of successful output]\n> make -C git-gui all\n> GITGUI_VERSION = 0.6.GITGUI\n>     GEN CREDITS-FILE\n> error: Cannot locate authorship information.\n> make[1]: *** [CREDITS-FILE] Error 1\n> make: *** [all] Error 2\n>\n> Looking at the CREDITS-GEN script it runs git for all sorts of evil  \n> purposes thus it appears that in order to build and install git one  \n> has to already got installed git!\n>\n> That seems terminally flawed/broken to me...\n>\n> So how do I get git installed in the first place on my OSX box?!?\n>\n> Best regards,\n>\n> \tAnton\n\n-- \nAnton Altaparmakov <aia21 at cam.ac.uk> (replace at with @)\nUnix Support, Computing Service, University of Cambridge, CB2 3QH, UK\nLinux NTFS maintainer, http://www.linux-ntfs.org/\n"},{"id":"36624","messageId":"20070308145532.GA30674@spearce.org","threadId":"7152","inReplyTo":"F0177878-0A2B-43B0-9838-E032FB3A0A58@cam.ac.uk","subject":"Re: Git building is borked","fromName":"Shawn O. Pearce","fromEmail":"spearce@spearce.org","sentAt":"2007-03-08T14:55:32Z","receivedAt":"2007-03-08T14:55:32Z","isPatch":false,"sender":{"key":"spearce@spearce.org","avatar":"https://avatars.githubusercontent.com/u/34844?v=4"},"body":"Anton Altaparmakov <aia21@cam.ac.uk> wrote:\n> But now I put the git-gui mentions back into the Makefile and tried  \n> again it still fails.  Looking at it closer it actually requires me  \n> to compile within a checked out git tree, i.e. including the .git  \n> directory and all its contents!  That seems even weirder than  \n> requiring git to be installed in the first place...\n\nWhat version of Git specifically are you building with?  How did\nyou obtain these source files?\n\nRelease tarballs of Git contain a git-gui/credits file that makes\nCREDITS-GEN avoid invoking the not-yet-existing Git.  Building\ngit-gui without this file does require not only a working Git\ninstallation, but also the git-gui object database.  Both of these\nare readily available on a Git hacker's system, and on any system\nthat is attempting to create a release tarball.\n\nThere are other files included in the release tarballs (version,\ngit-gui/version) that are also required to get a correct build when\nyou don't have Git installed, or are missing its object database.\nHaving these missing does not stop the build process, but it does\nmake the output of `git version` and `git gui version` relatively\nuseless.\n\n\nSo you need to be bootstrapping from a released *.tar.{gz,bz2},\nwhich can be found here:\n\n  http://www.kernel.org/pub/software/scm/git/\n\n\nSadly, simply downloading the source files from a random gitweb\ndoesn't work anymore.  Yes, I know, my fault.  ;-)\n\n-- \nShawn.\n"},{"id":"36626","messageId":"C5E8BD06-1404-403B-88D0-F24F386A14AF@cam.ac.uk","threadId":"7152","inReplyTo":"20070308145532.GA30674@spearce.org","subject":"Re: Git building is borked","fromName":"Anton Altaparmakov","fromEmail":"aia21@cam.ac.uk","sentAt":"2007-03-08T15:07:57Z","receivedAt":"2007-03-08T15:07:57Z","isPatch":false,"sender":{"key":"aia21@cam.ac.uk","avatar":null},"body":"On 8 Mar 2007, at 14:55, Shawn O. Pearce wrote:\n> Anton Altaparmakov <aia21@cam.ac.uk> wrote:\n>> But now I put the git-gui mentions back into the Makefile and tried\n>> again it still fails.  Looking at it closer it actually requires me\n>> to compile within a checked out git tree, i.e. including the .git\n>> directory and all its contents!  That seems even weirder than\n>> requiring git to be installed in the first place...\n>\n> What version of Git specifically are you building with?  How did\n> you obtain these source files?\n\nOn my old workstation (Linux) which has the git git tree on it I  \ntarred up the files in the git directory (not including the .git  \ndirectory), then scp-ed the tar ball to my new workstation (OSX),  \nuntarred it there and tried to build git to boot strap...\n\n> Release tarballs of Git contain a git-gui/credits file that makes\n> CREDITS-GEN avoid invoking the not-yet-existing Git.  Building\n> git-gui without this file does require not only a working Git\n> installation, but also the git-gui object database.  Both of these\n> are readily available on a Git hacker's system, and on any system\n> that is attempting to create a release tarball.\n>\n> There are other files included in the release tarballs (version,\n> git-gui/version) that are also required to get a correct build when\n> you don't have Git installed, or are missing its object database.\n> Having these missing does not stop the build process, but it does\n> make the output of `git version` and `git gui version` relatively\n> useless.\n>\n> So you need to be bootstrapping from a released *.tar.{gz,bz2},\n> which can be found here:\n>\n>   http://www.kernel.org/pub/software/scm/git/\n>\n> Sadly, simply downloading the source files from a random gitweb\n> doesn't work anymore.  Yes, I know, my fault.  ;-)\n\nAh, ok.  I did not realize that released tar balls would be different  \nto just tarring up the files...\n\nThat is fair enough.  In the end I manage to boot strap myself by  \nremoving the git-gui stuff out of the main Makefile which allowed me  \nto do make and sudo make install.  Then I used the newly installed  \ngit to do a \"git clone\" of the git repository on kernel.org, then  \nbuild and installed that which gave me git-gui as well.\n\nI then deleted the old git directory I used for boot strapping.\n\nThanks for the quick response.\n\nBest regards,\n\n\tAnton\n-- \nAnton Altaparmakov <aia21 at cam.ac.uk> (replace at with @)\nUnix Support, Computing Service, University of Cambridge, CB2 3QH, UK\nLinux NTFS maintainer, http://www.linux-ntfs.org/\n"},{"id":"36627","messageId":"16571667-1962-4BB1-824A-9D7DD0A32747@cam.ac.uk","threadId":"7152","inReplyTo":"20070308145532.GA30674@spearce.org","subject":"Re: Git building is borked","fromName":"Anton Altaparmakov","fromEmail":"aia21@cam.ac.uk","sentAt":"2007-03-08T15:10:46Z","receivedAt":"2007-03-08T15:10:46Z","isPatch":false,"sender":{"key":"aia21@cam.ac.uk","avatar":null},"body":"btw. Would it be an idea to maybe make building/installing git-gui  \noptional?\n\nI actually did \"make configure\" and then the configure script...  It  \nshould not be too hard to make that detect whether it is running in  \nthe git repository and if not and the files are not there either  \nautomatically disable git-gui.  Or at least allow a \"--disable-git- \ngui\" switch to ./configure or something.\n\nWould make the lives of weird people like me easier.  (-:\n\nBest regards,\n\n\tAnton\n\nOn 8 Mar 2007, at 14:55, Shawn O. Pearce wrote:\n\n> Anton Altaparmakov <aia21@cam.ac.uk> wrote:\n>> But now I put the git-gui mentions back into the Makefile and tried\n>> again it still fails.  Looking at it closer it actually requires me\n>> to compile within a checked out git tree, i.e. including the .git\n>> directory and all its contents!  That seems even weirder than\n>> requiring git to be installed in the first place...\n>\n> What version of Git specifically are you building with?  How did\n> you obtain these source files?\n>\n> Release tarballs of Git contain a git-gui/credits file that makes\n> CREDITS-GEN avoid invoking the not-yet-existing Git.  Building\n> git-gui without this file does require not only a working Git\n> installation, but also the git-gui object database.  Both of these\n> are readily available on a Git hacker's system, and on any system\n> that is attempting to create a release tarball.\n>\n> There are other files included in the release tarballs (version,\n> git-gui/version) that are also required to get a correct build when\n> you don't have Git installed, or are missing its object database.\n> Having these missing does not stop the build process, but it does\n> make the output of `git version` and `git gui version` relatively\n> useless.\n>\n>\n> So you need to be bootstrapping from a released *.tar.{gz,bz2},\n> which can be found here:\n>\n>   http://www.kernel.org/pub/software/scm/git/\n>\n>\n> Sadly, simply downloading the source files from a random gitweb\n> doesn't work anymore.  Yes, I know, my fault.  ;-)\n\n-- \nAnton Altaparmakov <aia21 at cam.ac.uk> (replace at with @)\nUnix Support, Computing Service, University of Cambridge, CB2 3QH, UK\nLinux NTFS maintainer, http://www.linux-ntfs.org/\n"},{"id":"36628","messageId":"20070308151302.GC30674@spearce.org","threadId":"7152","inReplyTo":"C5E8BD06-1404-403B-88D0-F24F386A14AF@cam.ac.uk","subject":"Re: Git building is borked","fromName":"Shawn O. Pearce","fromEmail":"spearce@spearce.org","sentAt":"2007-03-08T15:13:02Z","receivedAt":"2007-03-08T15:13:02Z","isPatch":false,"sender":{"key":"spearce@spearce.org","avatar":"https://avatars.githubusercontent.com/u/34844?v=4"},"body":"Anton Altaparmakov <aia21@cam.ac.uk> wrote:\n> On 8 Mar 2007, at 14:55, Shawn O. Pearce wrote:\n> >What version of Git specifically are you building with?  How did\n> >you obtain these source files?\n> \n> On my old workstation (Linux) which has the git git tree on it I  \n> tarred up the files in the git directory (not including the .git  \n> directory), then scp-ed the tar ball to my new workstation (OSX),  \n> untarred it there and tried to build git to boot strap...\n\nSince you solved your problem, this is more for the list archives\nthan anything:\n\nUse `make dist` instead.  It uses your currently installed Git\nto generate a tarball from the revision in HEAD, then appends in\nthe 4 critical files.  I use this all of the time (almost daily,\nor close to it) to do builds of Git on Cygwin and Solaris 9.\nIn both cases I am building without `git` (or .git) available,\nand am relying on just the output of `make dist`.\n \n-- \nShawn.\n"},{"id":"36629","messageId":"C8A6CE49-CBAE-415E-8F40-D1062ECBD2F9@cam.ac.uk","threadId":"7152","inReplyTo":"20070308151302.GC30674@spearce.org","subject":"Re: Git building is borked","fromName":"Anton Altaparmakov","fromEmail":"aia21@cam.ac.uk","sentAt":"2007-03-08T15:19:14Z","receivedAt":"2007-03-08T15:19:14Z","isPatch":false,"sender":{"key":"aia21@cam.ac.uk","avatar":null},"body":"On 8 Mar 2007, at 15:13, Shawn O. Pearce wrote:\n> Anton Altaparmakov <aia21@cam.ac.uk> wrote:\n>> On 8 Mar 2007, at 14:55, Shawn O. Pearce wrote:\n>>> What version of Git specifically are you building with?  How did\n>>> you obtain these source files?\n>>\n>> On my old workstation (Linux) which has the git git tree on it I\n>> tarred up the files in the git directory (not including the .git\n>> directory), then scp-ed the tar ball to my new workstation (OSX),\n>> untarred it there and tried to build git to boot strap...\n>\n> Since you solved your problem, this is more for the list archives\n> than anything:\n>\n> Use `make dist` instead.  It uses your currently installed Git\n> to generate a tarball from the revision in HEAD, then appends in\n> the 4 critical files.  I use this all of the time (almost daily,\n> or close to it) to do builds of Git on Cygwin and Solaris 9.\n> In both cases I am building without `git` (or .git) available,\n> and am relying on just the output of `make dist`.\n\nAh, that is cool.  Thanks.  I will use that next time.  (-:\n\nBest regards,\n\n\tAnton\n-- \nAnton Altaparmakov <aia21 at cam.ac.uk> (replace at with @)\nUnix Support, Computing Service, University of Cambridge, CB2 3QH, UK\nLinux NTFS maintainer, http://www.linux-ntfs.org/\n"}]}