Source: fltk1.1 Version: 1.1.10-7 Severity: serious Tags: wheezy sid User: [email protected] Usertags: qa-ftbfs-20110923 qa-ftbfs hardening-format-security hardening Justification: FTBFS on amd64
Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part: > g++ -I.. -g -O2 -fstack-protector --param=ssp-buffer-size=4 > -D_FORTIFY_SOURCE=2 -Wformat -Wformat-security -Werror=format-security -Wall > -Wunused -Wno-format-y2k -fPIC -fno-strict-aliasing -D_THREAD_SAFE > -D_REENTRANT -I/usr/include/freetype2 -I/usr/include/freetype2 -g -O2 > -fstack-protector --param=ssp-buffer-size=4 -D_FORTIFY_SOURCE=2 -Wformat > -Wformat-security -Werror=format-security -c Fl_File_Chooser2.cxx > Fl_File_Chooser2.cxx: In member function 'void Fl_File_Chooser::fileNameCB()': > Fl_File_Chooser2.cxx:572:35: error: format not a string literal and no format > arguments [-Werror=format-security] > Fl_File_Chooser2.cxx: In member function 'void Fl_File_Chooser::newdir()': > Fl_File_Chooser2.cxx:760:48: error: format not a string literal and no format > arguments [-Werror=format-security] > Fl_File_Chooser2.cxx: In member function 'void > Fl_File_Chooser::showChoiceCB()': > Fl_File_Chooser2.cxx:931:55: error: format not a string literal and no format > arguments [-Werror=format-security] > cc1plus: some warnings being treated as errors > > make[3]: *** [Fl_File_Chooser2.o] Error 1 The full build log is available from: http://people.debian.org/~lucas/logs/2011/09/23/fltk1.1_1.1.10-7_lsid64.buildlog This happened because since dpkg 1.16.0 [0], hardening flags are enabled under various conditions. [0] http://lists.debian.org/debian-devel-announce/2011/09/msg00001.html A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on about 50 AMD64 nodes of the Grid'5000 platform, using a clean chroot. Internet was not accessible from the build systems. -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
