Package: osgcal
Version: 0.1.46-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 osgcal_0.1.46-2 on em64t by sbuild/amd64 0.53
...
>  g++ -DHAVE_CONFIG_H -I. -I. -I. -g -Wall -O2 -I./include 
> -I/usr/include/libxml2 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -g 
> -Wall -O2 -c src/osgCal/HardwareModel.cpp  -fPIC -DPIC -o 
> .libs/HardwareModel.o
> In file included from src/osgCal/HardwareModel.cpp:17:
> ./include/osgCal/CustomAssert:57: warning: type qualifiers ignored on 
> function return type
> src/osgCal/HardwareModel.cpp: In member function 'int 
> osgCal::GlueCalHardwareModel::addVertex(osgCal::GlueCalHardwareModel::CalHardwareMesh&,
>  int, CalCoreSubmesh*, int)':
> src/osgCal/HardwareModel.cpp:762: error: 'memcpy' was not declared in this 
> scope
> src/osgCal/HardwareModel.cpp:773: error: 'memset' was not declared in this 
> scope
> src/osgCal/HardwareModel.cpp:784: error: 'memset' was not declared in this 
> scope
> src/osgCal/HardwareModel.cpp:801: error: 'memset' was not declared in this 
> scope
> make[3]: *** [HardwareModel.lo] Error 1
> make[3]: Leaving directory `/build/tbm/osgcal-0.1.46'

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