This is the mail archive of the
mailing list for the Cygwin project.
Re: GCC fatal error: can't open /tmp/ccc6IHTT.s for writing
- From: Earnie Boyd <earnie at users dot sourceforge dot net>
- To: cygwin at cygwin dot com
- Date: Fri, 24 Feb 2012 09:41:00 -0500
- Subject: Re: GCC fatal error: can't open /tmp/ccc6IHTT.s for writing
- Authentication-results: mr.google.com; spf=pass (google.com: domain of firstname.lastname@example.org designates 10.52.36.84 as permitted sender) email@example.com; dkim=pass firstname.lastname@example.org
- References: <4F4756DD.email@example.com> <4F477DBD.firstname.lastname@example.org> <4F479609.email@example.com>
On Fri, Feb 24, 2012 at 8:52 AM, Paul Keir <firstname.lastname@example.org> 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.
> I'm afraid I can't send the output of cygcheck to the mailing list for
> confidentiality reasons. I could either send it to you directly, or perhaps
> run cygcheck in a way to generate less data. By the way I get the following
> errors from cygcheck, only when I redirect the output:
You can always edit the file to blot out the sensitive data.
sed -e 's.sensitive.insensitive.g' cygcheck.sensitive > cygcheck.insensitive
Problem reports: http://cygwin.com/problems.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple