Package: boolstuff Version: 0.1.11-1 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 boolstuff_0.1.11-1 on em64t by sbuild/amd64 0.53 ... > make[3]: Entering directory `/build/tbm/boolstuff-0.1.11/src/commands' > if x86_64-linux-gnu-g++ -DPACKAGE_NAME=\"\" -DPACKAGE_TARNAME=\"\" > -DPACKAGE_VERSION=\"\" -DPACKAGE_STRING=\"\" -DPACKAGE_BUGREPORT=\"\" > -DPACKAGE=\"boolstuff\" -DVERSION=\"0.1.11\" -DSTDC_HEADERS=1 > -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 > -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 > -DHAVE_UNISTD_H=1 -DHAVE_DLFCN_H=1 -DHAVE_GETOPT_LONG=1 -DHAVE_NAMESPACES= > -DHAVE_STD= -DHAVE_SSTREAM= -I. -I. -I../../src > -DCOMMAND_NAME=\"booldnf\" -g -O2 -Wall -MT booldnf-booldnf.o -MD -MP -MF > ".deps/booldnf-booldnf.Tpo" -c -o booldnf-booldnf.o `test -f 'booldnf.cpp' || > echo './'`booldnf.cpp; \ > then mv -f ".deps/booldnf-booldnf.Tpo" ".deps/booldnf-booldnf.Po"; else > rm -f ".deps/booldnf-booldnf.Tpo"; exit 1; fi > booldnf.cpp: In function 'int main(int, char**)': > booldnf.cpp:101: error: 'EOF' was not declared in this scope > booldnf.cpp:116: error: 'EOF' was not declared in this scope > make[3]: *** [booldnf-booldnf.o] Error 1 > make[3]: Leaving directory `/build/tbm/boolstuff-0.1.11/src/commands' --- src/commands/booldnf.cpp~ 2008-11-07 16:49:44.000000000 +0000 +++ src/commands/booldnf.cpp 2008-11-07 16:49:54.000000000 +0000 @@ -32,6 +32,7 @@ #include <getopt.h> #endif +#include <cstdio> #include <iostream> using namespace std; -- Martin Michlmayr http://www.cyrius.com/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
