Package: sdcv
Version: 0.4.2-8
User: [EMAIL PROTECTED]
Usertags: ftbfs-gcc-4.4
Tags: patch

Your package fails to build with the upcoming GCC 4.4.  Version 4.4
has not been released yet but I'm building with a snapshot in order
to find errors and give people an advance warning.

GCC 4.4 cleaned up some more C++ headers.  You always have to #include
headers directly and cannot rely for things to be included indirectly.

You can reproduce this problem with gcc-snapshot from unstable.

> Automatic build of sdcv_0.4.2-8 on em64t by sbuild/amd64 0.53
...
> g++ -DLOCALEDIR=\"/usr/share/locale\" -DHAVE_CONFIG_H -I. -I. -I.. -Wall 
> -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include    -I.. -Ilib    -g -O2 
> -c -o readline.o readline.cpp
> g++ -DLOCALEDIR=\"/usr/share/locale\" -DHAVE_CONFIG_H -I. -I. -I.. -Wall 
> -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include    -I.. -Ilib    -g -O2 
> -c -o utils.o utils.cpp
> utils.cpp: In function 'bool stdio_getline(FILE*, std::string&)':
> utils.cpp:35: error: 'fgetc' was not declared in this scope
> utils.cpp:35: error: 'EOF' was not declared in this scope
> utils.cpp:37: error: 'EOF' was not declared in this scope
> utils.cpp: In function 'std::string utf8_to_locale_ign_err(const 
> std::string&)':
> utils.cpp:55: error: 'stderr' was not declared in this scope
> utils.cpp:55: error: 'fprintf' was not declared in this scope
> utils.cpp: In function 'char* locale_to_utf8(const char*)':
> utils.cpp:77: error: 'stderr' was not declared in this scope
> utils.cpp:77: error: 'fprintf' was not declared in this scope
> make[4]: *** [utils.o] Error 1
> make[4]: Leaving directory `/build/tbm/sdcv-0.4.2/src'

--- src/utils.cpp~      2008-11-11 20:06:13.000000000 +0000
+++ src/utils.cpp       2008-11-11 20:06:23.000000000 +0000
@@ -22,6 +22,7 @@
 #  include "config.h"
 #endif
 
+#include <cstdio>
 #include <cstdlib>
 #include <glib.h>
 #include <glib/gi18n.h>

-- 
Martin Michlmayr
http://www.cyrius.com/



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

Reply via email to