X-Recipient:	archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status:	No, hits=0.0 required=5.0 tests=BAYES_20,DKIM_SIGNED,DKIM_VALID,FREEMAIL_FROM,RCVD_IN_DNSWL_NONE,RCVD_IN_HOSTKARMA_YE,T_RP_MATCHES_RCVD
X-Spam-Check-By:	sourceware.org
From:	DAGwyn AT aol DOT com
Message-ID:	<2147.541ee049.3cdcc472@aol.com>
Date:	Thu, 10 May 2012 03:12:50 -0400 (EDT)
Subject:	Re: Cygwin 1.7.14-2 make/gcc no longer functional on Windows 7 64-bit
To:	marco DOT atzeri AT gmail DOT com, cygwin AT cygwin DOT com
MIME-Version:	1.0
x-aol-global-disposition:	G
X-AOL-SCOLL-SCORE:	0:2:495475584:93952408
X-AOL-SCOLL-URL_COUNT:	0
x-aol-sid:	3039ac1d290a4fab6a725ff0
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

In a message dated 5/9/2012 6:35:38 A.M. Eastern  Daylight Time, 
marco DOT atzeri AT gmail DOT com writes:
>On 5/9/2012 11:59 AM,  DAGwyn AT aol DOT com wrote:
>> PROBLEM  1:  "make" expects "cc" to  exist, and indeed it existed in my
>> previous  (August 2011)  installation of Cygwin.
>> PROBLEM 2:  "gcc-4" (also  happens  for gcc-3) can't create a writeable 
file
>> in /tmp, but "bash"  can.
> start removing this:
> 2604k 2011/03/29  C:\Windows\SYSTEM\cygwin1.dll - os=4.0 img=1.0 sys=4.0

Thanks; that fixed problem # 2.  I suggest that the installation  procedure 
should
either remove that file itself or else at least warn about it.
 
I worked around problem # 1 by invoking "ln -s /bin/gcc-4 /bin/cc" and  
suggest that
the GNU-make installation procedure should test for existence of various  
cc-compatible
commands and set up a similar link.  (Note also that some people  expect 
"c99"
to also exist, since it is required for POSIX compliance.)
 
My Cygwin Bash environment now seems to function as well as it used  to.
I appreciate the prompt response.
 

--
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

- Raw text -