Re: KDE broken on CURRENT (with gcc3.2)
On Tuesday 03 September 2002 09:28 pm, Michael WARDLE wrote: I have the exact same problem (even with fam-2.6.9). Can you post that patch? There was an error with FAM and GCC 3.1 discussed here: http://oss.sgi.com/projects/fam/archive/msg00452.html If this is the problem you are seeing, try removing the const modifier from Scheduler.h in the FAM sources. If anyone can suggest why this is a FAM bug (rather than a GCC bug), I might be able to make the required changes in FAM. Hope this helps That problem in the archive is exactly the same as what's happening with fam and gcc3.2. As for the Scheduler.h my knowledge of c++ isn't up to hacking that file. Beech To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: KDE broken on CURRENT (with gcc3.2)
On Tue, 3 Sep 2002, Alexander Kabaev wrote: ... The patch is not mine. I extracted it from GCC FSF CVS repository. -- Alexander Kabaev Could you please commit it to -current? It seems to do its job in that area. Bye! Michael Reifenberger ^.*Plaut.*$, IT, R/3 Basis, GPS To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: KDE broken on CURRENT (with gcc3.2)
On Tue, 3 Sep 2002, Beech Rintoul wrote:
Date: Tue, 3 Sep 2002 23:53:05 -0800
From: Beech Rintoul [EMAIL PROTECTED]
To: Michael WARDLE [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Subject: Re: KDE broken on CURRENT (with gcc3.2)
On Tuesday 03 September 2002 09:28 pm, Michael WARDLE wrote:
I have the exact same problem (even with fam-2.6.9).
Can you post that patch?
There was an error with FAM and GCC 3.1 discussed here:
http://oss.sgi.com/projects/fam/archive/msg00452.html
If this is the problem you are seeing, try removing the
const modifier from Scheduler.h in the FAM sources.
removing the const modifier fixes the compilation error
of fam with -current's gcc for me.
The diff is:
--- Scheduler.h.origThu Sep 5 00:20:53 2002
+++ Scheduler.h Thu Sep 5 00:21:34 2002
@@ -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) :
Bye!
Michael Reifenberger
^.*Plaut.*$, IT, R/3 Basis, GPS
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
KDE broken on CURRENT (with gcc3.2)
Hi all, I reported this to kde@, but got no answer back (yet). I deleted _ALL_ ports, removed /usr/local/include, removed /usr/X11R6. I also removed /usr/include and reinstalled a fresh compiled world. X11R6 and QT are fresh built from sources. Same code compiles fine with gcc3.1. Can anybody with C++ knowledge help here ? ports/audio/arts c++ -DHAVE_CONFIG_H -I. -I. -I.. -I../mcop -I/usr/local/include -I/usr/X11R6/inc lude -I../libltdl -pthread -DQT_THREAD_SUPPORT -L/usr/local/lib -I/usr/local/inc lude -I/usr/local/include -I/usr/X11R6/include -D_THREAD_SAFE -DNDEBUG -DNO_DEBU G -O2 -O -pipe -fno-exceptions -fno-check-new -ftemplate-depth-99 -c qiomanager. cc -MT qiomanager.lo -MD -MP -MF .deps/qiomanager.TPlo -fPIC -DPIC -o .libs/qio manager.o In file included from qiomanager.cc:308: qiomanager_p.moc:28: no `void Arts::QIOWatch::initMetaObject()' member function declared in class `Arts::QIOWatch' qiomanager_p.moc: In member function `void Arts::QIOWatch::initMetaObject()': qiomanager_p.moc:32: `badSuperclassWarning' undeclared (first use this function) qiomanager_p.moc:32: (Each undeclared identifier is reported only once for each function it appears in.) qiomanager_p.moc:34: no method `QObject::initMetaObject' qiomanager_p.moc:39: `struct QMetaData' has no member named `ptr' qiomanager_p.moc:39: `QMember' undeclared (first use this function) qiomanager_p.moc:39: syntax error before `)' token qiomanager_p.moc:42: no matching function for call to `QMetaObject::QMetaObject (const char[9], const char[8], QMetaData*, int, int, int)' /usr/X11R6/include/qmetaobject.h:226: candidates are: QMetaObject::QMetaObject(const QMetaObject) /usr/X11R6/include/qmetaobject.h:147: QMetaObject::QMetaObject(const char*, QMetaObject*, const QMetaData*, int, const QMetaData*, int, const QMetaProperty*, int, const QMetaEnum*, int, const QClassInfo*, int) In file included from qiomanager.cc:308: qiomanager_p.moc: At global scope: qiomanager_p.moc:54: no `void Arts::QTimeWatch::initMetaObject()' member function declared in class `Arts::QTimeWatch' qiomanager_p.moc: In member function `void Arts::QTimeWatch::initMetaObject()': qiomanager_p.moc:60: no method `QObject::initMetaObject' qiomanager_p.moc:65: `struct QMetaData' has no member named `ptr' qiomanager_p.moc:65: syntax error before `)' token qiomanager_p.moc:68: no matching function for call to `QMetaObject::QMetaObject (const char[11], const char[8], QMetaData*, int, int, int)' /usr/X11R6/include/qmetaobject.h:226: candidates are: QMetaObject::QMetaObject(const QMetaObject) /usr/X11R6/include/qmetaobject.h:147: QMetaObject::QMetaObject(const char*, QMetaObject*, const QMetaData*, int, const QMetaData*, int, const QMetaProperty*, int, const QMetaEnum*, int, const QClassInfo*, int) gmake[2]: *** [qiomanager.lo] Error 1 gmake[2]: Leaving directory `/usr/ports/audio/arts/work/arts-1.0.3/qtmcop' gmake[1]: *** [all-recursive] Error 1 gmake[1]: Leaving directory `/usr/ports/audio/arts/work/arts-1.0.3' gmake: *** [all-recursive-am] Error 2 *** Error code 2 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 Martin Martin Blapp, [EMAIL PROTECTED] [EMAIL PROTECTED] -- ImproWare AG, UNIXSP ISP, Zurlindenstrasse 29, 4133 Pratteln, CH Phone: +41 061 826 93 00: +41 61 826 93 01 PGP: finger -l [EMAIL PROTECTED] PGP Fingerprint: B434 53FC C87C FE7B 0A18 B84C 8686 EF22 D300 551E -- To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: KDE broken on CURRENT (with gcc3.2)
Folks, ports/audio/arts I got this one solved by rm /usr/ports. It was a stale patch :/ 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. Martin To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: KDE broken on CURRENT (with gcc3.2)
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. regards, -- wca To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: KDE broken on CURRENT (with gcc3.2)
Hi, That's not KDE domain, though. We only depend on FAM. Of course ;-) But the arts problem I fixed - sigh - was a KDE problem. I just listed this one too. Martin To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: KDE broken on CURRENT (with gcc3.2)
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
Re: KDE broken on CURRENT (with gcc3.2)
On Tue, 2002-09-03 at 19:01, Alan E wrote: 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? gcc-3.2 is the new compiler in -CURRENT as of two days ago. Joe -- 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 -- PGP Key : http://www.marcuscom.com/pgp.asc To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: KDE broken on CURRENT (with gcc3.2)
I can confirm that kde3 doesn't build on -CURRENT with gcc 3.2.1 as well, but it has never worked for me on gcc 3.1 either. Ken To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: KDE broken on CURRENT (with gcc3.2)
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? gcc-3.2 on -CURRENT is the compiler that is default. Ken To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: KDE broken on CURRENT (with gcc3.2)
I am experiencing this behavior as well (can't compile kde3 with gcc 3.2.1 or 3.1). However, with Alexander Kabaev's gcc 3.2 patch to cp-lang.c, kdelibs compiles ok and I can get kdebase to install by doing a 'make -k install'. Not sure exactly what's broken in the process, but it seems usable so far. On Tue, 3 Sep 2002, Kenneth Culver ([EMAIL PROTECTED]) wrote: I can confirm that kde3 doesn't build on -CURRENT with gcc 3.2.1 as well, but it has never worked for me on gcc 3.1 either. Ken To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: KDE broken on CURRENT (with gcc3.2)
On Wed, 4 Sep 2002 20:59:20 + Michael Johnson [EMAIL PROTECTED] wrote: I am experiencing this behavior as well (can't compile kde3 with gcc 3.2.1 or 3.1). However, with Alexander Kabaev's gcc 3.2 patch to cp-lang.c, kdelibs compiles ok and I can get kdebase to install by doing The patch is not mine. I extracted it from GCC FSF CVS repository. -- Alexander Kabaev To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: KDE broken on CURRENT (with gcc3.2)
On Tuesday 03 September 2002 06:16 pm, Alexander Kabaev wrote: On Wed, 4 Sep 2002 20:59:20 + Michael Johnson [EMAIL PROTECTED] wrote: I am experiencing this behavior as well (can't compile kde3 with gcc 3.2.1 or 3.1). However, with Alexander Kabaev's gcc 3.2 patch to cp-lang.c, kdelibs compiles ok and I can get kdebase to install by doing The patch is not mine. I extracted it from GCC FSF CVS repository. I have the exact same problem (even with fam-2.6.9). Can you post that patch? Beech To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: KDE broken on CURRENT (with gcc3.2)
I have the exact same problem (even with fam-2.6.9). Can you post that patch? There was an error with FAM and GCC 3.1 discussed here: http://oss.sgi.com/projects/fam/archive/msg00452.html If this is the problem you are seeing, try removing the const modifier from Scheduler.h in the FAM sources. If anyone can suggest why this is a FAM bug (rather than a GCC bug), I might be able to make the required changes in FAM. Hope this helps -- MICHAEL WARDLE SGI Desktop and Sysadmin Software Adacel Technologies Limited To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
