On Tue, Sep 03, 2002 at 02:29:12PM -0700, Will Andrews wrote: >On Tue, Sep 03, 2002 at 11:30:02PM +0200, Martin Blapp wrote: >> > ports/devel/fam >> > --------------- >> > >> > c++ -DHAVE_CONFIG_H -I. -I. -I.. -I../include -DCONFIG_ETC_CONFIG_PATH=\"/usr/lo >> > cal/etc/fam.conf\" -O -pipe -c RPC_TCP_Connector.c++ >> > c++ -DHAVE_CONFIG_H -I. -I. -I.. -I../include -DCONFIG_ETC_CONFIG_PATH=\"/usr/lo >> > cal/etc/fam.conf\" -O -pipe -c Scanner.c++ >> > c++ -DHAVE_CONFIG_H -I. -I. -I.. -I../include -DCONFIG_ETC_CONFIG_PATH=\"/usr/lo >> > cal/etc/fam.conf\" -O -pipe -c Scheduler.c++ >> > Scheduler.c++:37: uninitialized const member `Scheduler::IOTypeInfo::iotype' >> > Scheduler.c++:38: uninitialized const member `Scheduler::IOTypeInfo::iotype' >> > gmake[2]: *** [Scheduler.o] Error 1 >> > gmake[2]: Leaving directory `/usr/ports/devel/fam/work/fam-2.6.8/fam' >> > gmake[1]: *** [all-recursive] Error 1 >> > gmake[1]: Leaving directory `/usr/ports/devel/fam/work/fam-2.6.8' >> > gmake: *** [all-recursive-am] Error 2 >> > *** Error code 2 >> > >> >> Is still broken. > >That's not KDE domain, though. We only depend on FAM.
I'm the maintainer, Will. Since I don't have a -CURRENT system, is one of the hasta's set up to test -CURRENT patches on? I can make a good guess at it from looking at the code, but it'll need to be tested somewhere. Also, is gcc-3.2 on -CURRENT a supported configuration? -- AlanE KDE-FreeBSD Team (http://freebsd.kde.org/) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
