Your message dated Wed, 30 Jun 2004 04:59:50 +0900
with message-id <[EMAIL PROTECTED]>
and subject line [Bug other/6903] gcc could give better error message when /tmp gets 
full
has caused the attached Bug report to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)

--------------------------------------
Received: (at submit) by bugs.debian.org; 17 Aug 1998 18:02:55 +0000
Received: (qmail 2621 invoked from network); 17 Aug 1998 18:02:54 -0000
Received: from pcsw104b.ukc.ac.uk (129.12.41.137)
  by debian.novare.net with SMTP; 17 Aug 1998 18:02:54 -0000
Received: from merry.bs.net ([EMAIL PROTECTED])
        by pcsw104b.ukc.ac.uk (8.8.8/8.8.8/Debian/GNU) with floppy id TAA27095;
        Mon, 17 Aug 1998 19:02:52 +0100
Date: Mon, 17 Aug 1998 19:02:52 +0100
Message-Id: <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
From: Charles Briscoe-Smith <[EMAIL PROTECTED]>
Cc: Charles Briscoe-Smith <[EMAIL PROTECTED]>
Subject: gcc: could give better error message when /tmp gets full.

Package: gcc
Version: 2.7.2.3-4.7
Severity: wishlist

merry$ gcc -Wall -Werror -Wmissing-prototypes -g -O2 -I.  -DSTDC_HEADERS=1 
-DHAVE_STRDUP=1 -DHAVE_STRERROR=1 Test.c -o Test
cc1: /tmp/ccb04872: I/O error

This happened repeatedly when /tmp filled up during compilation (Test.c is
over a megabyte long)...  A better error message might mention "device
full" or some such.

-- 
Charles Briscoe-Smith
White pages entry, with PGP key: <URL:http://alethea.ukc.ac.uk/wp?95cpb4>
PGP public keyprint: 74 68 AB 2E 1C 60 22 94  B8 21 2D 01 DE 66 13 E2
---------------------------------------
Received: (at 25824-done) by bugs.debian.org; 29 Jun 2004 19:59:51 +0000
>From [EMAIL PROTECTED] Tue Jun 29 12:59:51 2004
Return-path: <[EMAIL PROTECTED]>
Received: from omega.webmasters.gr.jp (webmasters.gr.jp) [218.44.239.78] 
        by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
        id 1BfOlj-0003Xi-00; Tue, 29 Jun 2004 12:59:51 -0700
Received: from omega.webmasters.gr.jp (localhost [127.0.0.1])
        by webmasters.gr.jp (Postfix) with ESMTP
        id 90AF2DEB58; Wed, 30 Jun 2004 04:59:50 +0900 (JST)
Date: Wed, 30 Jun 2004 04:59:50 +0900
Message-ID: <[EMAIL PROTECTED]>
From: GOTO Masanori <[EMAIL PROTECTED]>
To: Charles Briscoe-Smith <[EMAIL PROTECTED]>,
        [EMAIL PROTECTED], [EMAIL PROTECTED]
Subject: Re: [Bug other/6903] gcc could give better error message when /tmp gets full
User-Agent: Wanderlust/2.9.9 (Unchained Melody) SEMI/1.14.3 (Ushinoya)
 FLIM/1.14.3 (=?ISO-8859-4?Q?Unebigory=F2mae?=) APEL/10.3 Emacs/21.2
 (i386-debian-linux-gnu) MULE/5.0 (SAKAKI)
MIME-Version: 1.0 (generated by SEMI 1.14.3 - "Ushinoya")
Content-Type: text/plain; charset=US-ASCII
Delivered-To: [EMAIL PROTECTED]
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2004_03_25 
        (1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Status: No, hits=-1.5 required=4.0 tests=BAYES_10 autolearn=no 
        version=2.60-bugs.debian.org_2004_03_25
X-Spam-Level: 

> Package: gcc
> Version: 2.7.2.3-4.7
> Severity: wishlist
> 
> merry$ gcc -Wall -Werror -Wmissing-prototypes -g -O2 -I.  -DSTDC_HEADERS=1 
> -DHAVE_STRDUP=1 -DHAVE_STRERROR=1 Test.c -o Test
> cc1: /tmp/ccb04872: I/O error
> 
> This happened repeatedly when /tmp filled up during compilation (Test.c is
> over a megabyte long)...  A better error message might mention "device
> full" or some such.

Unfortunatelly it's not even glibc bug.  EIO/ENOSPC is returned from
kernel, so this bug is occured by buggy kernel or filesystems.  I
think this bug is too old to keep open.  I close this bug.  If you
reappear this bug, please provide us your kernel version and mounted
filesystem name.

Regards,
-- gotom



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to