Re: installation issue when building with NO_CURL=YesPlease

From: "Dirk Süsserott" <newsletter@dirk.my1.cc>
To: Bruce Stephens <bruce.stephens@isode.com>
Cc: "Dirk Süsserott" <newsletter@dirk.my1.cc>,
	"Paul Walker" <PWalker752@aol.com>,
	"Ramkumar Ramachandra" <artagnon@gmail.com>,
	git@vger.kernel.org, git@drmicha.warpmail.net
Subject: Re: installation issue when building with NO_CURL=YesPlease
Date: Wed, 26 May 2010 21:03:30 +0200	[thread overview]
Message-ID: <4BFD7082.1080608@dirk.my1.cc> (raw)
In-Reply-To: <80typu1ozt.fsf@tiny.isode.net>

Am 26.05.2010 20:45 schrieb Bruce Stephens:
> Dirk Süsserott <newsletter@dirk.my1.cc> writes:
> 
> [...]
> 
>> 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.
> 
> It wouldn't be too horrible to fix the Makefiles, though.  Doing stuff
> like this works portably (judging by what some OpenSSL Makefiles do):
> 
> 	foo="$(REMOTE_CURL_ALIASES)"; for i in $$foo; do \
> 
> [...]
> 

Bruce,

I just saw that Michael posted a patch which tests for the emptyness of 
REMOTE_CURL_ALIASES. Probably that's a more convenient solution.

Dirk