Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/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
X-Info: This message was accepted for relay by
	smtp02.mrf.mail.rcn.net as the sender used SMTP authentication
X-Trace: UmFuZG9tSVYbZS+wYRQi4xo3wyHIiG2nCDv0es992j2mU1uzf6j7mcKypY1epJNt
Message-ID: <3F2489E7.5040302@cygwin.com>
Date: Sun, 27 Jul 2003 22:26:47 -0400
From: Larry Hall <cygwin-lh AT cygwin DOT com>
Reply-To: cygwin AT cygwin DOT com
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4) Gecko/20030624
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: cygwin AT cygwin DOT com
CC: Guy <guymarkey AT bigpond DOT com>
Subject: Re: Assembler messaes:FATAL can't create /cygdrive....
References: <Pine DOT GSO DOT 4 DOT 44 DOT 0307272220320 DOT 26427-100000 AT slinky DOT cs DOT nyu DOT edu>
In-Reply-To: <Pine.GSO.4.44.0307272220320.26427-100000@slinky.cs.nyu.edu>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit

Igor Pechtchanski wrote:
> Hi,
> 
> Replies inline below.
> 
> On Mon, 28 Jul 2003, Guy wrote:
> 
> 
>>G'day all,
>>I've recently installed cygwin v1.5.0-1 and gcc v3.2.3 on my machine
> 
> 
> FYI, cygwin 1.5.0 is a test release...  It should still work, but you
> might also try it with 1.3.22 and let this list know if there's a
> regression in 1.5.0...
> 
> 
>>(windows ME) but am having a nightmare getting gcc to work!
>>I was running configure thus
>>sh configure --prefix=c:/fltk-1.1.4/fltk-1.1.4rc1/
> 
> 
> I don't think it's wise to pass Win32 paths to a shell script.  Some
> Cygwin programs understand Win32 paths, but it's better to use POSIX paths
> all around.  For more information, "man cygpath".
> 
> 
>>and getting...
>>
>>checking for gcc...   gcc
>>checking for C compiler default output...  configure:error:C compiler cannot
>>create executables.
> 
> 
> The file "config.log" should tell you exactly what went wrong there.
> 
> 
>>To try to work out what was wrong I wrote a simple hello_world.c program to
>>test things. when I went to compile with
>>gcc -I/syg/usr/include -o hello.o hello_world.c
>>I received the following
>>Assembler messages:
>>Error: can't create /cygdrive/c/TEMP/ccJ6snL.o: No such file or directory
> 
> 
> This is because your "TMP" or "TEMP" shell variable was set to "c:\TEMP"
> by Windows.  Try doing "export TEMP=/tmp" before compiling (or put it in
> your .bash_profile).
> 
> 
>>I then created the directory /cygdrive/c/TEMP and got
>>Error : can't open /cygdrive/c/TEMP/ccnsEmIl.s for reading : No such file or
>>directory.
> 
> 
> Could be a permission issue, or something to do with the "check_case"
> value in the CYGWIN variable -- too little information to tell for sure.
> Does "ls /cygdrive/c/TEMP" work?
> 
> At a guess, this should go away with using "export TEMP=/tmp", anyway.
> 
> 
>>from all this I gather that when I installed gcc the directory /cygdrive..
>>should have been created? with some stuff in it. I know f.. all about how
>>the assembler does its stuff!
> 
> 
> No, gcc uses the value of the TEMP variable to find out where to create
> its stuff.  Set TEMP to something different, and your temporary files will
> be created there.
> 
> 
>>Can anyone tell me where I've stuffed up?
>>Thanks
>>Guy
> 
> 
> You didn't -- Windows did.  I'm not quite sure why /cygdrive/c/TEMP
> as the value for TEMP doesn't work for you (works for me)...  See guesses
> above.


Or <http://cygwin.com/problems.html>.



-- 
Larry Hall                              http://www.rfk.com
RFK Partners, Inc.                      (508) 893-9779 - RFK Office
838 Washington Street                   (508) 893-9889 - FAX
Holliston, MA 01746


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