Re: GCC fatal error: can't open /tmp/ccc6IHTT.s for writing

2012-07-25 Thread mark . kica
Robert Miles bellsouth.net> writes: Hello , I had same problem . The reason was older cygwin1.dll . Try to delete all of them (also in c:\Windows\System32\ directory) , and reinstall cygwin package with setup.exe (cygwin : The Linux emulation engine) -- Problem reports: htt

Re: GCC fatal error: can't open /tmp/ccc6IHTT.s for writing

2012-02-27 Thread Dave Korn
On 27/02/2012 16:12, Paul Keir wrote: > Thanks Dave, it's fixed. It looks like the problem was the cygwin1.dll > in C:\Windows\SYSTEM. I have no idea why that was there. (I am not the > first to use this machine.) Well, you may just find out when something else stops working - it's not unknown f

Re: GCC fatal error: can't open /tmp/ccc6IHTT.s for writing

2012-02-27 Thread Paul Keir
Thanks Dave, it's fixed. It looks like the problem was the cygwin1.dll in C:\Windows\SYSTEM. I have no idea why that was there. (I am not the first to use this machine.) As a precaution I have also removed C:\Users\\home\apps\gcc-4.7-20120128\bin from my PATH. I had built it with --pr

Re: GCC fatal error: can't open /tmp/ccc6IHTT.s for writing

2012-02-24 Thread Robert Miles
On 2/24/2012 3:22 AM, Paul Keir wrote: Hello, After installing a package (libxrandr-dev I think) GCC 4.5.3 (from Exp) has a problem. Even Hello World gives me: hello.c:1:0: fatal error: can't open /tmp/ccc6IHTT.s for writing: No such file or directory compilation terminated. I have tried r

Re: GCC fatal error: can't open /tmp/ccc6IHTT.s for writing

2012-02-24 Thread Dave Korn
On 24/02/2012 15:36, Paul Keir wrote: > echo $? returns 1 after using gcc. Right, that's "helpful" of it! That's clearly just a fail status but not an errno value. Anyway, I think your cygcheck reveals the problem. You have multiple cygwin1.dlls of different versions in your path at the sam

Re: GCC fatal error: can't open /tmp/ccc6IHTT.s for writing

2012-02-24 Thread Paul Keir
echo $? returns 1 after using gcc. On 24/02/2012 14:57, Dave Korn wrote: On 24/02/2012 13:52, Paul Keir wrote: Thanks. No, it's not full. The permissions are: drwxrwxrwt+ 1 Paul root 0 Feb 24 13:36 tmp and I can create the same file manually. Oh well, always worth checking the basics

Re: GCC fatal error: can't open /tmp/ccc6IHTT.s for writing

2012-02-24 Thread Dave Korn
On 24/02/2012 13:52, Paul Keir wrote: > Thanks. No, it's not full. The permissions are: > drwxrwxrwt+ 1 Paul root 0 Feb 24 13:36 tmp > and I can create the same file manually. Oh well, always worth checking the basics first, but no real surprise! > The output of gcc -v hello.c is attached.

Re: GCC fatal error: can't open /tmp/ccc6IHTT.s for writing

2012-02-24 Thread Earnie Boyd
On Fri, Feb 24, 2012 at 8:52 AM, Paul Keir wrote: > Thanks. No, it's not full. The permissions are: > drwxrwxrwt+ 1 Paul root      0 Feb 24 13:36 tmp > and I can create the same file manually. > > The output of gcc -v hello.c is attached. I am running Windows 7 > Professional - Service Pack 1. > >

Re: GCC fatal error: can't open /tmp/ccc6IHTT.s for writing

2012-02-24 Thread Paul Keir
Thanks. No, it's not full. The permissions are: drwxrwxrwt+ 1 Paul root 0 Feb 24 13:36 tmp and I can create the same file manually. The output of gcc -v hello.c is attached. I am running Windows 7 Professional - Service Pack 1. I'm afraid I can't send the output of cygcheck to the mailing

Re: GCC fatal error: can't open /tmp/ccc6IHTT.s for writing

2012-02-24 Thread Dave Korn
On 24/02/2012 09:22, Paul Keir wrote: > Hello, > > After installing a package (libxrandr-dev I think) GCC 4.5.3 (from Exp) > has a problem. Even Hello World gives me: > > hello.c:1:0: fatal error: can't open /tmp/ccc6IHTT.s for writing: No > such file or directory > compilation terminated. > > I