Scanning dependencies of target python_module_PyKDE4_marble
[ 99%] [ 99%] [ 99%] Building CXX object marble/src/bindings/python/CMakeFiles/python_module_PyKDE4_marble.dir/sip/sipmarblepart1.o
Building CXX object marble/src/bindings/python/CMakeFiles/python_module_PyKDE4_marble.dir/sip/sipmarblepart0.o
Building CXX object marble/src/bindings/python/CMakeFiles/python_module_PyKDE4_marble.dir/sip/sipmarblepart2.o
In file included from /usr/include/python2.6/Python.h:8:0,
from /usr/include/python2.6/sip.h:32,
from /var/tmp/portage/kde-base/marble-9999/work/marble-9999_build/marble/src/bindings/python/sip/sipAPImarble.h:11,
from /var/tmp/portage/kde-base/marble-9999/work/marble-9999_build/marble/src/bindings/python/sip/sipmarblepart1.cpp:7:
/usr/include/python2.6/pyconfig.h:1079:0: warning: "_XOPEN_SOURCE" redefined
<command-line>:0:0: note: this is the location of the previous definition
In file included from /usr/include/python2.6/Python.h:8:0,
from /usr/include/python2.6/sip.h:32,
from /var/tmp/portage/kde-base/marble-9999/work/marble-9999_build/marble/src/bindings/python/sip/sipAPImarble.h:11,
from /var/tmp/portage/kde-base/marble-9999/work/marble-9999_build/marble/src/bindings/python/sip/sipmarblepart0.cpp:7:
/usr/include/python2.6/pyconfig.h:1079:0: warning: "_XOPEN_SOURCE" redefined
<command-line>:0:0: note: this is the location of the previous definition
In file included from /usr/include/python2.6/Python.h:8:0,
from /usr/include/python2.6/sip.h:32,
from /var/tmp/portage/kde-base/marble-9999/work/marble-9999_build/marble/src/bindings/python/sip/sipAPImarble.h:11,
from /var/tmp/portage/kde-base/marble-9999/work/marble-9999_build/marble/src/bindings/python/sip/sipmarblepart2.cpp:7:
/usr/include/python2.6/pyconfig.h:1079:0: warning: "_XOPEN_SOURCE" redefined
<command-line>:0:0: note: this is the location of the previous definition
sipmarblepart1.cpp: In function 'PyObject* meth_Marble_ViewportParams_focusPointIsCenter(PyObject*, PyObject*)':
sipmarblepart1.cpp:3269:30: error: 'class Marble::ViewportParams' has no member named 'focusPointIsCenter'
sipmarblepart2.cpp: In function 'PyObject* meth_Marble_RenderPluginInterface_pluginInstance(PyObject*, PyObject*)':
sipmarblepart2.cpp:2171:30: error: 'class Marble::RenderPluginInterface' has no member named 'pluginInstance'
sipmarblepart2.cpp: In function 'PyObject* meth_Marble_MarbleWidget_needsUpdate(PyObject*, PyObject*)':
sipmarblepart2.cpp:14310:30: error: 'class Marble::MarbleWidget' has no member named 'needsUpdate'
sipmarblepart2.cpp: In function 'PyObject* meth_Marble_MarbleWidget_setNeedsUpdate(PyObject*, PyObject*)':
sipmarblepart2.cpp:14335:21: error: 'class Marble::MarbleWidget' has no member named 'setNeedsUpdate'
sipmarblepart2.cpp: In function 'PyObject* meth_Marble_MarbleWidget_northPoleY(PyObject*, PyObject*)':
sipmarblepart2.cpp:14363:30: error: 'class Marble::MarbleWidget' has no member named 'northPoleY'
sipmarblepart2.cpp: In function 'PyObject* meth_Marble_MarbleWidget_setProxy(PyObject*, PyObject*)':
sipmarblepart2.cpp:15301:21: error: 'class Marble::MarbleWidget' has no member named 'setProxy'
sipmarblepart2.cpp: In function 'PyObject* meth_Marble_MarbleWidget_proxyHost(PyObject*, PyObject*)':
sipmarblepart2.cpp:15332:42: error: 'class Marble::MarbleWidget' has no member named 'proxyHost'
sipmarblepart2.cpp: In function 'PyObject* meth_Marble_MarbleWidget_proxyPort(PyObject*, PyObject*)':
sipmarblepart2.cpp:15359:30: error: 'class Marble::MarbleWidget' has no member named 'proxyPort'
sipmarblepart2.cpp: In function 'PyObject* meth_Marble_MarbleWidget_user(PyObject*, PyObject*)':
sipmarblepart2.cpp:15386:42: error: 'class Marble::MarbleWidget' has no member named 'user'
sipmarblepart2.cpp: In function 'PyObject* meth_Marble_MarbleWidget_password(PyObject*, PyObject*)':
sipmarblepart2.cpp:15413:42: error: 'class Marble::MarbleWidget' has no member named 'password'
sipmarblepart2.cpp: In function 'PyObject* meth_Marble_MarbleWidget_changeCurrentPosition(PyObject*, PyObject*)':
sipmarblepart2.cpp:16914:21: error: 'class Marble::MarbleWidget' has no member named 'changeCurrentPosition'
sipmarblepart2.cpp: In function 'PyObject* meth_Marble_MarbleWidget_updateGps(PyObject*, PyObject*)':
sipmarblepart2.cpp:16968:21: error: 'class Marble::MarbleWidget' has no member named 'updateGps'
make[2]: *** [marble/src/bindings/python/CMakeFiles/python_module_PyKDE4_marble.dir/sip/sipmarblepart1.o] Error 1
make[2]: *** Waiting for unfinished jobs....
make[2]: *** [marble/src/bindings/python/CMakeFiles/python_module_PyKDE4_marble.dir/sip/sipmarblepart2.o] Error 1
make[1]: *** [marble/src/bindings/python/CMakeFiles/python_module_PyKDE4_marble.dir/all] Error 2
make: *** [all] Error 2
emake failed
* ERROR: kde-base/marble-9999 failed:
* Make failed!
*
* Call stack:
* ebuild.sh, line 56: Called src_compile
* environment, line 6493: Called kde4-meta_src_compile
* environment, line 3876: Called kde4-base_src_compile
* environment, line 3523: Called cmake-utils_src_compile
* environment, line 1726: Called _execute_optionaly 'src_compile'
* environment, line 728: Called enable_cmake-utils_src_compile
* environment, line 2095: Called cmake-utils_src_make
* environment, line 1745: Called die
* The specific snippet of code:
* emake "$@" || die "Make failed!";

