Your message dated Wed, 12 Mar 2003 12:58:04 +0900
with message-id <[EMAIL PROTECTED]>
and subject line Bug#98361: More info please?
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; 22 May 2001 09:20:16 +0000
>From [EMAIL PROTECTED] Tue May 22 04:20:16 2001
Return-path: <[EMAIL PROTECTED]>
Received: from bimbo.mlociny.pl [213.134.143.66]
by master.debian.org with smtp (Exim 3.12 1 (Debian))
id 1528Ku-00014u-00; Tue, 22 May 2001 04:20:16 -0500
Received: (qmail 5851 invoked from network); 22 May 2001 09:20:43 -0000
Received: from michal.mlociny.pl (HELO michal.local) (192.168.1.71)
by bimbo.mlociny.pl with SMTP; 22 May 2001 09:20:43 -0000
Received: from michal.local ([EMAIL PROTECTED] [127.0.0.1])
by localhost (8.12.0.Beta7/8.12.0.Beta7/Debian 8.12.0.Beta7-1) with
ESMTP id f4M9KDYu015612
for <[EMAIL PROTECTED]>; Tue, 22 May 2001 11:20:13 +0200
Received: (from [EMAIL PROTECTED])
by michal.local (8.12.0.Beta7/8.12.0.Beta7/Debian 8.12.0.Beta7-1) id
f4M9KDqa015609
for [EMAIL PROTECTED]; Tue, 22 May 2001 11:20:13 +0200
Date: Tue, 22 May 2001 11:20:02 +0200
From: =?utf-8?Q?Micha=C5=82?= Rudewicz <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Subject: libc6-dev_2.2.3-1_i386 - /usr/include/string.h bug
Message-ID: <[EMAIL PROTECTED]>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
User-Agent: Mutt/1.3.15i
Delivered-To: [EMAIL PROTECTED]
Package: libc6-dev
Version: 2.2.3-1_i386
During compilations both - gcc-2.95 gcc-3.0 returns:
#v+
gcc-3.0 -c -O4 -pedantic -DUSG=1 buildhas.c
In file included from i_proto.h:79,
from ispell.h:607,
from buildhas.c:64:
/usr/include/string.h:242: parse error before "void"
/usr/include/string.h:245: parse error before "void"
#v-
I'm using Debian woody (upgraded from Potato, upgraded from Slink) with
2.4.4 kernel.
Michal
--
[EMAIL PROTECTED]
Little Shark, 09-320 Bieżuń, ul. Leśna 21 tel.:(0 602) 799 257
---------------------------------------
Received: (at 98361-done) by bugs.debian.org; 12 Mar 2003 03:58:06 +0000
>From [EMAIL PROTECTED] Tue Mar 11 21:58:05 2003
Return-path: <[EMAIL PROTECTED]>
Received: from oris.opensource.jp (oris.opensource.gr.jp) [218.44.239.73]
(postfix)
by master.debian.org with esmtp (Exim 3.12 1 (Debian))
id 18sxNV-0002At-00; Tue, 11 Mar 2003 21:58:05 -0600
Received: from oris.opensource.jp (oris.opensource.jp [218.44.239.73])
by oris.opensource.gr.jp (Postfix) with ESMTP
id 5E166C33C6; Wed, 12 Mar 2003 12:58:04 +0900 (JST)
Date: Wed, 12 Mar 2003 12:58:04 +0900
Message-ID: <[EMAIL PROTECTED]>
From: GOTO Masanori <[EMAIL PROTECTED]>
To: "H. S. Teoh" <[EMAIL PROTECTED]>,
[EMAIL PROTECTED], [EMAIL PROTECTED]
Subject: Re: Bug#98361: More info please?
In-Reply-To: <[EMAIL PROTECTED]>
References: <[EMAIL PROTECTED]>
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-Status: No, hits=-1.8 required=4.0
tests=IN_REP_TO,QUOTED_EMAIL_TEXT,REFERENCES,SPAM_PHRASE_00_01,
USER_AGENT
version=2.44
X-Spam-Level:
At Mon, 30 Dec 2002 15:57:25 -0500,
H. S. Teoh <[EMAIL PROTECTED]> wrote:
>
> tags 98361 + moreinfo
> thanks
>
> Hi, could you provide more info on this bug please? Such as snippets of
> the context surrounding the line numbers of the various .h files given in
> the original bug report.
>
> Just because the parse error occurs in string.h doesn't necessarily mean
> the bug is in string.h; an unterminated comment in a previously-included
> file can throw the compiler off-sync and cause an error much later on in
> an unrelated file.
>
> If it's possible, it would be great if you could send a snippet of the C
> processed code surrounding lines 220-260 in string.h. This should catch
> problems with unterminated comments.
This bug should be already fixed. There is no reason to keep opening,
so I close this bug.
Regards,
-- gotom
