Your message dated Wed, 16 May 2012 23:25:51 +0100
with message-id
<CAPQ4b8=m5zq6mPLjoh0mZT3Bhq=gkytyf3aqhs-kvzijxut...@mail.gmail.com>
and subject line Re: libc6-dev: programs using HUGE_VAL will issue a warning
when compiled with -pedantic on the g++-3.3
has caused the Debian Bug report #231748,
regarding libc6-dev: programs using HUGE_VAL will issue a warning when compiled
with -pedantic on the g++-3.3
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 this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
231748: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=231748
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libc6-dev
Version: 2.3.2-8
Severity: normal
-- System Information
Debian Release: 3.0
Architecture: i386
Kernel: Linux skywise 2.4.24 #1 Sat Jan 31 22:26:19 CET 2004 i686
Locale: LANG=de_DE, LC_CTYPE=de_DE
Versions of packages libc6-dev depends on:
ii libc6 2.3.2-8 GNU C Library: Shared
libraries an
A program using HUGE_VAL will compile with a warning when compiled with
g++-3.3 -pedantic (g++-3.3 (GCC) 3.3.2 (Debian)).
How to reproduce:
Save the following program as "test.cpp".
/* snip */
#include <math.h>
int main(int argc,char **argv)
{
double x = HUGE_VAL;
return 0;
}
/* snip */
compile it as follows:
$ g++-3.3 -pedantic test.cpp
g++ will issue the following warning:
test.cpp:5:14: Warnung: use of C99 hexadecimal floating constant
--- End Message ---
--- Begin Message ---
fixed 231748 4.0.2-1
stop
Hello,
Thanks for the detailed bug reports and your interest in improving
Debian. Sorry that the bug was unattended for so long. I'm just
doing some cleanup, I am not involved with the GCC package.
I tried to reproduce the bug and can not (gcc-4.7.0 here), and neither
could other people with previous versions; and indeed it's marked as
fixed in upstream's bug tracker.
So I think that it's better to close it by now. Please reopen it if
you still have concerns about it.
Regards.
--- End Message ---
