[prev in list] [next in list] [prev in thread] [next in thread]
List: pykde
Subject: Re: [PyKDE] PyKDE fails to compile on Debian
From: Jim Bublitz <jbublitz () nwinternet ! com>
Date: 2006-03-12 18:00:06
Message-ID: 200603121000.06852.jbublitz () nwinternet ! com
[Download RAW message or body]
On Sunday 12 March 2006 08:35, Gudjon I. Gudjonsson wrote:
> sipkdecorepart0.o sipkdecorepart0.cpp
> sip/kdecore/ktimezones.sip: In function 'PyObject*
> convertFrom_ZoneMap(void*)':
> /usr/include/kde/ktimezones.h:191: error: 'KTimezone::KTimezone(const
> KTimezone&)' is private
> sip/kdecore/ktimezones.sip:209: error: within this context
> sipkdecorepart0.cpp: In function 'void* init_KTimezones(sipWrapper*,
> PyObject*, sipWrapper**)':
> /usr/include/kde/ktimezones.h:340: error: 'KTimezones::KTimezones(const
> KTimezones&)' is private
> sipkdecorepart0.cpp:9497: error: within this context
> sipkdecorepart0.cpp: In function 'void* init_KTimezone(sipWrapper*,
> PyObject*, sipWrapper**)':
> /usr/include/kde/ktimezones.h:191: error: 'KTimezone::KTimezone(const
> KTimezone&)' is private
> sipkdecorepart0.cpp:10450: error: within this context
According to the "official" KDE 3.5.0/3.5.1 source from kde.org,
KTimezone::KTimezone(const KTimezone&) isn't private. In fact it's implicit
(not declared at all as far as I can tell).
Can you check the KDE ktimezones.h that's being included when you
build/compile and see if/how the copy constructor is declared there? Looks
like a difference in KDE source files.
Jim
_______________________________________________
PyKDE mailing list PyKDE@mats.imk.fraunhofer.de
http://mats.imk.fraunhofer.de/mailman/listinfo/pykde
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic