Package: ois
Version: 0.99+1.0rc1-1
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 ois_0.99+1.0rc1-1 on em64t by sbuild/amd64 0.53
...
> /bin/sh ../libtool --tag=CXX   --mode=compile g++ -DHAVE_CONFIG_H -I. 
> -I../includes  -I../includes -g -O2 -I/usr/X11R6/include    -g -O2 -MT 
> EventHelpers.lo -MD -MP -MF .deps/EventHelpers.Tpo -c -o EventHelpers.lo 
> `test -f './linux/EventHelpers.cpp' || echo './'`./linux/EventHelpers.cpp
>  g++ -DHAVE_CONFIG_H -I. -I../includes -I../includes -g -O2 
> -I/usr/X11R6/include -g -O2 -MT EventHelpers.lo -MD -MP -MF 
> .deps/EventHelpers.Tpo -c ./linux/EventHelpers.cpp  -fPIC -DPIC -o 
> .libs/EventHelpers.o
> ./linux/EventHelpers.cpp: In function 'DeviceComponentInfo 
> getComponentInfo(int)':
> ./linux/EventHelpers.cpp:53: error: 'memset' was not declared in this scope
> ./linux/EventHelpers.cpp: In static member function 'static void 
> OIS::EventUtils::enumerateForceFeedback(int, OIS::LinuxForceFeedback**)':
> ./linux/EventHelpers.cpp:218: error: 'memset' was not declared in this scope
> make[2]: *** [EventHelpers.lo] Error 1

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