Package: kflog
Version: 2.1.1-3.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.  GCC 4.3 has converted a number
of warnings into errors.  With GCC 4.3, you're no longer to
just redefine a previous #define.  You need to either avoid
redefinitions directly or to use #ifndef to make sure that something
has not been defined already.  See
http://www.cyrius.com/journal/gcc/gcc-4.3-pedwarn.html

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 kflog_2.1.1-3.1 on em64t by sbuild/amd64 0.53
...
> mkdir .libs
> g++ -DHAVE_CONFIG_H -I. -I/build/tbm/kflog-2.1.1/./kflog/kfrfil -I../.. 
> -I/usr/include/kde -I/usr/share/qt3/include -I. -DQT_THREAD_SUPPORT 
> -D_REENTRANT -DNDEBUG -DNO_DEBUG -O2 -g -Wall -O2 -fno-exceptions 
> -fno-check-new -c /build/tbm/kflog-2.1.1/./kflog/kfrfil/filser.cpp  -fPIC 
> -DPIC -o .libs/filser.o
> /build/tbm/kflog-2.1.1/./kflog/kfrfil/filser.cpp:18:1: error: "_GNU_SOURCE" 
> redefined
> <command-line>: error: this is the location of the previous definition
> In file included from 
> /build/tbm/kflog-2.1.1/./kflog/kfrfil/../projectionlambert.h:21,
>                  from /build/tbm/kflog-2.1.1/./kflog/kfrfil/../mapmatrix.h:24,
>                  from 
> /build/tbm/kflog-2.1.1/./kflog/kfrfil/../basemapelement.h:25,
>                  from 
> /build/tbm/kflog-2.1.1/./kflog/kfrfil/../singlepoint.h:21,
>                  from 
> /build/tbm/kflog-2.1.1/./kflog/kfrfil/../radiopoint.h:21,
>                  from /build/tbm/kflog-2.1.1/./kflog/kfrfil/../airport.h:21,
>                  from /build/tbm/kflog-2.1.1/./kflog/kfrfil/filser.cpp:30:

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