X-Recipient: archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status: No, hits=-2.0 required=5.0	tests=AWL,BAYES_00,T_RP_MATCHES_RCVD
X-Spam-Check-By: sourceware.org
Message-ID: <4F50275E.5060901@cs.cmu.edu>
Date: Thu, 01 Mar 2012 17:50:22 -0800
From: Paul Allen Newell <pnewell AT cs DOT cmu DOT edu>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.27) Gecko/20120216 Thunderbird/3.1.19
MIME-Version: 1.0
To: cygwin AT cygwin DOT com
CC: "Newell, Paul" <pnewell AT cs DOT cmu DOT edu>
Subject: Re: question on Cygwin's version of make
References: <4F4F21AC DOT 7060209 AT cs DOT cmu DOT edu> <CAB8Xom9zz5CN+yE6cHBj-h-PG4aUxghckkmAYZiQko8SfmNuhQ AT mail DOT gmail DOT com> <4F4F2877 DOT 4080006 AT cs DOT cmu DOT edu> <4F4FB35D DOT 1010802 AT molconn DOT com>
In-Reply-To: <4F4FB35D.1010802@molconn.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-IsSubscribed: yes
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com

On 3/1/2012 9:35 AM, LMH wrote:
> Some folks call make from a bash file to take advantage of things that 
> bash can do and make can't, or at least easily. Using a "config.sh" to 
> run make could let you test anything you want, print warnings, or 
> exit, if anything is spotted. If everything looks good, the script can 
> call make. This is common when you need to collect information about 
> the local configuration (OS, arch, preferences, etc) in a portable way.
>
> Don't know if that helps, but that is what occurred to me reading you 
> post.
>
> LMH
>

LMH:

Thanks for the reply. For many years, I've had no trouble doing 
everything inside a makefile, including getting platform/OS/etc. I've 
seen posts that use a config.sh or similar ... up until now I've had no 
need to consider that path.

Given that the problem is identified (basename doesn't like spaces), a 
fix is easy (don't use spaces), and everything works, I don't think 
switching is going to help me. Its more and more looking (to me) like a 
error/warning message is thrown by basename which is being called under 
the hood by make (as opposed to my explicitly using that function) and, 
right now, I can't capture the message when I think I am getting 
everything stdout and stderr is spitting out.

Paul

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple