From: Andreas Ericsson <ae@op5.se>
To: Jakub Narebski <jnareb@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: Compiling git-snapshot-20069831
Date: Thu, 31 Aug 2006 17:19:24 +0200 [thread overview]
Message-ID: <44F6FDFC.9050707@op5.se> (raw)
In-Reply-To: <ed6tg9$9ij$1@sea.gmane.org>
Jakub Narebski wrote:
> Jorma Karvonen wrote:
>
>> When I tested
>>
>> make NEEDS_LIBICONV=1 NO_CURL=1
>>
>> the make succeeded but when trying make install I got error messages
>> shown in the enclosed file.
>
> Try then
> $ NEEDS_LIBICONV=YesPlease NO_CURL=YesPlease make
>
I think you meant
$ make NEEDS_LIBICONV=YesPlease NO_CURL=YesPlease install
there, Jakub.
Jorma, since the Makefile has no ideas on state, it only notices that
some files it needs to make a complete install with the parameters
you're passing it when also passing 'install' are missing, it tries to
build them, but without the NEEDS_LIBICONV and NO_CURL flags. Pass them
both when doing normal 'make' and when doing 'make install' and you'll
be fine. You might also want to check if your distribution provides a
pre-compiled package. If that's the case, you should be able to get away
with something easy such as
$ apt-get install git
or
$ yum install git
Good luck
--
Andreas Ericsson andreas.ericsson@op5.se
OP5 AB www.op5.se
Tel: +46 8-230225 Fax: +46 8-230231
next prev parent reply other threads:[~2006-08-31 15:19 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-31 12:03 Compiling git-snapshot-20069831 Jorma Karvonen
2006-08-31 12:09 ` Johannes Schindelin
2006-08-31 12:24 ` Jakub Narebski
2006-08-31 14:38 ` Jorma Karvonen
2006-08-31 14:59 ` Jakub Narebski
2006-08-31 15:19 ` Andreas Ericsson [this message]
2006-08-31 15:28 ` Johannes Schindelin
2006-08-31 16:59 ` Jorma Karvonen
2006-08-31 17:06 ` Johannes Schindelin
2006-08-31 17:25 ` Jorma Karvonen
2006-08-31 19:30 ` Jakub Narebski
2006-09-01 13:30 ` Jorma Karvonen
2006-08-31 21:37 ` Linus Torvalds
2006-08-31 22:07 ` Johannes Schindelin
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=44F6FDFC.9050707@op5.se \
--to=ae@op5.se \
--cc=git@vger.kernel.org \
--cc=jnareb@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).