Re: Question about installing git from source

From: Alexander Kuleshov <kuleshovmail@gmail.com>
Date: Dec 23, 2014, 17:13 UTC
Message-ID: <CANCZXo4daZffQ7binFpHBy9adKKeuwHuR5VRixXUowMdgAdhTQ@mail.gmail.com>
In-Reply-To: <xmqqioh247th.fsf@gitster.dls.corp.google.com>

Hell Junio,

Look I download git from master, executed following:

make configure make prefix=/usr all sudo make prefix=/usr install

And got the same during installing:

~/dev/git $ sudo make prefix=/usr install
    GEN perl/PM.stamp
    SUBDIR perl
/usr/bin/perl Makefile.PL PREFIX='/usr' INSTALL_BASE=''
--localedir='/usr/share/locale'
Generating a Unix-style perl.mak
Writing perl.mak for Git
Writing MYMETA.yml and MYMETA.json
    GEN git-add--interactive
    GEN git-difftool
    GEN git-archimport
    GEN git-cvsexportcommit
    GEN git-cvsimport
    GEN git-cvsserver
    GEN git-relink
    GEN git-send-email
    GEN git-svn
    GEN git-p4
    SUBDIR gitweb
    SUBDIR ../
make[2]: 'GIT-VERSION-FILE' is up to date.
    GEN git-instaweb
    SUBDIR git-gui
    SUBDIR gitk-git
    SUBDIR perl
/usr/bin/perl -pe "s<\Q++LOCALEDIR++\E></usr/share/locale>"
<Git/SVN/Prompt.pm >blib/lib/Git/SVN/Prompt.pm
/usr/bin/perl -pe "s<\Q++LOCALEDIR++\E></usr/share/locale>"
<Git/SVN/Editor.pm >blib/lib/Git/SVN/Editor.pm
/usr/bin/perl -pe "s<\Q++LOCALEDIR++\E></usr/share/locale>"
<Git/SVN/Fetcher.pm >blib/lib/Git/SVN/Fetcher.pm
/usr/bin/perl -pe "s<\Q++LOCALEDIR++\E></usr/share/locale>"
<Git/SVN/Utils.pm >blib/lib/Git/SVN/Utils.pm
/usr/bin/perl -pe "s<\Q++LOCALEDIR++\E></usr/share/locale>"
<Git/SVN/Log.pm >blib/lib/Git/SVN/Log.pm
/usr/bin/perl -pe "s<\Q++LOCALEDIR++\E></usr/share/locale>"
<Git/SVN/Memoize/YAML.pm >blib/lib/Git/SVN/Memoize/YAML.pm
/usr/bin/perl -pe "s<\Q++LOCALEDIR++\E></usr/share/locale>"
<Git/SVN.pm >blib/lib/Git/SVN.pm
/usr/bin/perl -pe "s<\Q++LOCALEDIR++\E></usr/share/locale>"
<Git/SVN/Migration.pm >blib/lib/Git/SVN/Migration.pm
/usr/bin/perl -pe "s<\Q++LOCALEDIR++\E></usr/share/locale>"
<Git/IndexInfo.pm >blib/lib/Git/IndexInfo.pm
/usr/bin/perl -pe "s<\Q++LOCALEDIR++\E></usr/share/locale>"
<Git/SVN/GlobSpec.pm >blib/lib/Git/SVN/GlobSpec.pm
/usr/bin/perl -pe "s<\Q++LOCALEDIR++\E></usr/share/locale>"
<Git/SVN/Ra.pm >blib/lib/Git/SVN/Ra.pm
/usr/bin/perl -pe "s<\Q++LOCALEDIR++\E></usr/share/locale>" <Git.pm

>blib/lib/Git.pm

/usr/bin/perl -pe "s<\Q++LOCALEDIR++\E></usr/share/locale>"
<Git/I18N.pm >blib/lib/Git/I18N.pm
    SUBDIR templates
install -d -m 755 '/usr/bin'
Copying scripts to /usr/bin
cp: omitting directory ‘bin-wrappers’
cp: omitting directory ‘block-sha1’
cp: omitting directory ‘builtin’
cp: omitting directory ‘compat’
cp: omitting directory ‘contrib’
cp: omitting directory ‘Documentation’
cp: omitting directory ‘ewah’
cp: omitting directory ‘git-gui’
cp: omitting directory ‘gitk-git’

...

2014-12-23 23:03 GMT+06:00 Junio C Hamano <gitster@pobox.com>:

Show 43 quoted lines

> Alexander Kuleshov <kuleshovmail@gmail.com> writes:
>
>> Trying to install git from source, executing:
>>
>> make configure
>> ./configure --prefix=/usr
>> make --prefix=/usr all
>> sudo make install DISTDIR=/usr
>
> That does not seem to match any of the ways how INSTALL tells us to
> build and install.
>
> Excerpts from INSTALL
>
>     (1) ... If you want to do a global install, you can do
>
>         $ make prefix=/usr all doc info ;# as yourself
>         # make prefix=/usr install install-doc install-html install-info ;# as root
>
> Note how "prefix" is spelled.
>
>    (2) Alternatively you can use autoconf generated ./configure
>        script to set up install paths (via config.mak.autogen), so
>        you can write instead
>
>         $ make configure ;# as yourself
>         $ ./configure --prefix=/usr ;# as yourself
>         $ make all doc ;# as yourself
>         # make install install-doc install-html;# as root
>
> Note how "make" does not have any "prefix".
>
> Also when you install to a temporary directory so that you can tar
> up the resulting hierarchy, the variable to use is spelled DESTDIR,
> e.g.
>
>         make DESTDIR=/var/tmp/git-2.2.1 install install-doc
>
>> ...
>> What's problem can be here?
>
> Hopefully the above would be a good start to help you figure that
> out.

-- 
_________________________
0xAX