Package: xarchon
Version: 0.50-10.1
Usertags: ftbfs-gcc-4.3
Tags: patch

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).  Some background of this can be found at
http://gcc.gnu.org/PR28080

You can reproduce this problem with gcc-snapshot (20070326-1 or higher)
from unstable. (Currently not available for i386, but for amd64, powerpc
and ia64.  I hope to have i386 binaries in the archive in ~3 weeks.)

> Automatic build of xarchon_0.50-10.1 on coconut0 by sbuild/ia64 0.49
...
> c++ -DHAVE_CONFIG_H -I. -I. -I.. -I/usr/include/gtk-1.2 
> -I/usr/include/glib-1.2 -I/usr/lib/glib/include  -I../    -g -O2 -Wall -c 
> Xarchon_Problem.cpp
> In file included from Xarchon_Genetic.hpp:6,
>                  from Xarchon_Interface.hpp:6,
>                  from Xarchon_Problem.cpp:2:
> Genetic.hpp: In member function 'T* Genetic_Population<T>::Choose_State()':
> Genetic.hpp:172: error: there are no arguments to 'rand' that depend on a 
> template parameter, so a declaration of 'rand' must be available
> Genetic.hpp:172: error: (if you use '-fpermissive', G++ will accept your 
> code, but allowing the use of an undeclared name is deprecated)
> Genetic.hpp: In member function 'virtual Genetic_Operator<T>* 
> Genetic_Generation<T>::Choose_Operator()':

--- src/Genetic.hpp~    2007-04-04 14:13:35.000000000 +0000
+++ src/Genetic.hpp     2007-04-04 14:13:41.000000000 +0000
@@ -1,6 +1,7 @@
 #ifndef GENETIC_HPP
 #define GENETIC_HPP
 
+#include <cstdlib>
 #include <list>
 using namespace std;
 

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