Doing an emerge of kemerge fails (on at least three sytems now) during the emerge of a dependency (kebuild) with the following output: In file included from main.cpp:25: /usr/kde/3/include/kebuild/kebuild.h:27: kebuildview.h: No such file or directory It would seem that this is a problem with the kebuild ebuild, not necessarily the kemerge ebuild. What a mouthful!
This bug is specifically in kebuildpart-0.3, where "make" fails to generate kebuildview.h. This is a problem with the makefile, *not* with the ebuild file. (Problem also occurs when installing manually.) Suggested workaround: manually merge kebuildpart-0.2, then upgrade to kebuildpart-0.3. Hopefully, this is an easy fix after comparing makefiles between versions...
You touched this one last and is hopefully in a better position to test and fix it. I don't have KDE installed currently.
Wout is taking a stroll, and it appears this bug is not with the ebuild, but with the kebuildpart code itself. If you decide to handle this, Yannick, just add your comments to the bug and reassign it to wmertens or myself when you are done.
The issue will be resolve in next Kemerge version which I was expected to do today but the ... autoconf/automake issue make it block. I mean each time I do make dist on my packet it generate the tar file but then I can re-build as it claim the need for configure.in.in even if it doesn't make sense... I need lots of training on autoconf/automake/configure...
This worries me . . . Leif do you get this earlier in the build? I use sudo to emerge and when I saw my home directory . . . ouch! /usr/qt/3/bin/uic -L /usr/kde/3/lib/kde3/plugins/designer -nounload -tr tr2i18n -i ebuildview.h ./ebuildview.ui | sed -e "s,tr2i18n( \"\" ),QString::null,g" | sed -e "s,tr2i18n( \"\"\, \"\" ),QString::null,g" | sed -e "s,image\([0-9][0-9]*\)_data,img\1_ebuildview,g" >> ebuildview.cpp || rm -f ebuildview.cpp fcntl: Bad file descriptor QSettings::sync: failed to open '/root/.qt/qt_plugins_3.0rc' for writing Conflict in /usr/qt/3/plugins/designer/kdewidgets.so: Plugin cannot be queried successfully! fcntl: Bad file descriptor QSettings::sync: failed to open '/root/.qt/qt_plugins_3.0rc' for writing fcntl: Bad file descriptor QSettings::sync: failed to open '/root/.qt/qt_plugins_3.0rc' for writing fcntl: Bad file descriptor QSettings::sync: failed to open '/root/.qt/qt_plugins_3.0rc' for writing fcntl: Bad file descriptor QSettings::sync: failed to open '/root/.qt/qt_plugins_3.0rc' for writing fcntl: Bad file descriptor QSettings::sync: failed to open '/root/.qt/qt_plugins_3.0rc' for writing Conflict in /usr/kde/3/lib/kde3/plugins/designer/kdewidgets.so: Plugin cannot be queried successfully! fcntl: Bad file descriptor QSettings::sync: failed to open '/root/.qt/qt_plugins_3.0rc' for writing Conflict in /usr/qt/3/plugins/designer/kdewidgets.so: Plugin cannot be queried successfully! fcntl: Bad file descriptor QSettings::sync: failed to open '/root/.qt/qt_plugins_3.0rc' for writing Conflict in /usr/kde/3/lib/kde3/plugins/designer/kdewidgets.so: Plugin cannot be queried successfully!
kebuild is a dead software ... replaced by kemerge.
Still fails with kemerge 0.7
fcntl: Bad file descriptor QSettings::sync: failed to open '/root/.qt/qt_plugins_3.0rc' for writing Conflict in /usr/kde/3/lib/kde3/plugins/designer/kdewidgets.so: Plugin cannot be queried successfully! I have no idea what those are, but kemerge still compile, install and works even if those lines appear.
*** Bug 6545 has been marked as a duplicate of this bug. ***
kebuild may be dead but kemerge still fails
ok, heres the fix make sure you have qt-3.0.5 installed: `emerge -s ^qt$` then re-emerge kdelibs `emerge kdelibs` then emerge kportagemaster this worked for me and for everyone else ... re-open this bug if it doesnt work for you guys :)
What is the error? kemerge-0.7 compile fine on my machine.
The warning stuff about qt-plugin is also seen on other package such as kbear. Therefore it is probably a configuration issue related to Qt but has nothing to do with Kemerge. As per the comment above to use kportagemaster instead, everyone's free to do that. I just feel that the way it was propose is unpleasant as I'm not forcing anyone to use my software.
me saving kportagemaster was a typo ;P basically the issue is that when the latest version of QT is installed, the KDELibs arent updated to handle the new functions so when KDE apps go to compile, they try to link via kdelibs to non existing functions (they change prototypes from what they used to use) basically the answer is 'if you kde ebuild fails becase of missing QT func calls, make sure qt-3.0.5 is installed, re-emerge KDELibs, re-emerge your app'
