From: "Dirk Süsserott" <newsletter@dirk.my1.cc>
To: Paul Walker <PWalker752@aol.com>
Cc: Ramkumar Ramachandra <artagnon@gmail.com>, git@vger.kernel.org
Subject: Re: installation issue when building with NO_CURL=YesPlease
Date: Wed, 26 May 2010 20:27:26 +0200 [thread overview]
Message-ID: <4BFD680E.8000603@dirk.my1.cc> (raw)
In-Reply-To: <8E0CE121-DB2F-4017-AB46-282562B072FB@aol.com>
Am 26.05.2010 16:15 schrieb Paul Walker:
>
> On 26 May 2010, at 14:58, Ramkumar Ramachandra wrote:
>
>> Hi,
>>
>>> As I could not find any bug reporting information on the wiki I
>>> thought I
>>> would mention this here, please let me know if there is a better
>>> forum for
>>> bug reports.
>>
>> Bugs are usually reported on this mailing list.
>>
>>> I believe the latest git release (1.7.1.) has an installation
>>> bug when building with "NO_CURL=YesPlease". Looking at the Makefile
>>> line
>>> 1999 it reads
>>>
>>> for p in $(REMOTE_CURL_ALIASES); do
>>>
>>> which results in "/bin/sh: syntax error at line 1 : `;' unexpected" as
>>> REMOTE_CURL_ALIASES is empty.
>>
>> I can't reproduce this. How exactly are you building? I'm using
>> $ NO_CURL=YesPlease make
>> ... and it builds fine for me.
>>
>> -- Ram
>
> I used:
>
> gmake prefix=<path> NO_CURL=YesPlease NO_PYTHON=YesPlease all
>
> which works fine, followed by
>
> gmake prefix=<path> NO_CURL=YesPlease NO_PYTHON=YesPlease install
>
> which reported the above error
>
I had a similar problem when "make install"ing under AIX. Not with
NO_CURL but with some other NO_* option. I forgot which.
This yealded to an empty $(REMOTE_***_ALIASES) macro
(REMOTE_CURL_ALIASES in your case) which my AIX shell cannot handle.
It reads "for p in; do" which makes it unhappy. I solved my problem with
the SHELL_PATH environment variable (look at the first few lines in
the Makefile).
$ SHELL_PATH=/bin/bash NO_SOMETHING=YesPlease make install
then worked fine for me.
HTH,
Dirk
next prev parent reply other threads:[~2010-05-26 18:33 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-26 13:35 installation issue when building with NO_CURL=YesPlease Paul Walker
2010-05-26 13:58 ` Michael J Gruber
2010-05-26 14:41 ` Paul Walker
2010-05-26 13:58 ` Ramkumar Ramachandra
2010-05-26 14:15 ` Paul Walker
2010-05-26 14:24 ` [PATCH] Makefile: reenable install with NO_CURL Michael J Gruber
2010-05-26 18:27 ` Dirk Süsserott [this message]
2010-05-26 18:45 ` installation issue when building with NO_CURL=YesPlease Bruce Stephens
2010-05-26 19:03 ` Dirk Süsserott
2010-07-02 18:50 ` [PATCH 1/2] Makefile: remove some unnecessary curly braces Brandon Casey
2010-07-02 18:50 ` [PATCH 2/2] Makefile: work around ksh's failure to handle missing list argument to for loop Brandon Casey
2010-07-03 6:21 ` Raja R Harinath
2010-07-04 18:37 ` Michael J Gruber
2010-07-05 6:19 ` Johannes Sixt
2010-07-05 8:14 ` Michael J Gruber
2010-07-05 9:15 ` Johannes Sixt
2010-07-05 9:31 ` Michael J Gruber
2010-07-05 18:18 ` Junio C Hamano
2010-07-05 20:00 ` Andreas Schwab
2010-07-05 21:29 ` Brandon Casey
2010-07-06 2:36 ` Junio C Hamano
2010-07-06 21:56 ` [PATCH 2/2 v2] " Brandon Casey
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=4BFD680E.8000603@dirk.my1.cc \
--to=newsletter@dirk.my1.cc \
--cc=PWalker752@aol.com \
--cc=artagnon@gmail.com \
--cc=git@vger.kernel.org \
/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).