Package: libcoyotl
Version: libcoyotl-3.1-4
Usertags: ftbfs-gcc-4.3
Tags: patch

Your package causes other packages to fail 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).  Some background of this can be found at
http://gcc.gnu.org/PR28080

You can reproduce this problem with gcc-snapshot from unstable.
I'm including a patch for the problem below, but I'm not sure whether
are more problems.

> Automatic build of acovea_5.1.1-2 on coconut0 by sbuild/ia64 0.49
...
>  ia64-linux-gnu-g++ -I. -I. -I. -I. -I.. -DACOVEA_VERSION=\"5.1.1\" 
> -DACOVEA_CONFIG_DIR=\"/usr/share//libacovea/config/\" 
> -DACOVEA_BENCHMARK_DIR=\"/usr/share//libacovea/benchmarks/\" -g -O2 -MT 
> acovea.lo -MD -MP -MF .deps/acovea.Tpo -c acovea.cpp  -fPIC -DPIC -o 
> .libs/acovea.o
> In file included from acovea.cpp:36:
> acovea.h:422: warning: 'typedef' was ignored in this declaration
> acovea.h:630: warning: 'typedef' was ignored in this declaration
> acovea.h:636: warning: 'typedef' was ignored in this declaration
> In file included from acovea.cpp:40:
> /usr/include/libcoyotl/sortutil.h: In function 'void 
> libcoyotl::quick_sort(T*, size_t)':
> /usr/include/libcoyotl/sortutil.h:138: error: 'CHAR_BIT' was not declared in 
> this scope


--- libcoyotl/sortutil.h~       2007-04-01 14:17:36.000000000 +0000
+++ libcoyotl/sortutil.h        2007-04-01 14:18:01.000000000 +0000
@@ -36,6 +36,7 @@
 #if !defined(LIBCOYOTL_SORTUTIL_H)

 #define LIBCOYOTL_SORTUTIL_H

 

+#include <climits>

 #include <stdexcept>

 

 namespace libcoyotl


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