{"thread":{"id":"25027","subject":"building git on Solaris","startedAt":"2010-09-07T21:02:35Z","lastAt":"2010-09-10T20:00:03Z","messageCount":6,"participants":["Chris Hoogendyk","Ævar Arnfjörð Bjarmason","Brandon Casey","Ben Walton","Tomas Carnecky"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"150254","messageId":"4C86A86B.1030107@bio.umass.edu","threadId":"25027","inReplyTo":null,"subject":"building git on Solaris","fromName":"Chris Hoogendyk","fromEmail":"hoogendyk@bio.umass.edu","sentAt":"2010-09-07T21:02:35Z","receivedAt":"2010-09-07T21:02:35Z","isPatch":false,"sender":{"key":"hoogendyk@bio.umass.edu","avatar":null},"body":"Building git 1.7.1 on Solaris 9 using gcc and gnu tools.\n\nMy build environment includes:\n\n    CC=gcc\n    CFLAGS='-L/usr/local/lib -R/usr/local/lib'\n    CPPFLAGS=-I/usr/local/include\n    LDFLAGS='-L/usr/local/lib -R/usr/local/lib'\n    LD_INCLUDE_PATH=/usr/include:/usr/local/include\n    LD_LIBRARY_PATH=/usr/local/lib:/usr/lib:/usr/sfw/lib\n    \nPATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/usr/ucb:/usr/ccs/bin\n    PWD=/usr/local/src/git/git-1.7.1\n    SHELL=/bin/ksh\n\nIf I ask `which make`, I get /usr/local/bin/make. If I say, `make \n--version`, I get \"GNU Make 3.80\".\n\nIf I ask `which perl`, I get /usr/local/bin/perl. If I say, `perl \n--version`, I get \"This is perl, v5.8.6 built for \nsun4-solaris-thread-multi\".\n\nI'm building with\n\n     # make configure\n     # ./configure --prefix=/usr/local\n     # make all doc\n     # make install install-doc install-html\n\nIt seems to work fine (though way sparse in what it has to say), until \nit hits here (from the `make all doc`):\n\n            :\n            :\n        GEN git-submodule\n        GEN git-web--browse\n        SUBDIR perl\n    make: Warning: Ignoring DistributedMake -o option\n    Usage : make [ -f makefile ][ -K statefile ]... [ -d ][ -dd ][ -D ][ \n-DD ]\n                 [ -e ][ -i ][ -k ][ -n ][ -p ][ -P ][ -q ][ -r ][ -s ][ \n-S ][ -t ]\n                 [ -u ][ -w ][ -V ][ target... ][ macro=value... ][ \n\"macro +=value\"... ]\n    make: Fatal error: Unknown option `-C'\n    make: *** [perl/perl.mak] Error 1\n\n\nI couldn't figure out where that was coming from (Can I turn on a bit \nmore verbosity during the build?) until I tried to do a `make clean` and \ngot a little more detail, where it ended up with `make -C Documentation/ \nclean` followed by the same set of errors.\n\nWhen I simply enter `make -C Documentation/ clean` from the command \nline, it works.\n\nPoking around, I eventually found that /usr/ccs/bin/make will emit those \nerrors, whereas /usr/local/bin/make does not. However, /usr/ccs/bin/make \nshould never be called. That is last in my PATH, whereas \n/usr/local/bin/make is first in my PATH.\n\nSo, something fishy is going on with the environment. But, those path \nprecedences are everywhere in my system. If I `su - nobody`, for \nexample, I get /usr/local/bin first in the PATH. I also did a `find . \n-type f | xargs grep ccs` from within /usr/local/src/git/git-1.7.1, and \nthe only things I found were in the config.log where it was noting \n/usr/ccs/bin/ar, /usr/ccs/bin/as and /usr/ccs/bin/ld, which, I believe, \nare correct.\n\nDoes anyone have any guidance or clues as to where I should look from \nhere? Or how to fix this?\n\nTIA\n\n\n---------------------\n\nNOTE: I also had to do the following:\n\n    # diff configure configure.orig\n    7810c7810\n    <   for opt in -pthreads -lpthreads; do\n    ---\n    >   for opt in -pthread -lpthread; do\n    #\n\nto get rid of errors like this:\n\n               :\n               :\n        CC xdiff/xpatience.o\n        AR xdiff/lib.a\n        LINK git-fast-import\n    gcc: unrecognized option `-pthread'\n        CC imap-send.o\n        LINK git-imap-send\n    gcc: unrecognized option `-pthread'\n        CC shell.o\n        LINK git-shell\n   gcc: unrecognized option `-pthread'\n        CC show-index.o\n        LINK git-show-index\n    gcc: unrecognized option `-pthread'\n               :\n               :\n\n---------------------\n\n\n-- \n---------------\n\nChris Hoogendyk\n\n-\n   O__  ---- Systems Administrator\n  c/ /'_ --- Biology & Geology Departments\n (*) \\(*) -- 140 Morrill Science Center\n~~~~~~~~~~ - University of Massachusetts, Amherst \n\n<hoogendyk@bio.umass.edu>\n\n--------------- \n\nErdös 4\n"},{"id":"150256","messageId":"AANLkTikvy-wUB-RFLegp7KJa_srqh97nLC03bdZDmru=@mail.gmail.com","threadId":"25027","inReplyTo":"4C86A86B.1030107@bio.umass.edu","subject":"Re: building git on Solaris","fromName":"Ævar Arnfjörð Bjarmason","fromEmail":"avarab@gmail.com","sentAt":"2010-09-07T21:42:20Z","receivedAt":"2010-09-07T21:42:20Z","isPatch":false,"sender":{"key":"avarab@gmail.com","avatar":"https://avatars.githubusercontent.com/u/45301?v=4"},"body":"On Tue, Sep 7, 2010 at 21:02, Chris Hoogendyk <hoogendyk@bio.umass.edu> wrote:\n\n> Does anyone have any guidance or clues as to where I should look from here?\n> Or how to fix this?\n\nCall make as gmake?\n"},{"id":"150299","messageId":"4C87A1DF.1020706@bio.umass.edu","threadId":"25027","inReplyTo":"AANLkTikvy-wUB-RFLegp7KJa_srqh97nLC03bdZDmru=@mail.gmail.com","subject":"Re: building git on Solaris","fromName":"Chris Hoogendyk","fromEmail":"hoogendyk@bio.umass.edu","sentAt":"2010-09-08T14:46:55Z","receivedAt":"2010-09-08T14:46:55Z","isPatch":false,"sender":{"key":"hoogendyk@bio.umass.edu","avatar":null},"body":"\n\nÆvar Arnfjörð Bjarmason wrote:\n> On Tue, Sep 7, 2010 at 21:02, Chris Hoogendyk <hoogendyk@bio.umass.edu> wrote:\n>   \n>> Does anyone have any guidance or clues as to where I should look from here?\n>> Or how to fix this?\n>>     \n>\n> Call make as gmake?\n\nmagical.\n\nI did an `ln -s /usr/local/bin/make /usr/local/bin/gmake` and then \nreferenced gmake rather than make. For some reason, that got over the \nhump. I have no clue why calling make would initially work and later in \nthe process revert to /usr/ccs/bin/make, but calling the same code via \nthe symlink name gmake works.\n\nAnyway, now I'm in the normal build debugging mode. Got all the way \nthrough to building the Documentation, at which stage I now need to get \nasciidoc and python. I don't really like bloating my minimal server \nsystems with python, but it seems I'm finally stuck, since I have \nfaculty who really want to use git.\n\nThanks for the clue.\n\n\n-- \n---------------\n\nChris Hoogendyk\n\n-\n   O__  ---- Systems Administrator\n  c/ /'_ --- Biology & Geology Departments\n (*) \\(*) -- 140 Morrill Science Center\n~~~~~~~~~~ - University of Massachusetts, Amherst \n\n<hoogendyk@bio.umass.edu>\n\n--------------- \n\nErdös 4\n"},{"id":"150306","messageId":"1283957577-sup-9932@pinkfloyd.chass.utoronto.ca","threadId":"25027","inReplyTo":"4C87A1DF.1020706@bio.umass.edu","subject":"Re: building git on Solaris","fromName":"Ben Walton","fromEmail":"bwalton@artsci.utoronto.ca","sentAt":"2010-09-08T14:55:11Z","receivedAt":"2010-09-08T14:55:11Z","isPatch":false,"sender":{"key":"bdwalton@gmail.com","avatar":"https://avatars.githubusercontent.com/u/396061?v=4"},"body":"Excerpts from Chris Hoogendyk's message of Wed Sep 08 10:46:55 -0400 2010:\n\nHi Chris,\n\n> get asciidoc and python. I don't really like bloating my minimal\n> server systems with python, but it seems I'm finally stuck, since I\n> have faculty who really want to use git.\n\nYou could also use the git packages[1] from OpenCSW.  You'll get all\nof the dependencies, etc and you won't need to install python.  You\nwill get the OpenCSW packages for perl, etc though, which you may find\nto be bloat too?\n\nHTH.\n-Ben\n\n[1] http://opencsw.org/packages/git\n--\nBen Walton\nSystems Programmer - CHASS\nUniversity of Toronto\nC:416.407.5610 | W:416.978.4302\n"},{"id":"150303","messageId":"nMrBbfBjISeakrCCpr3u3goqKMFMLUPCXiAa8ohZrHAmY1k660aYdA@cipher.nrlssc.navy.mil","threadId":"25027","inReplyTo":"4C87A1DF.1020706@bio.umass.edu","subject":"Re: building git on Solaris","fromName":"Brandon Casey","fromEmail":"brandon.casey.ctr@nrlssc.navy.mil","sentAt":"2010-09-08T15:16:54Z","receivedAt":"2010-09-08T15:16:54Z","isPatch":false,"sender":{"key":"brandon.casey.ctr@nrlssc.navy.mil","avatar":null},"body":"On 09/08/2010 09:46 AM, Chris Hoogendyk wrote:\n> Ævar Arnfjörð Bjarmason wrote:\n>> On Tue, Sep 7, 2010 at 21:02, Chris Hoogendyk <hoogendyk@bio.umass.edu> wrote:\n>>  \n>>> Does anyone have any guidance or clues as to where I should look from here?\n>>> Or how to fix this?\n>>>     \n>>\n>> Call make as gmake?\n> \n> magical.\n> \n> I did an `ln -s /usr/local/bin/make /usr/local/bin/gmake` and then referenced gmake rather than make. For some reason, that got over the hump. I have no clue why calling make would initially work and later in the process revert to /usr/ccs/bin/make, but calling the same code via the symlink name gmake works.\n> \n> Anyway, now I'm in the normal build debugging mode. Got all the way through to building the Documentation, at which stage I now need to get asciidoc and python. I don't really like bloating my minimal server systems with python, but it seems I'm finally stuck, since I have faculty who really want to use git.\n> \n> Thanks for the clue.\n\nThere is a quick-install-doc make target.\n\nIt extracts prebuilt documentation from a branch named origin/man\nin your repository.  Junio keeps this up-to-date with the\nDocumentation on master.  You can use it instead of trying to build\nthe documentation from scratch.\n\n-Brandon\n"},{"id":"150475","messageId":"4C8A8E43.1030708@dbservice.com","threadId":"25027","inReplyTo":"4C87A1DF.1020706@bio.umass.edu","subject":"Re: building git on Solaris","fromName":"Tomas Carnecky","fromEmail":"tom@dbservice.com","sentAt":"2010-09-10T20:00:03Z","receivedAt":"2010-09-10T20:00:03Z","isPatch":false,"sender":{"key":"tom@dbservice.com","avatar":"https://gravatar.com/avatar/900a300bdd1a8bbe086008ad78210bbee2ad2803b7d50a5cba04c1e9404bd6d2?d=mp&s=160"},"body":"On 9/8/10 4:46 PM, Chris Hoogendyk wrote:\n> Anyway, now I'm in the normal build debugging mode. Got all the way\n> through to building the Documentation, at which stage I now need to get\n> asciidoc and python. I don't really like bloating my minimal server\n> systems with python, but it seems I'm finally stuck, since I have\n> faculty who really want to use git.\n\nGit doesn't *need* python nor asciidoc, it works just fine without.\nExcept, of course, that tools which require python don't work (but there\naren't many of those, most is C, shell and perl).\n\ntom\n"}]}