Compilation error when building FAM with gcc 3.2

Billy O'Connor billy at
Fri Sep 6 14:17:45 PDT 2002

Vassili Dzuba <vassilidzuba at> writes:

> When trying to compile FAM in a chrooted environment build using the current LFS
> packages (including gcc3.2)n i obtain the error message :
> c++ -DHAVE_CONFIG_H -I. -I. -I.. -I../include -DCONFIG_ETC_CONFIG_PATH=\"/usr/etc/fam.conf\"    -g -O2 -c Scheduler.c++
> Scheduler.c++:37: uninitialized const member `Scheduler::IOTypeInfo::iotype'
> Scheduler.c++:38: uninitialized const member `Scheduler::IOTypeInfo::iotype'
> make[2]: *** [Scheduler.o] Error 1

There are 3 open gcc3 bugs concerning const initialization, I don't
know if they have anything to do with this or not, would you try this
small patch?

diff -Naur ./fam/Scheduler.h ../fam-2.6.9-new/fam/Scheduler.h
--- ./fam/Scheduler.h	2002-07-16 02:14:41.000000000 -0400
+++ ../fam-2.6.9-new/fam/Scheduler.h	2002-08-31 08:29:32.000000000 -0400
@@ -105,7 +105,7 @@
     //  for the corresponding I/O type.
     struct IOTypeInfo {
-	FDInfo::FDIOHandler FDInfo::*const iotype;
+	FDInfo::FDIOHandler FDInfo::* iotype;
 	unsigned int nbitsset;		// number of bits set in fds
 	fd_set fds;
 	IOTypeInfo(FDInfo::FDIOHandler FDInfo::* a_iotype) :

Unsubscribe: send email to listar at
and put 'unsubscribe blfs-dev' in the subject header of the message

More information about the blfs-dev mailing list