Package: blackbox
Version: 0.70.1-2
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 blackbox_0.70.1-2 on em64t by sbuild/amd64 0.53
...
> if /bin/sh ../libtool --tag=CXX --mode=compile x86_64-linux-gnu-g++ 
> -DHAVE_CONFIG_H -I. -I. -I..  -DSHAPE -DMITSHM -DXFT  -DNLS 
> -DLOCALEPATH=\"/usr/share/blackbox/nls\" -I/usr/include -I/usr/local/include  
> -g -O2 -I/usr/include/freetype2   -MT Image.lo -MD -MP -MF ".deps/Image.Tpo" 
> -c -o Image.lo Image.cc; \
>       then mv -f ".deps/Image.Tpo" ".deps/Image.Plo"; else rm -f 
> ".deps/Image.Tpo"; exit 1; fi
>  x86_64-linux-gnu-g++ -DHAVE_CONFIG_H -I. -I. -I.. -DSHAPE -DMITSHM -DXFT 
> -DNLS -DLOCALEPATH=\"/usr/share/blackbox/nls\" -I/usr/include 
> -I/usr/local/include -g -O2 -I/usr/include/freetype2 -MT Image.lo -MD -MP -MF 
> .deps/Image.Tpo -c Image.cc  -fPIC -DPIC -o .libs/Image.o
> Image.cc: In member function 'void bt::Image::hgradient(const bt::Color&, 
> const bt::Color&, bool)':
> Image.cc:1350: error: 'memcpy' was not declared in this scope
> make[3]: *** [Image.lo] Error 1
> make[3]: Leaving directory `/build/tbm/blackbox-0.70.1/lib'

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