I emerged gpsd, but still got the same error, so I figure it must be something sip/python bindings eclass related?
Anyone know how to work around this marble problem? I already had polkit-qt-9999 installed- just today it fails. Need to try again and look at the output.

OK- emerge polkit-qt says:

Code:

-- Could NOT find Policykit (missing: _POLICYKIT_LIBRARY _POLICYKIT_GRANT_LIBRARY _POLICYKIT_DBUS_LIBRARY _POLICYKIT_INCLUDE_DIR)
-- PolicyKit was not found on your system. Skipping compilation of polkit-qt

Guess I'll emerge policykit, but IIRC I had to remove that package some time ago due to some conflict or deprecation problem?

OK- installed policykit, but now polkit-qt bails out at the last moment with this:

Any idea of what to do here? I've looked at the /var/tmp/portage/sys-auth/polkit-qt temp and work files, and the cmake lists in the polkit-qt source files to see if I can stop dodoc wanting README.porting from being in the mix, but have failed so far. Could this be addressed in the ebuild? The latest portage and ovelay polkit-qt ebuilds are similar, but not exactly the same.

Even more confusing, the /usr/portage/distfiles/svn-src/polkit-qt/polkit-qt-1/README.porting file DOES exist. Maybe copy it to another location?

I only want to TRY the new one. I think this was clear. In the end, this is a thread about testing new releases of kde SC, isn't it?

Sorry, I didn't realize there already was a new 2.3 beta.

Anyway, as long as koffice 2.3 has beta status, I wouldn't bother with ebuilds. Especially when it has a track record of breaking stuff, files moving from one package to another, leading to upgrade blocks from one beta to another (and even with RCs). So... better use live ebuilds for now until there's actually an RC around and watch out for user ebuilds on bugs.gentoo.org then._________________backend.cpp:92:2: warning: #warning TODO - this error message is about as useful as a cooling unit in the arctic

I only want to TRY the new one. I think this was clear. In the end, this is a thread about testing new releases of kde SC, isn't it?

Sorry, I didn't realize there already was a new 2.3 beta.

Anyway, as long as koffice 2.3 has beta status, I wouldn't bother with ebuilds. Especially when it has a track record of breaking stuff, files moving from one package to another, leading to upgrade blocks from one beta to another (and even with RCs). So... better use live ebuilds for now until there's actually an RC around and watch out for user ebuilds on bugs.gentoo.org then.

