This is the mail archive of the
mailing list for the Cygwin project.
Re: Cygwin 1.7.14-2 make/gcc no longer functional on Windows 7 64-bit
- From: Christopher Faylor <cgf-use-the-mailinglist-please at cygwin dot com>
- To: cygwin at cygwin dot com
- Date: Thu, 10 May 2012 10:20:19 -0400
- Subject: Re: Cygwin 1.7.14-2 make/gcc no longer functional on Windows 7 64-bit
- References: <email@example.com>
- Reply-to: cygwin at cygwin dot com
On Thu, May 10, 2012 at 03:12:50AM -0400, DAGwyn@aol.com wrote:
>In a message dated 5/9/2012 6:35:38 A.M. Eastern Daylight Time,
>>On 5/9/2012 11:59 AM, DAGwyn@aol.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
>>> 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
>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
Problem reports: http://cygwin.com/problems.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple