Package: shaketracker
Version: 0.4.6-5
Usertags: ftbfs-gcc-4.3

Your package fails to build with GCC 4.3.  Version 4.3 has not been
released yet but I'm building with a snapshot in order to find errors
and give people an advance warning.  In GCC 4.3, the C++ header
dependencies have been cleaned up.  The advantage of this is that
programs will compile faster.  The downside is that you actually
need to directly #include everything you use (but you really should
do this anyway, otherwise your program won't work with any compiler
other than GCC).  There's some more information about this at
http://www.cyrius.com/journal/2007/05/10#gcc-4.3-include

You can reproduce this problem with gcc-snapshot from unstable.  Note
that Red Hat, Novell and Ubuntu have done some work getting packages
to build with GCC 4.3 so there might be patches floating around
somewhere.  I suggest you talk to your upstream.


> Automatic build of shaketracker_0.4.6-5 on em64t by sbuild/amd64 0.53
...
> g++ -DPACKAGE_NAME=\"\" -DPACKAGE_TARNAME=\"\" -DPACKAGE_VERSION=\"\" 
> -DPACKAGE_STRING=\"\" -DPACKAGE_BUGREPORT=\"\" -DPACKAGE=\"shaketracker\" 
> -DVERSION=\"0.4.6\"  -I. -I.      -I/usr/lib/sigc++-1.0/include 
> -I/usr/include/sigc++-1.0 -I/usr/lib/gtkmm/include -I/usr/include/gtk-1.2 
> -I/usr/include/glib-1.2 -I/usr/lib/glib/include -I/usr/lib/sigc++-1.0/include 
> -I/usr/include/sigc++-1.0  -DPOSIX_ENABLED   -DALSA_ENABLED  -g3 -c 
> file_writer.cpp
> file_writer.cpp: In member function 'void 
> File_Writer::store_pascal_string(const char*)':
> file_writer.cpp:121: error: 'strlen' was not declared in this scope
> make[2]: *** [file_writer.o] Error 1
> make[2]: Leaving directory 
> `/build/tbm/shaketracker-0.4.6/build-tree/shaketracker-0.4.6/trackercore'
> make[1]: *** [all-recursive] Error 1
> make[1]: Leaving directory 
> `/build/tbm/shaketracker-0.4.6/build-tree/shaketracker-0.4.6'

-- 
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