I already know that, but as I said before I can't use the live ebuild for a unknow reason. It's halt in the same point (see my previuos post about that) complaining about a missing file. I had been having this issue for 2 month (so I can't compile any version of the 2.3 series). This is why I ask for a beta ebuild (I yes, I have looked to ebuilds in bug tracker too).

O.o when I say something about polkit? When I said "previos" I'm talking about my previous post (I think it was at the begining of this page, but I'm not sure) Anyway, the error I am talking on koffice-libs is:

So, here it is- anyone run into this, and know what to do? I resynced layman -s kde, and pulled new svn-src files just to be sure (hadn't done so in a while). The bug referenced is over a year old https://bugs.kde.org/show_bug.cgi?id=209903 and seems to refer to a qt problem. Do I need to update qting-edge and recompile all my qt packages, or is that the wrong track. The "can't find file to patch at input line 10" and "Perhaps you used the wrong -p or --strip option?' would seem more likely. The patch is not missing in the kdelibs overlay ebuild directory- I checked and it is there.

Also, I'm not understanding why kdelibs-4.3.3 is even involved here- this is kde-live (kde-4.6 trunk)?

Does then mean we should go with portage Qt-4.7.0 for portage kde (4.5.3) as well as our overlay kde-live, and do complete kde rebuilds?

I'm currently using Qt 4.7.9999 on my kde-live installation, as it helped solve some previous problems, but my kdelibs klauncher_mac.patch failure mentioned above is still not resolved. I've resynced several times- no fix yet. I'd hate to go back to 4.7.0, and find I again have the other problems, but in general I really don't like running QT 9999 versions with kde-live.

@wrc1944: You don't need to go with it for 4.5.3, also qt-4.6.x still is the best choice if you also plan to compile openoffice with +kde. I'm using 4.7.0 and having GUI display issues in OO, besides no errors. What issues were you facing?_________________backend.cpp:92:2: warning: #warning TODO - this error message is about as useful as a cooling unit in the arctic

@genstorm,
Sorry- should have mentioned I was referring to my ~amd64 kde-live Gentoo partition regarding qt-4.7.0. I unmasked it as soon as it was in portage, and then tried rebuilding kde-live, but ran into a few compiling issues. After going to qting-edge/qt-4.7.9999 as mentioned on the kde-testing thread that resolved those problems (can't recall exactly what they were at the moment). Don't plan on compiling OO.

Then you should stay with qt-4.7.9999 as it is in no way related to your failing patch. Simply remove it from the ebuild. Patches don't get renamed as long as there's no need to adapt to newer sources.

PS: I like to combine major Qt updates with upcoming KDE upgrades._________________backend.cpp:92:2: warning: #warning TODO - this error message is about as useful as a cooling unit in the arctic

Does then mean we should go with portage Qt-4.7.0 for portage kde (4.5.3) as well as our overlay kde-live, and do complete kde rebuilds?

I'm currently using Qt 4.7.9999 on my kde-live installation, as it helped solve some previous problems, but my kdelibs klauncher_mac.patch failure mentioned above is still not resolved. I've resynced several times- no fix yet. I'd hate to go back to 4.7.0, and find I again have the other problems, but in general I really don't like running QT 9999 versions with kde-live.

Guess I should try editing the overlay ebuild and comment out that patch. From what I've read online, it seems to be for dealing with Mac OS systems, which I don't really need. Is this correct, and isn't anyone else running into this kdelibs-live patch issue?

My upgrade experience was that Qt 4.7 is binary compatible with Qt 4.6.

genstorm wrote:

Shining Arcanine wrote:

Qt 4.7.0 ebuilds just became available in the portage testing tree today. I had a pesky memory leak issue that caused compositing to fail, but that seems to have been fixed with the Qt updates.

@wrc1944: You don't need to go with it for 4.5.3, also qt-4.6.x still is the best choice if you also plan to compile openoffice with +kde. I'm using 4.7.0 and having GUI display issues in OO, besides no errors. What issues were you facing?

Well then packages.gentoo.org is lagging behind. Indeed, when I removed my package.unmask file for qt it is still listed unmasked._________________backend.cpp:92:2: warning: #warning TODO - this error message is about as useful as a cooling unit in the arctic

today after updating to qt 4.7.0 on amd64, kmail would no longer
receive or send mail (just gave an "unable to connect / protocol
unexpectedly died" error).

Something wrong with openssl and kmail (I have both
openssl-0.1X and openssl-0.0.9x installed)

found on the web the idea of:

Code:

ln -s libcrypto.so.1.0.0 libcrypto.so.0.9.8

Now kmail works again.

So in case anyone bumps into this ...

Strangely, this problem did not occur on my x86 notebook_________________.... there is nothing - absolutely nothing - half so much worth
doing as simply messing about with Linux ...
(apologies to Kenneth Graeme)