Message-ID: <4FAA4870.1020604@gmail.com>
Date: Wed, 09 May 2012 12:35:28 +0200
From: marco atzeri <marco DOT atzeri AT gmail DOT com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:12.0) Gecko/20120428 Thunderbird/12.0.1
MIME-Version: 1.0
To: DAGwyn AT aol DOT com, cygwin AT cygwin DOT com
Subject: Re: Cygwin 1.7.14-2 make/gcc no longer functional on Windows 7 64-bit
References: <29681 DOT 57c19e47 DOT 3cdb9a19 AT aol DOT com>
In-Reply-To: <29681.57c19e47.3cdb9a19@aol.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com

On 5/9/2012 11:59 AM, DAGwyn AT aol DOT com wrote:
> I just installed Cygwin on Windows 7 64-bit, rooted at D:\cygwin, using the
>   latest (1.7.14-2) setup.exe a few hours ago.  In addition to the  default
> packages, I added several others including gcc4, gcc, and GNU  make.  (See
> the attached cygcheck.out for the full list.)  Here is a  portion of a bash
> terminal session:
>
> Douglas AT Douglas-PC ~
> $ ls  -bCF  # note that there is no Makefile ...
> bin/ DOTFILES/ gcc-tools/ HG/  lib/ OS/ src/ work/
> cygcheck.out DOTS/ hello.c include/ man/ PROBE.OUT  SX/
>
> Douglas AT Douglas-PC ~
> $ make hello.o  # ... so "make" uses its  default definitions and rules
> cc    -c -o hello.o  hello.c
> make: cc: Command not found
> <builtin>: recipe for target  `hello.o' failed
> make: *** [hello.o] Error 127
>
> Douglas AT Douglas-PC  ~
> $ gcc-4 -c -o hello.o hello.c  # (get similar behavior from  gcc-3)
> hello.c:1:0: fatal error: can’t open /tmp/ccEwiiBz.s for writing: No  such
> file or directory
> compilation terminated.
>
> Douglas AT Douglas-PC  ~
> $ echo foo>  /tmp/bar  # works fine for bash ...
>
> 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.
>
> ADDITIONAL CLUE:  A similar installation on the same system from  August
> 2011 was working fine, until I fetched updates that seemed to break it  (see
> below).  I deleted the entire D:\cygwin folder, icons, etc. and  reinstalled
> Cygwin from scratch, with the above results.
>
> JUST IN CASE:  I recently had a problem with the SONAR component  of Norton
> 360 detecting "suspicious activity" in some executables I had compiled
> under Cygwin. and auto-deleting the executables.  I disabled SONAR checking
> for all of D:\cygwin, then fetched Cygwin updates as reported in  the
> preceding paragraph.  I haven't seen any further warnings from  SONAR, and don't
> think it could explain the reported problems.
>

start removing this:

2604k 2011/03/29 C:\Windows\SYSTEM\cygwin1.dll - os=4.0 img=1.0 sys=4.0
                   "cygwin1.dll" v0.0 ts=2011/3/29 9:10
     Cygwin DLL version info:
         DLL version: 1.7.9
         DLL epoch: 19
         DLL old termios: 5
         DLL malloc env: 28
         Cygwin conv: 181
         API major: 0
         API minor: 237
         Shared data: 5
         DLL identifier: cygwin1
         Mount registry: 3
         Cygwin registry name: Cygwin
         Program options name: Program Options
         Installations name: Installations
         Cygdrive default prefix:
         Build date:
         Shared id: cygwin1S5

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