X-Recipient:	archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status:	No, hits=-1.7 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_NONE,RCVD_IN_HOSTKARMA_YE
X-Spam-Check-By:	sourceware.org
X-Mail-Handler:	MailHop Outbound by DynDNS
X-Report-Abuse-To:	abuse AT dyndns DOT com (see http://www.dyndns.com/services/mailhop/outbound_abuse.html for abuse reporting information)
X-MHO-User:	U2FsdGVkX19As9AZ3AndjnDuevuRVvWC
Date:	Thu, 10 May 2012 10:20:19 -0400
From:	Christopher Faylor <cgf-use-the-mailinglist-please AT cygwin DOT com>
To:	cygwin AT cygwin DOT com
Subject:	Re: Cygwin 1.7.14-2 make/gcc no longer functional on Windows 7 64-bit
Message-ID:	<20120510142019.GC1729@ednor.casa.cgf.cx>
Reply-To:	cygwin AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
References:	<2147 DOT 541ee049 DOT 3cdcc472 AT aol DOT com>
MIME-Version:	1.0
In-Reply-To:	<2147.541ee049.3cdcc472@aol.com>
User-Agent:	Mutt/1.5.20 (2009-06-14)
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.com>
List-Unsubscribe:	<mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT 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 Thu, May 10, 2012 at 03:12:50AM -0400, DAGwyn AT aol DOT com wrote:
>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.)

I sincerely doubt that any Linux installer for make does anything like
this.  You don't necessarily need cc just because you're installing
make.

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