Package: cal3d
Version: 0.11.0-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 cal3d_0.11.0-2 on em64t by sbuild/amd64 0.53
...
> /bin/sh ../../libtool --tag=CXX --mode=compile x86_64-linux-gnu-g++ 
> -DHAVE_CONFIG_H -I. -I. -I../.. -I../../src  -I../../src  -Wall -g -fPIC -O2 
> -fno-rtti -c -o hardwaremodel.lo hardwaremodel.cpp
>  x86_64-linux-gnu-g++ -DHAVE_CONFIG_H -I. -I. -I../.. -I../../src -I../../src 
> -Wall -g -fPIC -O2 -fno-rtti -c hardwaremodel.cpp  -fPIC -DPIC -o 
> .libs/hardwaremodel.o
> hardwaremodel.cpp: In member function 'int 
> CalHardwareModel::addVertex(CalHardwareModel::CalHardwareMesh&, int, 
> CalCoreSubmesh*, int)':
> hardwaremodel.cpp:754: error: 'memcpy' was not declared in this scope
> hardwaremodel.cpp:765: error: 'memset' was not declared in this scope
> hardwaremodel.cpp:776: error: 'memset' was not declared in this scope
> hardwaremodel.cpp:793: error: 'memset' was not declared in this scope
> make[4]: *** [hardwaremodel.lo] Error 1
> make[4]: Leaving directory `/build/tbm/cal3d-0.11.0/src/cal3d'

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