From: Mikael Magnusson <mikachu@gmail.com>
To: Thiago Farina <tfransosi@gmail.com>
Cc: Johannes Sixt <j.sixt@viscovery.net>,
Matthieu Moy <Matthieu.Moy@grenoble-inp.fr>,
Alex Riesen <raa.lkml@gmail.com>,
git@vger.kernel.org
Subject: Re: [PATCH] Add more instructions about how to install git.
Date: Tue, 8 Sep 2009 16:56:03 +0200 [thread overview]
Message-ID: <237967ef0909080756g579f5359te7da19fded27596f@mail.gmail.com> (raw)
In-Reply-To: <a4c8a6d00909080752p5b663fc8r8bf1c60023ef39b4@mail.gmail.com>
2009/9/8 Thiago Farina <tfransosi@gmail.com>:
> On Tue, Sep 8, 2009 at 10:38 AM, Johannes Sixt<j.sixt@viscovery.net> wrote:
>> Thiago Farina schrieb:
>>> I tried to being more explicit about what the new users has to do. The
>>> first instruction that the text says is: "Normaly you can just do
>>> "make"".
>>> But the new user, cloning git won't have a configure file, so he can't
>>> just do "make".
>>>
>>> And then, the text says: "so you can write instead". This brings me to
>>> one alternative (not what I really should do), when in fact it should
>>> be (I guess) the first instructions that new users need to follow.
>>
>> Then guessed wrong. You really only have to say "make". The use of
>> autoconf and ./configure is purely optional and not necessary.
> I don't think so.
> Running only "make".
> $ make
> GIT_VERSION = 1.6.5.rc0
> * new build flags or prefix
> CC fast-import.o
> In file included from builtin.h:4,
> from fast-import.c:143:
> git-compat-util.h:129:25: error: openssl/ssl.h: No such file or directory
> git-compat-util.h:130:25: error: openssl/err.h: No such file or directory
[snip]
You need to edit the Makefile if your system needs tweaks, there are tons
of comments.
> Running configure and then make
> $ make configure
> GIT_VERSION = 1.6.5.rc0.dirty
> GEN configure
> $ make
> CC fast-import.o
> In file included from builtin.h:4,
> from fast-import.c:143:
> git-compat-util.h:129:25: error: openssl/ssl.h: No such file or directory
> git-compat-util.h:130:25: error: openssl/err.h: No such file or directory
You forgot to run configure.
> Now autconf, ./configure, make.
> $ autoconf
> $ ./configure
> configure: Setting lib to 'lib' (the default)
> configure: Will try -pthread then -lpthread to enable POSIX Threads.
> configure: CHECKS for site configuration
> configure: CHECKS for programs
[...]
> checking for mkstemps... no
> checking Checking for POSIX Threads with '-pthread'... yes
> configure: creating ./config.status
> config.status: error: cannot find input file: config.mak.in
> $ make
>
> Now it compiles everything.
--
Mikael Magnusson
next prev parent reply other threads:[~2009-09-08 14:56 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-08 5:11 [PATCH] Add more instructions about how to install git Thiago Farina
2009-09-08 5:44 ` Alex Riesen
2009-09-08 6:20 ` Matthieu Moy
2009-09-08 7:56 ` Michael J Gruber
2009-09-08 14:24 ` Thiago Farina
2009-09-08 14:37 ` Erik Faye-Lund
2009-09-08 14:38 ` Johannes Sixt
2009-09-08 14:52 ` Thiago Farina
2009-09-08 14:56 ` Mikael Magnusson [this message]
2009-09-08 15:19 ` Brian Gernhardt
2009-09-08 19:41 ` Matthieu Moy
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=237967ef0909080756g579f5359te7da19fded27596f@mail.gmail.com \
--to=mikachu@gmail.com \
--cc=Matthieu.Moy@grenoble-inp.fr \
--cc=git@vger.kernel.org \
--cc=j.sixt@viscovery.net \
--cc=raa.lkml@gmail.com \
--cc=tfransosi@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).